View Issue Details

IDProjectCategoryView StatusLast Update
0012126phpList 3 applicationAttachmentspublic23-03-09 16:49
Reportercrazydaddy Assigned To 
Status resolvedResolutionfixed 
Product Version2.10.4 
Target Version2.10.10Fixed in Version2.10.10 
Summary0012126: Receiving corrupt PDF attachments
DescriptionThis issue has been described in the forums since May 2007, under same title. It seems that it is mime encoding related and occurs only when messages are sent to MS Exchange 2003. Although this may strictly be an MS problem we'd appreciate a PHPlist fix as it impacts the majority of our mailing list user base and is certainly a major problem for us. The forums seem to indicate that the problem is still extant, or at least no fix in recent releases.
TagsNo tags attached.


related to 0002705 closed PHPList v2.11 release 
related to 0010176 closed PDF attachments corrupt for some recipients (on exchange servers) 
related to 0015164 resolvedmichiel Attachment data is double-wrapped in MIME-encoded message 



20-12-07 14:18


This issue has been classified to be investigated in the next release. We have no date planned yet for that release.

Did you check the forums and on the Microsoft website? There might be a solution already.

If you want, you can hire us to investigate and if possible build a solution.


01-04-08 01:41

manager   ~0043886

This issue is being discussed in these forum threads:


01-04-08 14:35


There is a problem in MS Exchange. A fix has been published by Microsoft. We are however still trying to find a workaround, for those users that are on systems that are not updated (bad boys! somehow I keep getting unsolicited offers)


06-04-08 04:14

reporter   ~0044258

There is a tool called Advanced PDF Repair. I have used it to repair many corrupt PDF files on my damaged disks successfully. Its homepage is

Maybe this can help.



15-05-08 19:45

reporter   ~0047184

I tried an experiment. I send a pdf file renamed to abc.test to a client with the exchange server issue. Your code sent it as an octet-stream. When the client renamed it, he claimed to still have the problem. This suggests a relatively sophisticated bug at the MSoft end. Looking at the MS note, KB937625, it appears to be an outlook only bug.


15-05-08 21:38

reporter   ~0047188

I noted that topic 9916 says something about a space character being an issue. Can anyone confirm that?


16-05-08 13:30


Last edited: 16-05-08 13:31

Also discussed in these forums threads:


04-11-08 18:44

updater   ~0050240

A working patch was already submitted in #15164. It just needs to be applied officially.


23-03-09 16:49

administrator   ~0050595

see also 0015164