[quote user="Euler GERMAN"]
My filetype.pm control file has two PDF related entries in the following order:
Adobe-PDF,0,X,0,.PDF
Adobe-PDF,S,0,\037PDF\045
It seems to me it uses preferentially the "Attachment type" rather than extension to choose which application to call.[/quote]
Thank you. I've added these two to my filetype.pm
[quote user="Euler GERMAN"]
Strangely, my mime-map.pm file has only a single line "Text/HTML = HTML-text" (no quotes). I'm assuming it has little or no-effect on how Pmail handles attachments. BTW, this is the same file I have under my \Programs\RESOURCE directory.
Anyway, I remember of recipients complaining about attachments sent by me were found corrupt after being processed by Pmail. This happened a long time ago and I don't remember which measures taken corrected the problem. My guess is that telling Pmail to behave by the "Attachment type" instead of file extension is a good guess. As an example, I remember plain-text attachments being added to the message body instead of attached as a file. I used a trick (can't remember who whispered it to me) to make Pmail treat plain-text as binary by adding the line below to filetype.pm:
[code];Text,0,X,0,.TXT
binary,0,R,0,\\032,R,0,\\013\\010,R,0,e,R,0,E,R,0,t,R,0,T,R,0,n,R,0,N,R,0,r,R,0,R,R,0,i,R,0,I,R,0,o,R,0,O,R,0,a,R,0,A,R,0,s,R,0,S,R,0,d,R,0,D,R,0,h,R,0,H,R,0,l,R,0,L,R,0,c,R,0,C,R,0,f,R,0,F,R,0,p,R,0,P,R,0,u,R,0,U,R,0,m,R,0,M
[/code]
Notice that the original "Text" is commented.
Lastly, anyone can get a copy of my current filtype.pm control file for the next 7 days. I'm not saying it is perfect, but it plays well here without hiccups AFAIK.
[/quote]
I've added this too.
I'll start sending PDFs again by right clicking the file to send to Pegasus and see if I get any more complaints of not being able to read PDF attachments.
So far it looks good. Pegasus is now saying that my attachment is a PDF, unlike before. However it still wants to use encoding. I'll let Pegasus do that for now.