Local email delivery does not work anymore after update to 3.0.3

Discussion in 'Installation/Configuration' started by modir, Dec 9, 2010.

  1. modir

    modir New Member

    After the upgrade from 3.0.1 to 3.0.3 the delivery of local emails does not work anymore. The rest (forwards, etc.) work without any problems.

    I have the following message in my log files:
    Dec 9 16:35:13 shared postfix/pipe[27745]: 0FBBF124843F: to=<[email protected]>, relay=maildrop, delay=0.16, delays=0.07/0.02/0/0.08, dsn=5.1.1, status=bounced (user unknown. Command output: Invalid user specified. )

    When I check in the MySQL database then the domian is in mail_domain and the email address exists in mail_user.

    Connecting to the mailbox over IMAP or POP3 works as well.

    Does anybody have some more ideas?

    The System is a CentOS 5.5 Linux.
     
  2. falko

    falko Super Moderator Howtoforge Staff

    Can you post your main.cf and your master.cf?
     
  3. modir

    modir New Member

    Hi falko,

    Here are the two files.

    Thanks for looking at them.

    Raffael
     

    Attached Files:

  4. falko

    falko Super Moderator Howtoforge Staff

    Are there any other errors in your mail log? Does
    Code:
    postqueue -p 
    show any errors?
    Is SELinux disabled?
     
  5. modir

    modir New Member

    "postqueue -p" doesn't show any errors. And SELinux is permissive.

    And no, there are no error in the maillog except for the mentioned one and for the valid ones. (There are many "postfix/smtpd[18654]: NOQUEUE: reject: RCPT from XXX Recipient address rejected: User unknown in virtual mailbox table;" messages. But they are valid because those user accounts really do not exist.)
     
  6. modir

    modir New Member

    I updated now to 3.0.3.1 and I have still the same problems. (I have to say that I didn't expect anything else because I haven't seen any closed tickets that would have something to do with this issue.)
     
  7. modir

    modir New Member

    I maybe found something:

    [root@shared postfix]# /usr/bin/maildrop -v
    maildrop 2.5.1 Copyright 1998-2005 Double Precision, Inc.
    GDBM/DB extensions enabled.
    Maildir quota extension are now always enabled.
    This program is distributed under the terms of the GNU General Public
    License. See COPYING for additional information.

    Do I need more extensions maybe?
     
  8. holykim

    holykim Member

    If you have an error "postfix/trivial-rewrite[16832]: warning: do not list domain server.tld in BOTH mydestination and virtual_mailbox_domains ... "

    please try to remove the domain from mydestination in /etc/postfix/main.cf

    Harry
     
  9. modir

    modir New Member

    Hi Harry,

    No, I do not have this message. Within postfix everything is fine. Amavis is giving it back marked as clean, etc.

    The problem is totally at the end when postfix already piped the message to maildrop:

    Dec 14 00:58:57 shared postfix/pipe[13260]: D3F4B1248608: to=<[email protected]>, relay=maildrop, delay=0.14, delays=0.07/0.02/0/0.06, dsn=5.1.1, status=bounced (user unknown. Command output: Invalid user specified. )


    My suspicion is now that there is something wrong with /var/vmail/.mailfilter. But I can not verify it.
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you install any centos updates ?
     
  11. modir

    modir New Member

    Hi Till,

    Yes, I did. Several of them.
     
  12. falko

    falko Super Moderator Howtoforge Staff

    When you upgraded to ISPConfig 3.0.3.1, did you choose to reconfigure all services?

    Did you install any CentOS updates for Postfix?
     
  13. modir

    modir New Member

    When I updated to 3.0.3 I did not reconfigure the services. And afterwards it didn't work anymore. With the update to 3.0.3.1 I did reconfigure all services and it still stayed the same.

    There were no updates regarding postfix. But there was an update for maildrop.
     
  14. modir

    modir New Member

    But the last maildrop update didn't bring any changes to the config files:

    [root@shared ~]# rpm --query --filesbypkg maildrop
    maildrop /usr/bin/lockmail
    maildrop /usr/bin/mailbot
    maildrop /usr/bin/maildrop
    maildrop /usr/bin/makedat
    maildrop /usr/bin/makedatprog
    maildrop /usr/bin/makemime
    maildrop /usr/bin/reformail
    maildrop /usr/bin/reformime
    maildrop /usr/share/doc/maildrop-2.5.1
    maildrop /usr/share/doc/maildrop-2.5.1/AUTHORS
    maildrop /usr/share/doc/maildrop-2.5.1/COPYING
    maildrop /usr/share/doc/maildrop-2.5.1/COPYING.GPL
    maildrop /usr/share/doc/maildrop-2.5.1/ChangeLog
    maildrop /usr/share/doc/maildrop-2.5.1/README
    maildrop /usr/share/doc/maildrop-2.5.1/README.postfix
    maildrop /usr/share/doc/maildrop-2.5.1/UPGRADE
    maildrop /usr/share/doc/maildrop-2.5.1/deliverquota.html
    maildrop /usr/share/doc/maildrop-2.5.1/lockmail.html
    maildrop /usr/share/doc/maildrop-2.5.1/mailbot.html
    maildrop /usr/share/doc/maildrop-2.5.1/maildir.html
    maildrop /usr/share/doc/maildrop-2.5.1/maildirmake.html
    maildrop /usr/share/doc/maildrop-2.5.1/maildirquota.html
    maildrop /usr/share/doc/maildrop-2.5.1/maildrop.html
    maildrop /usr/share/doc/maildrop-2.5.1/maildropex.html
    maildrop /usr/share/doc/maildrop-2.5.1/maildropfilter.html
    maildrop /usr/share/doc/maildrop-2.5.1/maildropgdbm.html
    maildrop /usr/share/doc/maildrop-2.5.1/makedat.html
    maildrop /usr/share/doc/maildrop-2.5.1/makemime.html
    maildrop /usr/share/doc/maildrop-2.5.1/manpage.css
    maildrop /usr/share/doc/maildrop-2.5.1/reformail.html
    maildrop /usr/share/doc/maildrop-2.5.1/reformime.html
    maildrop /usr/share/doc/maildrop-2.5.1/rfc2045.html
    maildrop /usr/share/doc/maildrop-2.5.1/rfc822.html

    Strange.
     
  15. falko

    falko Super Moderator Howtoforge Staff

Share This Page