[imp] attachments becoming unusable

[Philip Steeman]

Changed to horde 3.1.7 --> same problem
The problem has probably someting to do with the fact that the 
attachment is NOT base64 encoded if sent with imp.

source:
> Content-Type: text/plain;
> 	charset=ISO-8859-1;
> 	name="Gpuntis.RDP"
> Content-Disposition: attachment;
> 	filename="Gpuntis.RDP"
> Content-Transfer-Encoding: quoted-printable

Can it be a problem with php?
My version is 4.3.10

Philip

MailingListe schreef:
> Zitat von Philip Steeman <philip.steeman at khbo.be>:
> 
>> Hello,
>> I have the following problem with some kind of attachments:
>> - .rdp (remote desktop)
>> - .sav (SPPS)
>>
>> The best way to reproduce the problem, is the following:
>>
>> 1) make a rdp-file (via remote desktop on windows)
>> 2) mail it to yourself from imp
>> 3) read your mail via another mailclient (Outlook, Thunderbird)
>> 4) save this attachment via Outlook/TB
>> 5) make a diff between the original one and the second one --> they
>> differ and become unusable
>>
>> The following is true;
>> sent with imp, saved with imp: OK
>> sent with Outlook/TB, saved with Outlook/TB: OK
>> sent with Outlook/TB, saved with imp: OK
>> sent with imp, saved with Outlook/TB: WRONG
>>
>> Sent with TB the attachment is base64 encoded. Sent with imp it is
>> 'pure' text.
>>
>> This is a bit annoying for our users. I tell them to zip the file first
>> (or use imp to read).
>>
>> The version we use:
>> horde: 3.1.6
>> imp: 4.1.6
> 
> Works fine here...
> horde 3.1.7 (you should update BTW)
> imp 4.1.6
> 
> The file is included as base64 as it should. The file type is  
> missinterpreted but this does not matter.
> 
> --=_4mm6ik5x9eas
> Content-Type: audio/mpeg;
> 	name="test.rdp"
> Content-Disposition: attachment;
> 	filename="test.rdp"
> Content-Transfer-Encoding: base64
> 
> Regards
> 
> Andreas
> 
>