Deferred queue filling up after some Firewall issues

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Labsy
Outstanding Member
Outstanding Member
Posts: 380
Joined: Sat Sep 13, 2014 12:52 am

Deferred queue filling up after some Firewall issues

Postby Labsy » Mon Nov 11, 2019 10:58 am

Hi,

I am looking for ideas how to solve my situation.
Yesterday we've tried to upgrade (separate) firewall in front of Zimbra server, but after quite some issues with newer Firewall firmware (could not PING, DNs not resolving...) we decided to go back to original firmware. During the upgrade and reversal process, like 2-3 hours, Zimbra server had (of course) problems with connectivity. But we reverted to old, working firewall, and everything should be like before...
...but it's not!
Ever since we begin playing with firewall, Zimbra server begun filling deferred queue for all INCOMING messages.
While OUTGOING mail passes fine, INCOMING have problems - they are not refused, but stuck within deferred queue and NOT delivered to inbox. I can see this in Admin GUI:

Sender: somebody@gmail.com
From host: localhost.localdomain
From domain: gmail.com
Reason: Connect to server zimbra.myserver.com [1.2.3.4]:7025 connection timeout

Sender: customer@myserver.com
From host: localhost.localdomain
From domain: myserver.com
Reason: Delivery temoporarily suspended. Connect to server zimbra.myserver.com [1.2.3.4]:7025 connection timeout

We did not changed ANYTHING on zimbra server in last few months.
We did not touch Zimbra server.
Where is this localhost.localdomain comming from?
Is it OK to try delivering to port 7025?
Why is every incoming mail suspended?


Labsy
Outstanding Member
Outstanding Member
Posts: 380
Joined: Sat Sep 13, 2014 12:52 am

Re: Deferred queue filling up after some Firewall issues

Postby Labsy » Mon Nov 11, 2019 12:34 pm

Weird... I had to change local LMTP lookup from "DNS" to "native" and woila!...all Deferred queue got soaked up by proper mailboxes, all messages received, queue is now empty.
Wondering, how the hack could it run fine until today? 10 years on "DNS" settings, now all of the sudden needs "native" to work?! Weird:

As zimbra user, first lookup the values in server config and global.
Both were set to "dns", so I switched them over to "native":

Code: Select all

zmprov getserver zimbra.myserver.com zimbraMtaLmtpHostLookup
zmprov getconfig zimbraMtaLmtpHostLookup

zmprov ms zimbra.myserver.com zimbraMtaLmtpHostLookup native
zmprov mcf zimbraMtaLmtpHostLookup native

zmmtactl restart

Return to “Administrators”

Who is online

Users browsing this forum: Majestic-12 [Bot], MSN [Bot] and 13 guests