Forum Discussion
External Mail address is being changed while processed from EOP to internal Zimbra Server.
Co-existence Scenario: Actually I have a Zimbra mail server and office365. All the mail flow is through the Exchange connector. Till 4th March 2020, I have no issue with mail flow between office365 ...
If you're having trouble receiving mail from outside, you need to find out where the message is failing.
When sending your text message, check the, especially /var/log/zimbra.log, on your MTA server.
It's often helpful to tail the logfile as you send the message:
tail -f /var/log/zimbra.log
If you see nothing logged (no connection, nothing) then the problem likely either DNS or your firewall.
It will help to migrate Zimbra to Office 365. If there is a line in the /var/log/zimbra.log like:
postfix/lmtp ... deferred ... connection refused
There is no connection to port 7025 to perform Local Mail Transfer Protocol (LMTP) delivery.
This is nearly always caused by a host that is configured on private IP Space (or using NAT) and that does not have an interface for the public IP address the server resides on. This can be easily fixed by simply using native IP address lookups for lmtp rather than DNS. Alternatively, you could have your internal network's domain name configured to lookup differently internally than it does externally. Using that method is beyond the scope of this document.
Hi Lewis-H,
As per the last logs, I can clearly see there has been a change in the method of sending emails from office 365 to Zimbra. Due to this alteration, Zimbra’s Anti-spam is rejecting email considering it as a Spoof email ( you can see on a log that it is redirecting as a client domain instead of. Hence if you can just make us clarification on if there is any kind of changes on Exchange online routing.
Here I received the email in Zimbra too but just don't know why it is redirecting?
