Clay Dowling writes:
In the course of setting up sqwebmail, I found that for file attachments
it uses the following header:
Content-Disposition: attachment; filename*=iso-8859-1'en-us'Empire.tgz
See RFC 2231.
This causes problems with some mail clients such as squirrelmail, which
cannot handle this more compact notation and looses the filename
information.
I'm sure that were you to politely forward this pointer to squirrelmail's
developers, they'll be more than happy to enhance their client to handle
2231-encoded MIME headers.
I have modified webmail to produce the following header:
Content-Disposition: attachment; filename="Empire.tgz"
Squirrelmail and Sylpheed react more favorably to this header, and are
able to decipher the filename information. Before I commit to this change
on my production systems, will this change cause any problems? The
It might cause incorrect behavior with filenames that contains certain
characters.
Content-Type header still retains the original style:
Content-Type: application/octet-stream; name*=iso-8859-1''Empire.tgz
This is a parallel issue.
3 messages in net.sourceforge.lists.courier-users[courier-users] Re: Webmail mime file...
