[quote user="Tracy"]Just started using Pegasus and are finding PDF files are corrupted when it reaches the recipient....anyone else seen this?[/quote]
I remember once having problems with this as Pegasus Mail treated some PDFs as text files and corrupted their formatting by interpreting as line breaks which actually were some kind of binary data. The easiest workaround would be to manually select the encoding type at the bottom of the attachments tab after attaching the file: Basic MIME should do it. I believe there's also a way to configure Pegasus Mail to do this automatically but I can't figure it out right now.
To ensure this your issue can you open such a (supposedly corrupted) message in raw view and look for the header line starting with Content-transfer-encoding: preceding the attachment section to see whether it uses BASE64. The whole header section of a PDF attachment should look similar to this one:
Content-type: Application/Octet-stream; name="Filename.pdf"; type=Unknown
Content-disposition: attachment; filename="Filename.pdf"
Content-transfer-encoding: BASE64
If it already does then there's probably nothing you can do and the above workaround doesn't fit, the problem might be located at the recipient's site. Can you open these PDFs ok on your machine?
<p>[quote user="Tracy"]Just started using Pegasus and are finding PDF files are corrupted when it reaches the recipient....anyone else seen this?[/quote]</p><p>I remember once having problems with this as Pegasus Mail treated some PDFs as text files and corrupted their formatting by interpreting as line breaks which actually were some kind of binary data. The easiest workaround would be to manually select the encoding type at the bottom of the attachments tab after attaching the file: Basic MIME should do it. I believe there's also a way to configure Pegasus Mail to do this automatically but I can't figure it out right now.</p><p>&nbsp;To ensure this your issue can you open such a (supposedly corrupted) message in raw view and look for the header line starting with <i>Content-transfer-encoding: </i>preceding the attachment section to see whether it uses BASE64. The whole header section of a PDF attachment should look similar to this one:</p><p><i>Content-type: Application/Octet-stream; name="Filename.pdf"; type=Unknown
Content-disposition: attachment; filename="</i><i>Filename</i><i>.pdf"
Content-transfer-encoding: BASE64</i>
If it already does then there's probably nothing you can do and the above workaround doesn't fit, the problem might be located at the recipient's site. Can you open these PDFs ok on your machine?
</p>
Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
