zimbra mailserver - mail for 192.168.0.1 loops back to myself
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
zimbra mailserver - mail for 192.168.0.1 loops back to myself
A Zimbra mailserver is installed on a system with IP address local ip address 192.168.0.1 and its SMTP port is 26. Another, System Postfix is running on the same ip address but using port 25 for SMTP. I have set the "Relay MTA for external Delivery" in the Zimbra Admin Web Console the IP address as 192.168.0.1 and port 25. On doing so, Zimbra logs
Quote:
to=<foo@external-domain.com>, relay=none, delay=550, delays=550/0.04/0/0, dsn=4.3.5, status=deferred (mail for 192.168.0.1 loops back to myself)
Is there a way, relaying wherein we can relay to the same ip but on different port?
What is the point of having two MTAs on the same server? You're making your life more complicated than it needs to be, Zimbra will deliver the mail directly, why aren't you doing that? BTW, the reason you're having a problem is most likely the fact you have a DNS A & MX record pointing back to your LAN IP address.
What is the point of having two MTAs on the same server? You're making your life more complicated than it needs to be, Zimbra will deliver the mail directly, why aren't you doing that?
There are some third party modules I would be using, like AV scanning and other security modules, before the mails being delivered to Zimbra. Basically, these modules would be at the Gateway level port i.e. the default SMTP port 25 for accepting email.
Quote:
Originally Posted by fenice
BTW, the reason you're having a problem is most likely the fact you have a DNS A & MX record pointing back to your LAN IP address.
That's correct. Tried to change the "inet_interface" to a specific ip address, but that caused problems in zimbra's other service.
Zimbra already has good a/v scanning, I've never seen any problems with it in the 10 years I've used it. In any case, if you want to run a gateway server for your mail the I'd suggest you use an additional server such as Email Filter Applianceor one of the many (free) gateway appliances and run it on a completely different server and obviously with a different IP..
Please do bear with me for the delay in my reply, cuz was buzy with some other assignement.
I would Thank all our Members for their replies and valuable suggestions.
Basically, nothing to worry as mine is a Test environment. Its better not to touch .. agreeing to one of our member who emailed me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
agreeing to one of our member who emailed me.
