After yum upgrade, Postfix/Dovcott mail server is broken
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
OK, Here is more information, I cleaned it up for security reasons.
Code:
[root@host log]# cat /dev/null > /var/log/maillog
[root@host log]# tail -f maillog
Aug 23 22:54:57 host postfix/smtpd[5762]: connect from c-11-11-11-118.hsd1.mi.comcast.net[68.xxx.xxx.xxx]
Aug 23 22:54:58 host postfix/smtpd[5762]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory
Aug 23 22:54:58 host postfix/smtpd[5762]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory
Aug 23 22:54:58 host postfix/smtpd[5762]: warning: SASL authentication failure: no secret in database
Aug 23 22:54:58 host postfix/smtpd[5762]: warning: c-11-11-11-118.hsd1.mi.comcast.net[68.xxx.xxx.xxx]: SASL CRAM-MD5 authentication failed: authentication failure
Aug 23 22:54:58 host postfix/smtpd[5762]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory
Aug 23 22:54:58 host postfix/smtpd[5762]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory
Aug 23 22:54:58 host postfix/smtpd[5762]: 323DB1C6859F: client=c-11-11-11-118.hsd1.mi.comcast.net[68.xxx.xxx.xxx], sasl_method=PLAIN, sasl_username=myname
Aug 23 22:54:58 host postfix/cleanup[5777]: 323DB1C6859F: hold: header Received: from [192.168.0.7] (c-11-11-11-118.hsd1.mi.comcast.net [68.xxx.xxx.xxx])??by host.domain.com (Postfix) with ESMTP id 323DB1C6859F??for <A.Name@-ais.com>; Sat, 23 Aug 2008 22:54:58 -04 from c-11-11-11-118.hsd1.mi.comcast.net[68.xxx.xxx.xxx]; from=<goto@da.com> to=<A.Name@gd-ais.com> proto=ESMTP helo=<[192.168.0.7]>
Aug 23 22:54:58 host postfix/cleanup[5777]: 323DB1C6859F: message-id=<48B0D526.8060007@Host.com>
Aug 23 22:54:58 host postfix/smtpd[5762]: disconnect from c-11-11-11-118.hsd1.mi.comcast.net[68.XXX.XXX.XXX]
Starting MailScanner daemons:
incoming postfix: [ OK ]
outgoing postfix: [ OK ]
MailScanner: is only avaliable with the XS version at /usr/lib/perl5/vendor_perl/5.8.8/Compress/Zlib.pm line 9
BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.8.8/Compress/Zlib.pm line 9.
Compilation failed in require at /usr/lib/perl5/vendor_perl/5.8.8/Archive/Zip.pm line 11.
BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.8.8/Archive/Zip.pm line 11.
Compilation failed in require at /usr/lib/MailScanner/MailScanner/Message.pm line 48.
BEGIN failed--compilation aborted at /usr/lib/MailScanner/MailScanner/Message.pm line 48.
Compilation failed in require at /usr/sbin/MailScanner line 79.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 79.
Your SASL is incorrectly configured, and can't authenticate
Mail is being held because there is a Received header_check rule that is holding the mail
Mailscanner (amavisd-new + mods) is failing to load because there are version problems with your Compress::Zlib perl libraries.
There is too much to fix here all at once. You should focus on getting one portion of your mail server working at a time, in this order 1) plain SMTP, no authentication, no content filter, 2) authentication, 3) content_filter. 4) add various header_checks/body_checks/filter rules to tune.
Honestly, I have no interest in reading or debugging somebody else's HowTo.
In my opinion, it is worthwhile learning about how the software you use works. Consider
The Book of Postfix to guide you to understanding what is going on.
Otherwise, you end up in a position where you can't resolve any problems that arise.
So, you have a couple of choices. You can either tear it all down, and try to follow the
HowTo again to rebuild it, checking each step along the way. You can fix one component at a time, but
still need to learn about how to do that. I can't advise which way is best for you.
You can comment out your header_checks in your main.cf for now.
You can comment out all the smtpd_sasl* and smtpd_tls* settings in main.cf until you get basic postfix working.
There is no content_filter setting shown in your output of postconf -n, so mailscanner is being configured in master.cf or elsewhere.
Show master.cf also.
Your mailscanner software required certain perl modules, which it seems you probably updated via CPAN or source (right?).
These are in conflict with your existing package-based or base perl modules. You need to update some dependent perl
modules such as List::Scalar. But ignore this for now, at least until you get your basic mail server running.
OK, thanks for the advice, I didnt mean to have you debug someone elses how to, I thought you wanted me to post what I was going/went from. I will try to disable all the security settings so I can get the smtp working.
I thank you for the time you have taken, this is a learning experience.
It is a lot of documentation, and this is what makes trying to do too much at once so difficult to troubleshoot, which finally leads to: http://www.postfix.org/DEBUG_README.html
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.