[MlMt] Forwarding as attachment corrupts attachments (in some cases).

[Scott A. McIntyre]

Hi,

I've been banging my head against the proverbial wall on this one and 
was wondering if it's Just Me or not.

Over the last few weeks I've noticed that if I receive an email which 
contains attachments, and then attempt to forward that same email *as* 
an attachment (Message -> Forward as Attachment) that the attachment(s) 
become corrupt and are unable to be opened by the recipient.

I am able to replicate this, but not 100% of the time.  I have noticed 
that when it fails, I can usually detect the failure by checking the 
attachment size of the message as-arrived to me, and, the size that 
MailMate (Version 2.0BETA (6110)) reports in the compose window, or, the 
size of the attachments after they're sent and arrive at the destination 
mailbox.

For example, a simple screenshot I sent myself contained a 1.2MB 
attachment (as reported in MailMate in the message view window).

If I then forward that as an attachment, the attachment size increases 
to 2.1MB.  But not always.  When this size discrepancy appears, I know 
the receiving end won't be able to open the attached image (even though 
MailMate displays the attached email message, and the attachment 
name/type for preview/save).

If I simply forward that same message (but not as an attachment), it 
stays working, 100% of the time.

In looking at raw messages that I can't open, it does appear that 
something has gone amiss with the process.

My *guess* here is that it is something to do with Office365 being 
involved.

 From a message (received, working attachment) I see that MS has 
injected a load of cruft around the MIME parts:

--=_MailMate_BA273722-4B6C-42F7-9B20-E82276673846_=
Content-Disposition: attachment; filename="Test Image.png"
Content-Type: image/png
Content-Transfer-Encoding: base64
X-Microsoft-Exchange-Diagnostics:
	1;SY2PR01MB2683;27:R6tmwluRy+z <total of 148 characters>
X-Microsoft-Antispam-Message-Info:
	MNMPy5SSb41Wk0Z1QZbp/1S7U5 <total of 769 characters>

iVBORw0KGgoAAAANSUhEUgAABLYAAAN2CAYAAADkKQCvAAAKrGlDQ1BJQ0MgUHJvZmlsZQAASImV
lgdUU1kax+97L73QAqFD6E26QADpNYQmHWyEhBJKCAlBRVRUxBEcCyIiWNGhiIJjAWRQEVFsg4IK
9gEZVNRxsGBDZR+whJnds7tn/+fcvN/58t3vfve9e8/5A0C5zREK02E5ADIE2aIwP09GTGwcA/8E

and so on.

However, on the system that receives the corrupted attachment(s), those 
MIME bits are the same, but it appears that the attachment itself is the 
raw data of the PNG file (sort of), rather than being encoded.

=89PNG=0D
=1A
=00=00=00=0DIHDR=00=00=04=B6=00=00=03v=08=06=00=00=00=E4)=00=AF=00=00
=ACiCCPICC 
Profile=00=00H=89=95=96=07TSY=1A=C7=EF{/=BD=D0=02=A1C=E8M=BA@=00=
=E95=84&=1Dl=84=84=12J=08	AETT=C4=11=1C=0B""X=D1=A1=88=82c=01dP=11Ql=83=82=



And so on.

Is it just me?  This used to work, but, I don't know whether something 
has changed with MM, Microsoft, or solar flares...

Thanks,

Scott