No email received after yum update

Discussion in 'General' started by Florisjan, Apr 12, 2010.

  1. Florisjan

    Florisjan New Member

    Hello,

    I'm having a similar problem as before, I can no longer receive email. No errors are given anywhere, it just doesn't arrive.

    The 'perfect-server-cerntos-5.2-ispconfig-3' was running fine, using ispconfig version 3.0.2.

    Using 'yum update --exclude="postfix" --disablerepo=kbs-CentOS-Testing' worked fine until now.

    After updating, and a reboot, or updating ispconfig, which I suppose comes down to the same, email reception is gone. I can still log in to ispconfig, and secure webmail.

    All mail sent to the server is really lost, not still waiting to be delivered on other servers. So I assume it does actually arrive on the server, and then something goes wrong.

    This is a list of what has been updated, can anyone tell me which program causes the problem and how to fix it? The previous update was on march 22nd.

    Thanks a lot!

    Apr 12 18:42:44 server yum: Updated: openssl-0.9.8e-12.el5_4.6.x86_64
    Apr 12 18:42:44 server yum: Updated: cyrus-sasl-lib-2.1.22-5.el5_4.3.x86_64
    Apr 12 18:42:45 server yum: Updated: nspr-4.8.4-1.el5_4.x86_64
    Apr 12 18:42:46 server yum: Updated: httpd-2.2.3-31.el5.centos.4.x86_64
    Apr 12 18:42:47 server yum: Updated: nss-3.12.6-1.el5.centos.x86_64
    Apr 12 18:42:48 server yum: Installed: perl-NetAddr-IP-4.027-1.el5.rf.x86_64
    Apr 12 18:42:48 server yum: Updated: cyrus-sasl-2.1.22-5.el5_4.3.x86_64
    Apr 12 18:42:48 server yum: Updated: cyrus-sasl-plain-2.1.22-5.el5_4.3.x86_64
    Apr 12 18:42:52 server yum: Updated: subversion-1.6.9-0.1.el5.rf.x86_64
    Apr 12 18:42:53 server yum: Updated: perl-Net-SSLeay-1.36-1.el5.rf.x86_64
    Apr 12 18:42:53 server yum: Updated: lftp-4.0.6-1.el5.rf.x86_64
    Apr 12 18:42:53 server yum: Installed: re2c-0.13.5-1.el5.rf.x86_64
    Apr 12 18:42:53 server yum: Installed: perl-Encode-Detect-1.01-1.el5.rf.x86_64
    Apr 12 18:42:54 server yum: Updated: gnutls-1.4.1-3.el5_4.8.x86_64
    Apr 12 18:42:54 server yum: Installed: perl-Razor-Agent-2.84-1.el5.rf.x86_64
    Apr 12 18:42:54 server yum: Updated: perl-BerkeleyDB-0.41-1.el5.rf.x86_64
    Apr 12 18:42:55 server yum: Installed: perl-version-0.76-1.el5.rf.x86_64
    Apr 12 18:42:55 server yum: Updated: openssl-0.9.8e-12.el5_4.6.i686
    Apr 12 18:42:56 server yum: Updated: cyrus-sasl-lib-2.1.22-5.el5_4.3.i386
    Apr 12 18:42:57 server yum: Updated: nspr-4.8.4-1.el5_4.i386
    Apr 12 18:42:57 server yum: Updated: nspr-devel-4.8.4-1.el5_4.x86_64
    Apr 12 18:42:59 server yum: Updated: clamav-db-0.96-1.el5.rf.x86_64
    Apr 12 18:43:00 server yum: Updated: clamav-0.96-1.el5.rf.x86_64
    Apr 12 18:43:00 server yum: Updated: perl-Archive-Tar-1.56-1.el5.rf.noarch
    Apr 12 18:43:01 server yum: Updated: clamd-0.96-1.el5.rf.x86_64
     
    Last edited: Apr 12, 2010
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Please post the error messages from the maillog.
     
  3. Florisjan

    Florisjan New Member

    maillog

    Hello,

    Here's the last part of maillog, i don't see any errors so I just sent everything. For security reasons domain names / ip addresses have been changed.

    Mind the date is in the past.

    Just to be sure I just tried sending a message to myself using a gmail account, and tried receiving the mail using outlook. It did not arrive.

    This is the result in maillog:

    Apr 8 17:41:43 server postfix/smtpd[28230]: connect from mail-gy0-f175.google.com[209.85.160.175]
    Apr 8 17:41:44 server postfix/smtpd[28230]: 038251170325: client=mail-gy0-f175.google.com[209.85.160.175]
    Apr 8 17:41:44 server postfix/cleanup[28242]: 038251170325: message-id=<[email protected]>
    Apr 8 17:41:44 server postfix/qmgr[26245]: 038251170325: from=<[email protected]>, size=1876, nrcpt=1 (queue active)
    Apr 8 17:41:44 server postfix/smtp[28243]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)
    Apr 8 15:41:44 server postfix/smtp[28243]: 038251170325: to=<[email protected]>, relay=none, delay=0.47, delays=0.44/0.03/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused)
    Apr 8 17:41:45 server postfix/qmgr[26245]: 6D94F1170083: from=<[email protected]>, size=2993, nrcpt=1 (queue active)
    Apr 8 17:41:45 server postfix/qmgr[26245]: 1BD9E117009C: from=<>, size=4842, nrcpt=1 (queue active)
    Apr 8 17:41:45 server postfix/qmgr[26245]: C24621170321: from=<[email protected]>, size=2993, nrcpt=1 (queue active)
    Apr 8 15:41:45 server postfix/smtp[28243]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)
    Apr 8 15:41:45 server postfix/smtp[28243]: 6D94F1170083: to=<[email protected]>, relay=none, delay=1817, delays=1817/0.01/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused)
    Apr 8 15:41:45 server postfix/smtp[28243]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)
    Apr 8 15:41:45 server postfix/smtp[28243]: C24621170321: to=<[email protected]>, relay=none, delay=1696, delays=1696/0.03/0.14/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused)
    Apr 8 17:42:05 server imapd: Connection, ip=[::ffff:127.0.0.1]
    Apr 8 17:42:05 server imapd: LOGIN, user=[email protected], ip=[::ffff:127.0.0.1], port=[34678], protocol=IMAP
    Apr 8 17:42:05 server imapd: LOGOUT, user=[email protected], ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=87, sent=391, time=0
    Apr 8 17:42:07 server pop3d: Connection, ip=[::ffff:81.121.121.121]
    Apr 8 17:42:07 server pop3d: LOGIN, user=[email protected], ip=[::ffff:81.121.121.121], port=[63895]
    Apr 8 17:42:08 server pop3d: LOGOUT, user=[email protected], ip=[::ffff:81.121.121.121], port=[63895], top=0, retr=0, rcvd=12, sent=39, time=1
    Apr 8 17:42:14 server postfix/smtpd[28230]: disconnect from mail-gy0-f175.google.com[209.85.160.175]
    Apr 8 17:42:15 server postfix/smtp[28246]: connect to example.com[192.0.32.10]: Connection timed out (port 25)
    Apr 8 17:42:15 server postfix/smtp[28246]: 1BD9E117009C: to=<[email protected]>, relay=none, delay=194777, delays=194747/0.09/30/0, dsn=4.4.1, status=deferred (connect to example.com[192.0.32.10]: Connection timed out)
    Apr 8 17:43:13 server pop3d: Connection, ip=[::ffff:81.121.121.121]
    Apr 8 17:43:13 server pop3d: LOGIN, user=[email protected], ip=[::ffff:81.121.121.121], port=[63915]
    Apr 8 17:43:13 server pop3d: LOGOUT, user=[email protected], ip=[::ffff:81.121.121.121], port=[63915], top=0, retr=0, rcvd=12, sent=39, time=0
    Apr 8 17:43:59 server pop3d: Connection, ip=[::ffff:81.121.121.121]
    Apr 8 17:43:59 server pop3d: LOGIN, user=[email protected], ip=[::ffff:81.121.121.121], port=[63940]
    Apr 8 17:43:59 server pop3d: LOGOUT, user=[email protected], ip=[::ffff:81.121.121.121], port=[63940], top=0, retr=0, rcvd=12, sent=39, time=0
     

    Attached Files:

  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Looks as if amavisd is not started on your system. Please start it with the script in /etc/init.d and then check again the mail log file.
     
  5. Florisjan

    Florisjan New Member

    amavisd

    Amavisd was not running, thank you!
    I ran sa-update, and tried again, now email is back up.

    One final question, was this caused by updating or just coincidence?

    Thanks again,

    Florisjan

    /etc/init.d/amavisd restart
    Shutting down Mail Virus Scanner (amavisd): [FAILED]
    Starting Mail Virus Scanner (amavisd): [ OK ]

    Apr 8 17:14:22 server amavis[26944]: starting. /usr/sbin/amavisd at server.server.nl amavisd-new-2.6.4 (20090625), Unicode aware, LANG="en_US.UTF-8"
    Apr 8 17:14:22 server amavis[26944]: Perl version 5.008008

    ...
    Apr 8 17:14:24 server amavis[26946]: (!!)TROUBLE in pre_loop_hook: config: no rules were found! Do you need to run 'sa-update'?
    Apr 8 17:14:24 server amavis[26946]: (!)_DIE: Suicide () TROUBLE in pre_loop_hook: config: no rules were found! Do you need to run 'sa-update'?
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    I guess that a centos rpm, maybe one of the perl updates, messed up the spamassasin rule files and sa-update fixed it again.
     
  7. rukus77

    rukus77 New Member

    Same happened to me after updating clamd (and clamav).

    I began getting a clamd.sock error in the logs as well;

    (!)ClamAV-clamd: Can't connect to UNIX socket /var/run/clamav/clamd.sock: No such file or directory, retrying

    So I had to verify that the path matched between;

    amavisd.conf (CONTSCAN)

    and;

    clamd.conf (LocalSocket)

    I then to had to comment out TCPSocket and uncomment LocalSocket.

    Everything working well now. Hope this helps someone else out.

    Mike
     
    Last edited: Apr 14, 2010

Share This Page