1 (edited by rex_ray 2012-05-14 16:50:24)

Topic: [Solved] Postfix Bounced Mails with 'User unknown' error

==== Provide required information to help troubleshoot and get quick answer ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
==== ==== Provide required information to help troubleshoot and get quick answer ====
- iRedMail version: 0.7.3
- Linux/BSD distribution name and version: CentOS 6.2 (64 bit)
- Any related log? Log is helpful for troubleshooting.
====

Thanks in advance for the help. We have a production server running iRedMail-0.7.3 version without any problems. We are moving this setup to a new server with better hardware. For this I installed CentOS 6.2 on the new server followed by the installation of same iRedMail-0.7.3 version on it. Migrated the user/passwords(OpenLDAP) and the mailboxes to the new server. But here is the problem if I send a mail from 'user@example.com' to external domains the mail is sent successfully. However the mail sent from external domains (eg: user@gmail.com) to 'user@example.com' gets bounced. Even mail from www@example.com'
to 'user@example.com' bounces. One thing to note is if I create a new user 'user1@example.com' through 'iRedAdmin interface' then mail destined towards this mailbox gets successfully delivered.

Please see the output of postfix maillog below
 
  May 13 22:20:16 mail2 postfix/smtpd[5068]: connect from mail2.example.com[127.0.0.1]
May 13 22:20:16 mail2 postfix/smtpd[5068]: 3D162BC047C: client=mail2.example.com[127.0.0.1], sasl_method=LOGIN, sasl_username=www@example.com
May 13 22:20:16 mail2 postfix/cleanup[5071]: 3D162BC047C: message-id=<9e0a30d7e18e42592bf0f065629064ea@example.com>
May 13 22:20:16 mail2 postfix/qmgr[4371]: 3D162BC047C: from=<www@example.com>, size=558, nrcpt=1 (queue active)
May 13 22:20:16 mail2 roundcube: User www@example.com [10.10.80.39]; Message for user@example.com; 250: 2.0.0 Ok: queued as 3D162BC047C
May 13 22:20:16 mail2 postfix/pipe[5072]: 3D162BC047C: to=<user@example.com>, relay=dovecot, delay=0.15, delays=0.1/0.01/0/0.04, dsn=5.1.1, status=bounced (user unknown)
May 13 22:20:16 mail2 postfix/cleanup[5071]: 5F09DBC047E: message-id=<20120513165016.5F09DBC047E@mail2.example.com>
May 13 22:20:16 mail2 postfix/bounce[5074]: 3D162BC047C: sender non-delivery notification: 5F09DBC047E
May 13 22:20:16 mail2 postfix/qmgr[4371]: 5F09DBC047E: from=<>, size=2365, nrcpt=1 (queue active)
May 13 22:20:16 mail2 postfix/qmgr[4371]: 3D162BC047C: removed
May 13 22:20:16 mail2 postfix/smtpd[5068]: disconnect from mail2.example.com[127.0.0.1]
May 13 22:20:16 mail2 postfix/pipe[5072]: 5F09DBC047E: to=<www@example.com>, relay=dovecot, delay=0.21, delays=0.02/0/0/0.19, dsn=2.0.0, status=sent (delivered via dovecot service)
May 13 22:20:16 mail2 postfix/qmgr[4371]: 5F09DBC047E: removed
 
 
 
  Current Production Server:
 
  iRedMail Version: 0.7.3
  Operating System: CentOS 5.6 (64 bit)
  Backend: OpenLDAP
 
  New Server:
 
  iRedMail Version: 0.7.3
  Operating System: CentOS 6.2 (64 bit)
  Backend: OpenLDAP

Please help me out.

2

Re: [Solved] Postfix Bounced Mails with 'User unknown' error

Please paste below info to help troubleshoot:

- whole file of /etc/dovecot/dovecot-ldap.conf. REMOVE sensitive info before posting.
- LDIF data of this mail user

I guess you missed "enabledService=lda" in the LDIF data of mail user.

3

Re: [Solved] Postfix Bounced Mails with 'User unknown' error

ZhangHuangbin wrote:

Please paste below info to help troubleshoot:

- whole file of /etc/dovecot/dovecot-ldap.conf. REMOVE sensitive info before posting.
- LDIF data of this mail user

I guess you missed "enabledService=lda" in the LDIF data of mail user.

Thank you Zhang, I was able to solve the problem this morning. Compared the OpenLDAP attributes of mail id which was able to successfully receive incoming mails to the one which  was not able to do so. Found 'enabledService: lda' attribute to be the missing link. I added this missing attribute (thanks to your script 'updateLDAPValues_061_to_070.py') to all entries and now the problem is gone. As always thank you very much for your help.