Enda writes:
I have a customer who is complaining that his attachements are getting
renamed to .dat by the email server.
I've ran a bunch of tests with him, and am confident that the server isn't
actually doing this, but that the remote receiving server is.
The thing is, I can email through the server from any test client and not
replicate the problem, and then replicate it through sqwebmail. To me this
is an interop issue with sqwebmail and whatever third party MTA / clients
which are renaming the attachments.
Is this a mimetype / message encoding scheme problem that I can accomodate
through re-configuration, or am I the only one to come up against this?
You are unclear in your explanation, as to whether messages received by
sqwebmail show an incorrect attachment name, or whether messages sent from
sqwebmail show an incorrect attachment name when download by some other mail
client. I believe that it's the latter, but you are not clear.
If this is the latter, try renaming the file before attaching it, to exclude
any punctuation, spaces, or non-English characters from the filename (except
for a single .extension). When present, they cause the attachment's name to
be encoded according to certain standards which some poorly written mail
clients may not be able to process. In any case, no renaming of any
attachment occurs on any server, it's just that the mail client that
downloads the attachment fails to properly implement the applicable Internet
standards.
5 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] Sqwebmail composed em...
