Topic: Double-bounce from my secondary MX record
==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.4.2 MARIADB edition.
- Deployed with iRedMail Easy or the downloadable installer? downloadable
- Linux/BSD distribution name and version: Rocky Linux 8
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
Our iRedMail server is our primary mx record for our email. Of course, we have a secondary server that can accept mail if iRedmail is down/busy. iRedMail has decided it does not like our email server that is the secondary MX. We constantly get a "double-bounce" error if the secondary MX server tries to connect to the iRedMail server. I've whitelisted for greylisting. I've whitelisted for spam. What else do I need to whitelist to keep the iRedMail server from rejecting this mail? I want ALL mail from this server to be accepted regardless. After it's accepted, if Amavis thinks it's spam, etc. fine, but it at least needs to get into the processing queue.
Here is a portion of the maillog -
Jan 13 12:08:53 lochleven postfix/postscreen: CONNECT from [188.8.131.52]:59414 to [192.168.110.215]:25
Jan 13 12:08:53 lochleven postfix/postscreen: WHITELISTED [184.108.40.206]:59414
Jan 13 12:08:53 lochleven postfix/smtpd: connect from xeams.caledonia.net[220.127.116.11]
Jan 13 12:08:53 lochleven postfix/smtpd: discarding EHLO keywords: CHUNKING
Jan 13 12:08:53 lochleven postfix/smtpd: NOQUEUE: reject: RCPT from xeams.caledonia.net[18.104.22.168]: 550 5.1.0 <firstname.lastname@example.org>: Sender address rejected: User unknown; from=<email@example.com> to=<firstname.lastname@example.org> proto=ESMTP helo=<iris.caledonia.net>
Jan 13 12:08:53 lochleven postfix/smtpd: disconnect from xeams.caledonia.net[22.214.171.124] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5
this edited "validuser" can receive mail no problem if it comes directly to the iRedMail server as the primary MX, but going through the secondary fails!
According to the maillog, since January 9 we've had over 400 messages double-bounced like this - I need to figure this out ASAP. Thanks! I'll send multiple cups of coffee for this :-)