Logged In: YES 
user_id=113859

Hi Alexander,
thanks for answering and helping to get this bug fixed.

I completely agree with yout that charset guessing is
the wrong solution, but actually it _is_ a solution.
Unless the Charset is saved somewhere, I do not see a better
solution, though.
Guesses about the encoding will not fix the bug that you send
emails out with the wrong charset = (text encoding).
Thus this bug probably should still be open.

If you suggest to save the charset as part of the filetype
string:
This could potentially be a solution, but it might break the
current assumption
what is in this string. The charset usually is not part of
the MIME-Type,
but of the email Content-Type.

This is whay I propose to save the charset in an extra field,
if the filetype is "text/plain". This would be a larger change
to roundup as all input and output channels would need to be
checked
to save the charset or guess it instead.

Also I do not fully understand what you mean by: applying
site defaults. A good site will get utf-8 and latin-1
encoded text-attachments and must record that encoding and 
possibly recode it at a few occasions.

        Bernhard