<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>We’ve had a couple of users complain that PDFs that we produce using RenderX are being blocked in emails by MailMarshal. It’s the first I’ve heard of the issue but I wondered if what we have been told by one of the IT people from the client is accurate:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>==<o:p></o:p></p><p class=MsoNormal>The files attached did not contain a known finger print for Adobe PDF file type. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For example, if you created a .docx file in Microsoft Word and saved it, the document would contain a finger print in the Hexadecimal code of the file that identifies it as a Microsoft Word document. Our MailMarshal Spam Server (and presumably other Spam systems) check the finger print of every file received, to verify that the attachment is what is says it is. Another example would be… a .exe file would contain a .exe finger print, should the file be renamed to .zip, our Anti Spam system would block the attachment as it contained a .exe finger print.<o:p></o:p></p><p class=MsoNormal>==<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>They say they had to add a new file type to the MailMarshal config. They did this by creating a new ‘finger print’ from the first couple of hundred bytes of the files, which they have observed don’t change, and subsequently files are accepted. The inference is that the PDFs we are creating are not in the format recognised by MailMarshal.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Is there some configuration we need to do that has been overlooked? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div>
!DSPAM:87,52a7f8b89851456241067!
</body></html>