<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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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><span style='color:#1F497D'>Yes I think it is a case of the tail wagging the dog. I just wanted to make sure it wasn’t something I was doing wrong. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> xep-support-bounces@renderx.com [mailto:xep-support-bounces@renderx.com] <b>On Behalf Of </b>Kevin Brown<br><b>Sent:</b> Wednesday, 11 December 2013 4:59 PM<br><b>To:</b> 'RenderX Community Support List'<br><b>Subject:</b> [xep-support] Re: PDF attachments blocked as spam<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Never heard of it. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>A PDF created by RenderX certainly has some repeatable characteristics and if they can map them great … like seeking the /Producer line.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>If they looked into a PDF compressed or not, they would see … (of course with your own version of software)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>/Producer (XEP 4.19 build 20110414)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>For instance.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Or if they looked at the Metadata stream for the xmpmeta information, they would find:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><pdf:Producer>XEP 4.19 build 20110414</pdf:Producer><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Now, that issue is TOTALLY up to the company providing the overzealous checker of PDF files to determine what is a valid PDF file and what is not. If they have not “mapped” RenderX, sorry we cannot help you. Sounds like they probably think Adobe and Microsoft are the only two companies in the world that create PDFs…<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Kevin Brown<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>RenderX<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1..0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:xep-support-bounces@renderx.com">xep-support-bounces@renderx.com</a> [<a href="mailto:xep-support-bounces@renderx.com">mailto:xep-support-bounces@renderx.com</a>] <b>On Behalf Of </b>Darren Munt<br><b>Sent:</b> Tuesday, December 10, 2013 9:31 PM<br><b>To:</b> <a href="mailto:xep-support@renderx.com">xep-support@renderx.com</a><br><b>Subject:</b> [xep-support] PDF attachments blocked as spam<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><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><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p></div>
!DSPAM:87,52a800449851098917897!
</body></html>