Package: Evolution
Priority: Wishlist
Version: 1.0.0.99
Synopsis: IMAP weirdness from Exchange
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:

Using Exchange IMAP server, which has a habit of wrapping stuff to fit
72 chars, even though it is an attachment, or a signed message causes
mayhem in conjunction with messages that are pkix-signed. 

It appears that the Exchange server will run through some filters to get
it to fit into 72 chars, that cause the Ximian client to stop
acknowledging that it's a legitimate message with attachments. 

Example:

If I wrote you a really long message =
and the exchange server would wra=
p the lines, it would wrap them with a=
 equal sign. 

Any use of the '=' sign will show up as =3D


I once got a PIX-signed message that contained an attachment --  I had
to save the message as such, run it through a little stupid perl script
that I whipped up, and re=create the headers, load it in pine (I guess
Ximian would do, once all the ='s and =3Ds were fixed) and save the
image off.  What a hassle!

here's that stupid perl script I was talking about: 


$file = `cat smime.p7`;

$file =~ s/=\n//g;
$file =~ s/\=3D/=/g;
$file =~ s/=\n//g;
$file =~ s/\=3D/=/g;

print $file;


(Notice how I have to run it through the filters twice!)


Also, a lot of the pkix messages are only seen as smime.p7m attachments,
which I can't view inline.  It's a hassle to save these messages, and
load them up with 'less'  I don't especially care if the signature is
correct, just let me see the message content without having to jump
through hoops. 


Thanks.  You guys are awesome. 




Unknown reporter: pietbarber@netscape.net, changed to bugbuddy-import@ximian.com.