Problem with MailScanner, postfix and corrupt mails
Dean Jones
dean at SAHRA.ARIZONA.EDU
Mon Mar 28 18:26:38 IST 2005
[ The following text is in the "ISO-8859-1" character set. ]
[ Your display is set for the "US-ASCII" character set. ]
[ Some characters may be displayed incorrectly. ]
Julian Field wrote:
> Can you give us more details on the Cyrus problem you had? Would be
> worth adding this to the FAQ to help other people.
>
Ok, i'll throw some more details out at the cost of embarrasing myself ;)
Basically on my solaris boxes i compile stuff from scratch.
so for my mailscanner system i compiled:
cyrus-sasl, openssl, perl, berkely db, postfix and a bunch of other
non-related stuff.
I had set up postfix first and tested the TLS stuff (which is why i
needed cyrus-sasl and openssl to compile TLS into postfix) and the TLS
stuff was working.
but during my setup of MailScanner i had changed which user postfix runs
as and that user didn't have permission to read the cyrus-sasl
libraries. (doh)
I'm not 100% sure of the next part but it seemed a very small percentage
of MailScanner messages require that library for some reason??
So i was debugging MailScanner to check out some spamassassin rules i
had created and on one of the debug attempts i noticed there was an
error accessing that sasl library.
It looked like a rather ugly error as well.
so i just gave the mailscanner/postfix user read access on the libraries
and that problem went away.
And since that point there have been no corrupt mails but that might
just be coincidence?
------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ (http://www.mailscanner.biz/maq/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).
Support MailScanner development - buy the book off the website!
More information about the MailScanner
mailing list