Displaying 2 results from an estimated 2 matches for "rfc2184".
Did you mean:
rfc2104
2011 Sep 29
1
Broken mail clients? [MIME] Long attachment encoded filenames (for non-ASCII characters etc)
...ME is not as good as it should be, so I may easily
have got this all mixed up, in which case sorry for the noise...
Although I understand the preferred method for handling filenames split across
multiple lines (because they're too long to fit on one line in the message) is
that suggested in RFC2184/2231, so for example,
filename*0*=iso-8859-1''accented_characters_here_%EA%CA%E6
filename*1=etc%2Epdf
I find that some mail clients do this instead,
filename="=?ISO-8859-1?Q?accented_characters_here_=EA=CA=E6?=
=?ISO-8859-1?Q?etc=2Epdf?="...
2011 Sep 29
0
Long attachment encoded filenames (for non-ASCII characters etc) in MIME headers & corresponding Dovecot behaviour
...ME is not as good as it should be, so I may easily
have got this all mixed up, in which case sorry for the noise...
Although I understand the preferred method for handling filenames split across
multiple lines (because they're too long to fit on one line in the message) is
that suggested in RFC2184/2231, so for example,
filename*0*=iso-8859-1''accented_characters_here_%EA%CA%E6
filename*1=etc%2Epdf
I find that some mail clients do this instead,
filename="=?ISO-8859-1?Q?accented_characters_here_=EA=CA=E6?=
=?ISO-8859-1?Q?etc=2Epdf?="...