Attachments problems

[Derek B. Noonburg]

On 14 May, laurent.duperval@microcell.ca wrote:
> On 14 May, maf@tkrat.org wrote:
>> On 14 May, laurent.duperval@microcell.ca wrote:
>>> - The same file is viewed correctly when sent with Mozilla but not with
>>>   Tkrat
>> 
>> Could you try to send it (or one like that) to me with both mozilla and
>> TkRat.
> 
> Sure, and everyone gets a copy. If you see weird behaviour with it, report
> back to the list.
> 
> This is with tkrat.

Your sent-with-Mozilla version looks fine.  When I hit "save to file" on
the attachment, I see the name with the 8-bit character (c-cedilla).

But this one (sent with TkRat) doesn't show any default file name at all
when I hit "save to file".

I'm running TkRat 2.1.1.

Looking at the raw messages, the sent-with-tkrat message looks a little
weird.

Mozilla's MIME part header looks like this:

Content-Type: application/gzip;
 name="=?ISO-8859-1?Q?TestFran=E7ais=2Etxt=2Egz?="
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="=?ISO-8859-1?Q?TestFran=E7ais=2Etxt=2Egz?="

TkRat's looks like this:

Content-Type: APPLICATION/X-GZIP; NAME*="iso-8859-1''TestFran%E7ais.txt.gz"
Content-Transfer-Encoding: BASE64
Content-Disposition: ATTACHMENT;
 FILENAME*="iso-8859-1''TestFran%E7ais.txt.gz"

I'm not particularly familiar with MIME, so far all I know this is
perfectly fine, but it sure looks funny.

Also, there could be something going on with my mail system, which
consists of: my ISP's POP server, fetchmail, procmail, SpamAssassin,
Courier imapd.  (Both messages went through the identical chain,
though.)

Hope this helps.

- Derek