Hi guys, I'm using legacy Zimbra appliance on cloud ec2 server. After initial setup, ran zimbra-conf to setup new domain name and password. Logged into Zimbra admin console on port 7071 to setup new admin accounts etc.

At this stage I would have thought admin@example.com and the mail.example.com domain would no longer exist. However checking the mail queue shows that internal mail (presumably internal notifications) are still trying to go from <zimbra@mail.example.com> to <admin@example.com> and naturally it is bouncing because the ?mta and smtp agents can't resolve example.com because it has been replaced... but it looks like not all configuration files or ? mysql databases know about this.

Ive included part of the log output from /var/log/mail.conf (the sendmail log file ??) to show whats happening :

Apr 22 21:04:24 ip-10-196-170-187 postfix/smtp[11195]: connect to example.com[192.0.32.10]: Connection timed out (port 25)

Apr 22 21:04:24 ip-10-196-170-187 postfix/smtp[11195]: 7E95D12431: to=<admin@example.com>, relay=none, delay=617, delays=587/0.01/30/0, dsn=4.4.1, status=deferred (connect to example.com[192.0.32.10]: Connection timed out)

Apr 22 21:04:24 ip-10-196-170-187 postfix/smtp[11196]: connect to example.com[192.0.32.10]: Connection timed out (port 25)

Apr 22 21:04:24 ip-10-196-170-187 postfix/smtp[11197]: connect to example.com[192.0.32.10]: Connection timed out (port 25)

Apr 22 21:04:24 ip-10-196-170-187 postfix/smtp[11196]: 8B9D912435: to=<admin@example.com>, relay=none, delay=617, delays=587/0.01/30/0, dsn=4.4.1, status=deferred (connect to example.com[192.0.32.10]: Connection timed out)

Apr 22 21:04:24 ip-10-196-170-187 postfix/smtp[11197]: DE7E112432: to=<admin@example.com>, relay=none, delay=616, delays=586/0.03/30/0, dsn=4.4.1, status=deferred (connect to example.com[192.0.32.10]: Connection timed out)

Ive searched the forums for anything like this but cant find much, I saw an issue with the zimbra-conf script early on but I dont think it relates to this. It would seem to my uninformed eye that the issue lies in a config file somewhere, but I've looked at many seemingly mail related conf files and cant find any left over references to the mail.example.com domain.

All thoughts would be appreciated.

Thanks Scott H.

*****************************************************************************

SELF REPLY  :  Since this post this issue has ceased to occur .. . maybe I went off a bit too early .. would appear that perhaps these internal emails were deferred mails generated by the system between boot time and running of zimbra-conf, any way they must have all eventually been handled by me manually deleting them from the mail queue via the Zimbra admin console, so I guess all parts the system know what the proper domain name is now.

*****************************************************************************