1 (edited by echo5 2019-01-17 03:16:10)

Topic: CentOS7 update broke iRedMail 0.9.3

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail 0.9.3
- Installer
- CentOS 7.6-1810
- MYSQL
- Apache
- No iRedMail-Pro
- ====

I performed a yum update of the operating system. Now iRedMail is broken. I cannot send or receive email. I can login to roundcube and view email so Dovecot appears fine. Errors are below. It appears postfix or some connectivity to mysql is broken.


Jan 15 21:22:38 mission postfix/smtpd[16259]: connect from mail-ot1-f49.google.com[209.85.210.49]
Jan 15 21:22:38 mission postfix/trivial-rewrite[16264]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf lookup error for "*"
Jan 15 21:22:38 mission postfix/trivial-rewrite[16264]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf lookup error for "*"
Jan 15 21:22:38 mission postfix/trivial-rewrite[16264]: warning: proxy:mysql:/etc/postfix/mysql/relay_domains.cf: table lookup problem
Jan 15 21:22:38 mission postfix/trivial-rewrite[16264]: warning: relay_domains lookup failure
Jan 15 21:22:38 mission postfix/trivial-rewrite[16264]: warning: proxy:mysql:/etc/postfix/mysql/relay_domains.cf: table lookup problem
Jan 15 21:22:38 mission postfix/trivial-rewrite[16264]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf lookup error for "myuser@mydomain.org"
Jan 15 21:22:38 mission postfix/trivial-rewrite[16264]: warning: transport_maps lookup failure
Jan 15 21:22:38 mission postfix/smtpd[16259]: NOQUEUE: reject: RCPT from mail-ot1-f49.google.com[209.85.210.49]: 451 4.3.0 <otheruser@otherdomain.org>: Temporary lookup failure; from=<otheruser@otherdomain.org> to=<myuser@mydomain.org> proto=ESMTP helo=<mail-ot1-f49.google.com>
Jan 15 21:22:39 mission postfix/smtpd[16259]: disconnect from mail-ot1-f49.google.com[209.85.210.49]
Jan 15 21:24:03 mission postfix/submission/smtpd[16287]: connect from localhost[127.0.0.1]
Jan 15 21:24:03 mission postfix/trivial-rewrite[16264]: warning: proxy:mysql:/etc/postfix/mysql/relay_domains.cf: table lookup problem
Jan 15 21:24:03 mission postfix/trivial-rewrite[16264]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf lookup error for "myuser@mydomain.org"
Jan 15 21:24:03 mission postfix/trivial-rewrite[16264]: warning: transport_maps lookup failure
Jan 15 21:24:03 mission postfix/trivial-rewrite[16264]: warning: proxy:mysql:/etc/postfix/mysql/relay_domains.cf: table lookup problem
Jan 15 21:24:03 mission postfix/trivial-rewrite[16264]: warning: relay_domains lookup failure
Jan 15 21:24:03 mission postfix/submission/smtpd[16287]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 451 4.3.0 <myuser@mydomain.org>: Temporary lookup failure; from=<myuser@mydomain.org> to=<otheruser@otherdomain.org> proto=ESMTP helo=<myiredmailsvr.mydomain.tld>
Jan 15 21:24:03 mission roundcube: <di1feucc> SMTP Error: Failed to add recipient 'otheruser@otherdomain.org'. 4.3.0 <myuser@mydomain.org>: Temporary lookup failure (Code: 451) in /var/www/roundcubemail-1.1.3/program/lib/Roundcube/rcube.php on line 1708 (POST /mail/?_task=mail&_unlock=loading1547616243544&_lang=en_US&_framed=1?_task=mail&_action=send)
Jan 15 21:24:03 mission postfix/submission/smtpd[16287]: disconnect from localhost[127.0.0.1]

Jan 15 21:25:55 mission postfix/postscreen[16312]: CONNECT from [112.113.118.39]:56202 to [ip.ip.ip.ip]:25
Jan 15 21:25:58 mission postfix/postscreen[16312]: CONNECT from [112.113.118.39]:56231 to [ip.ip.ip.ip]:25
Jan 15 21:25:59 mission postfix/anvil[16261]: statistics: max connection rate 1/60s for (smtpd:209.85.210.49) at Jan 15 21:22:38
Jan 15 21:25:59 mission postfix/anvil[16261]: statistics: max connection count 1 for (smtpd:209.85.210.49) at Jan 15 21:22:38
Jan 15 21:25:59 mission postfix/anvil[16261]: statistics: max cache size 1 at Jan 15 21:22:38
Jan 15 21:26:01 mission postfix/postscreen[16312]: PASS NEW [112.113.118.39]:56202
Jan 15 21:26:04 mission postfix/postscreen[16312]: PASS NEW [112.113.118.39]:56231
Jan 15 21:26:12 mission postfix/smtpd[16325]: connect from unknown[112.113.118.39]
Jan 15 21:26:12 mission postfix/trivial-rewrite[16333]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf lookup error for "*"
Jan 15 21:26:12 mission postfix/trivial-rewrite[16333]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf lookup error for "*"
Jan 15 21:26:12 mission postfix/trivial-rewrite[16333]: warning: proxy:mysql:/etc/postfix/mysql/relay_domains.cf: table lookup problem
Jan 15 21:26:12 mission postfix/trivial-rewrite[16333]: warning: relay_domains lookup failure
Jan 15 21:26:13 mission postfix/trivial-rewrite[16333]: warning: proxy:mysql:/etc/postfix/mysql/relay_domains.cf: table lookup problem
Jan 15 21:26:13 mission postfix/trivial-rewrite[16333]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf lookup error for "user2@mydomain.org"
Jan 15 21:26:13 mission postfix/trivial-rewrite[16333]: warning: transport_maps lookup failure
Jan 15 21:26:13 mission postfix/smtpd[16325]: NOQUEUE: reject: RCPT from unknown[112.113.118.39]: 451 4.3.0 <1073408586@qq.com>: Temporary lookup failure; from=<1073408586@qq.com> to=<user2@mydomain.org> proto=SMTP helo=<wximv.com>
Jan 15 21:26:14 mission postfix/smtpd[16325]: lost connection after RCPT from unknown[112.113.118.39]

-----------------------------------

Additional information. The yum update of the OS from C7.2 to C7.6 was a precursor to performing the sequential upgrade processes from iRedMail 0.9.3 to 0.9.9. When iRedMail/Postfix became broken (see original post detail) I felt it is was unwise to proceed through the 0.9.3->0.9.9 upgrade processes with a broken Postfix.

My iRedMail is tarball based, not package based so the yum update shouldn't have upgraded anything that would've broken the config. I did notice that after the upgrade the contents of /etc/postfix/mysql/*.cf had all been overwritten with new versions. I do not know if there was some special iRedMail customization in those .cf files.

I was able to login to mysql and view the vmail database so the mysql backend appears to be functional.

Any advice on how to get CentOS updated without blowing up iRedMail?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 (edited by echo5 2019-01-17 09:15:49)

Re: CentOS7 update broke iRedMail 0.9.3

* * APPARENT FIX * *

In case anyone else comes across this issue..

As part of some system tune ups I performed a yum update of CentOS and I cleaned up some config files. I edited /etc/hosts and added a list fo hosts that included the iRedMail hostname and IP. This fouled the postfix/mysql connection even though the config files are all set to use 127.0.0.1. My guess is that someplace in a script the fqdn of the iRedMail host is referenced and it pointed to the public IP instead of 127.0.0.1.

Once I removed the entries in /etc/hosts everything appeared to work as it should.