1 Topic by aegorov

  • aegorov
  • Member
  • Offline
  • Registered: 2018-11-14
  • Posts: 1

Topic: Error 5.4.12 iRedMail

Good day!

- iRedMail version (check /etc/iredmail-release):
postmaster@mail:~$ cat /etc/iredmail-release
0.9.5-1     # Get professional upgrade support from iRedMail Team: http://www.iredmail.org/support.html

- Linux/BSD distribution name and version:
Ubuntu 14.04.5 LTS (GNU/Linux 3.19.0-28-generic x86_64)

- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
postmaster@mail:~$  /usr/sbin/slapd -VV
@(#) $OpenLDAP: slapd  (Ubuntu) (May 31 2017 21:52:16) $
buildd@lgw01-30:/build/openldap-tnOaja/openldap-2.4.31/debian/build/servers/slapd

postmaster@mail:~$ mysql --version
mysql  Ver 14.14 Distrib 5.5.60, for debian-linux-gnu (x86_64) using readline 6.3

- Web server (Apache or Nginx):
postmaster@mail:~$ nginx -v
nginx version: nginx/1.4.6 (Ubuntu)

- Manage mail accounts with iRedAdmin-Pro?
No

Experiencing an issue:
Reporting-MTA: dns;Disel-exchange.DIESEL.local
Received-From-MTA: dns;email.pdmz.ru
Arrival-Date: Thu, 8 Nov 2018 08:59:07 +0000

Original-Recipient: rfc822;[user]@pdmz.ru
Final-Recipient: rfc822;[user]@pdmz.ru
Action: failed
Status: 5.4.12
Diagnostic-Code: smtp;554 5.4.12 SMTP; Hop count exceeded - possible mail loop detected on message id <!&!AAAAAAAAAAAuAAAAAAAAAIwcADdjaOZEh0OicggMnuIBAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAACWD5T0Kb0tSZSL6Yy1zwMDAQAAAAA=@prom-lk.ru>
Remote-MTA: dns;disel-exchange

How can we fix it? Materials to eliminate we could not find.
We found instructions on how to fix this at Exchange:
https://support.office.com/en-us/articl … 8b70cfd74b

How can this be done on an iRedMail?

----

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

2 Reply by swejun (edited by swejun 2018-11-15 18:13:23)

  • swejun
  • Member
  • Offline
  • Registered: 2017-07-26
  • Posts: 84

Re: Error 5.4.12 iRedMail

As far as I understand, this is an error on the RECEIVING END, (Exchange server) and not the SENDER. It's not that clear in the link You posted, I must admit.
The receving mailserver is an  MS-Exchange, and the on-line guide describes how to fix the problem in MS-Exchange.

You route all incoming mail for your hybrid domain through Exchange Online.  

This error can happen when the MX record for your hybrid domain points to Exchange Online, and the Outbound connector that's used to route mail to your on-premises Exchange organization is configured to use DNS routing.

To fix the problem, configure a dedicated Outbound connector that uses smart host routing and that has your on-premises hybrid server configured as a smart host. The easiest way to fix the problem is to re-run the Hybrid Configuration Wizard in the on-premises Exchange organization. Or, you can verify the configuration of the Outbound connector that's used for hybrid by following these steps:
...