[RESOLVED] Mails do get stuck in deferred queue Temporary MTA failure on relaying[resolved]

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
v1rtu4l
Posts: 36
Joined: Tue Jun 28, 2016 3:04 pm

[RESOLVED] Mails do get stuck in deferred queue Temporary MTA failure on relaying[resolved]

Postby v1rtu4l » Tue Jul 05, 2016 10:57 am

Hi Guys,

right now we got a symptom that i have read quite a few times on several sites on the internet already (when googling for the error). If i send a mail via web client to another internal user (or external user) the mail will not get delivered, but get stuck in the deferred queue. If i choose to requeue the mail it will get delivered properly, but of course i can't monitor the deferred queue all day for this to be delivered properly

the corresponding error in zimbra.log is:

Code: Select all

Jul  5 12:40:36 mail postfix/smtp[1179]: DCB81342C0E: to=<myuser@mydomain.de>, relay=127.0.0.1[127.0.0.1]:10026, delay=0.17, delays=0.02/0.02/0/0.12, dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 id=16723-05 - Temporary MTA failure on relaying, From MTA() during fwd-connect (Negative greeting: 554 5.7.1 <localhost[127.0.0.1]>: Client host rejected: Access denied): id=16723-05 (in reply to end of DATA command))

the mailbox.log does not show any error nor warning for the time of this event.

Our setup is a very simple one. Just one server that hosts several (5) domains. I guess that the error popped up after i changed the MTA networks via admin GUI.
My understanding is, that the MTA trusted networks in the GUI will add the IP-Addresses and networks i add there to the zimbraMtaMyNetworks parameter but if i understand it correct it always also adds 127.0.0.1/8 to it if you change it via Web Admin Gui.

My setting right now is only two networks, basically 192.168.0.0/24 and 192.168.3.0/24. The first one being the subnet the mail server itself is part of, the other one is a separate network i want to relay from (but that is not really crucial and could be deleted).

the output of zmprov gd zimbraMtaMyNetworks shows only those two mentioned ip networks and not the 127.0.0.1/8

btw: https://www.jorgedelacruz.es/2014/07/21 ... -beta-iii/
this does not solve the problem
neither does the solution here http://ubuntuforums.org/showthread.php?t=2173036


which logs can i try to use to troubleshoot this issue ?

//EDIT//
after adding 127.0.0.1/8 to my MTA Networks the error message changed to "connection refused"

Code: Select all

Jul  5 13:52:31 mail zmconfigd[34910]: All rewrite threads completed in 0.00 sec
Jul  5 13:52:31 mail zmconfigd[34910]: All restarts completed in 0.00 sec
Jul  5 13:52:35 mail slapd[34890]: slap_queue_csn: queueing 0x73bd680 20160705115235.372453Z#000000#000#000000
Jul  5 13:52:35 mail slapd[34890]: slap_graduate_commit_csn: removing 0x73bd680 20160705115235.372453Z#000000#000#000000
Jul  5 13:52:47 mail postfix/postscreen[53042]: CONNECT from [192.168.0.190]:53603 to [192.168.0.190]:25
Jul  5 13:52:47 mail postfix/postscreen[53042]: WHITELISTED [192.168.0.190]:53603
Jul  5 13:52:47 mail postfix/smtpd[53043]: connect from mail.mydom.local[192.168.0.190]
Jul  5 13:52:48 mail postfix/smtpd[53043]: NOQUEUE: filter: RCPT from mail.mydom.local[192.168.0.190]: <extuser1@external.com>: Sender address triggers FILTER smtp-amavis:[127.0.0.1]:10026; from=<extuser1@external.com> to=<Administrator@internal.lan> proto=ESMTP helo=<mail.mydom.local>
Jul  5 13:52:48 mail postfix/smtpd[53043]: 056B0342C0E: client=mail.mydom.local[192.168.0.190]
Jul  5 13:52:48 mail postfix/cleanup[53046]: 056B0342C0E: message-id=<742982441.3.1467719567707.JavaMail.zimbra@external.com>
Jul  5 13:52:48 mail postfix/qmgr[37521]: 056B0342C0E: from=<extuser1@external.com>, size=2932, nrcpt=1 (queue active)
Jul  5 13:52:48 mail postfix/smtpd[53043]: disconnect from mail.mydom.local[192.168.0.190] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Jul  5 13:52:48 mail amavis[36847]: (36847-03) ESMTP [127.0.0.1]:10026 /opt/zimbra/data/amavisd/tmp/amavis-20160705T133018-36847-zF0KG_zM: <extuser1@external.com> -> <administrator@internal.lan> Received: from mx.scngmbh.eu ([127.0.0.1]) by localhost (mail.mydom.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP for <administrator@internal.lan>; Tue,  5 Jul 2016 13:52:48 +0200 (CEST)
Jul  5 13:52:48 mail amavis[36847]: (36847-03) Checking: pOunmJX9EPTZ ORIGINATING/MYNETS [192.168.0.190] <extuser1@external.com> -> <administrator@internal.lan>
Jul  5 13:52:48 mail postfix/dkimmilter/smtpd[53049]: connect from localhost[127.0.0.1]
Jul  5 13:52:48 mail postfix/dkimmilter/smtpd[53049]: warning: smtpd_client_event_limit_exceptions: non-null host address bits in "127.0.0.1/8", perhaps you should use "127.0.0.0/8" instead
Jul  5 13:52:48 mail postfix/dkimmilter/smtpd[53049]: warning: mynetworks: non-null host address bits in "127.0.0.1/8", perhaps you should use "127.0.0.0/8" instead
Jul  5 13:52:48 mail postfix/dkimmilter/smtpd[53049]: NOQUEUE: reject: CONNECT from localhost[127.0.0.1]: 451 4.3.0 <localhost[127.0.0.1]>: Temporary lookup failure; proto=SMTP
Jul  5 13:52:48 mail postfix/dkimmilter/smtpd[53049]: warning: smtpd_client_event_limit_exceptions: non-null host address bits in "127.0.0.1/8", perhaps you should use "127.0.0.0/8" instead
Jul  5 13:52:48 mail amavis[36847]: (36847-03) (!)pOunmJX9EPTZ FWD from <extuser1@external.com> -> <administrator@internal.lan>,  451 4.5.0 From MTA() during fwd-connect (Negative greeting: 451 4.3.0 <localhost[127.0.0.1]>: Temporary lookup failure): id=36847-03
Jul  5 13:52:48 mail postfix/dkimmilter/smtpd[53049]: lost connection after CONNECT from localhost[127.0.0.1]
Jul  5 13:52:48 mail postfix/dkimmilter/smtpd[53049]: disconnect from localhost[127.0.0.1] commands=0/0
Jul  5 13:52:48 mail amavis[36847]: (36847-03) Blocked MTA-BLOCKED {TempFailedInternal}, ORIGINATING/MYNETS LOCAL [192.168.0.190]:53603 <extuser1@external.com> -> <administrator@internal.lan>, Queue-ID: 056B0342C0E, Message-ID: <742982441.3.1467719567707.JavaMail.zimbra@external.com>, mail_id: pOunmJX9EPTZ, Hits: -, size: 2932, 126 ms
Jul  5 13:52:48 mail postfix/smtp[53047]: 056B0342C0E: to=<administrator@internal.lan>, relay=127.0.0.1[127.0.0.1]:10026, delay=0.18, delays=0.03/0.02/0/0.12, dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 id=36847-03 - Temporary MTA failure on relaying, From MTA() during fwd-connect (Negative greeting: 451 4.3.0 <localhost[127.0.0.1]>: Temporary lookup failure): id=36847-03 (in reply to end of DATA command))


seeing the warning regarding the 127.0.0.1/8, i changed it to 127.0.0.0/8, but still getting the "connection refused" on every mail.

after a zmcontrol restart things are ok again and everything gets delivered as expected:

TLDR; changed zimbraMtaMyNetworks to not include 127.0.0.0/8 and relaying stopped working, because amavis-d got an error, requeuing the mails did get them delivered. adding 127.0.0.1/8 did give a different error with same symptoms and finally changing it to 127.0.0.0/8 and restarting the zimbra servers remediated the situation.


qadir52786
Posts: 40
Joined: Sat Sep 13, 2014 3:58 am

Re: Mails do get stuck in deferred queue Temporary MTA failure on relaying[resolved]

Postby qadir52786 » Wed Oct 10, 2018 1:13 pm

Facing same issue after changing server ip address


Please update if any one have solution for this


Thank you
User avatar
L. Mark Stone
Elite member
Elite member
Posts: 1864
Joined: Wed Oct 09, 2013 11:35 am
Location: Portland, Maine
ZCS/ZD Version: 8.8.8 Patch 6 Network Edition
Contact:

Re: Mails do get stuck in deferred queue Temporary MTA failure on relaying[resolved]

Postby L. Mark Stone » Wed Oct 10, 2018 3:41 pm

qadir52786 wrote:Facing same issue after changing server ip address


Please update if any one have solution for this


Thank you


You don't say how you made the IP address change, but a Zimbra server's IP address is used in a variety of places. If you are having mail deferred issues, I would to see if you updated zimbraMtaMyNetworks?

Code: Select all

zmprov gs `zmhostname` zimbraMtaMyNetworks

Let us know?
Mark
___________________________________
L. Mark Stone
Mission Critical Email - Zimbra VAR/BSP/Training Partner https://www.missioncriticalemail.com/
Zeta Alliance http://www.zetalliance.org/
qadir52786
Posts: 40
Joined: Sat Sep 13, 2014 3:58 am

Re: Mails do get stuck in deferred queue Temporary MTA failure on relaying[resolved]

Postby qadir52786 » Fri Oct 12, 2018 3:09 pm

[zimbra@mail root]$ zmprov gs `zmhostname` zimbraMtaMyNetworks
# name mydomain.com
zimbraMtaMyNetworks: 192.168.2.0/24
the above is the same ip that i had change

right now when i send mail its got in to deferred when i do re-queue it got deliver .error shows like follows

host 127.0.0.1[127.0.0.1]said 451 4.5.0 id=31197-17 temporary mta failure on relaying mta() during frw-connect (negative greetings: 554 5.7.1 <lovalhost[127.0.0.1]> client host rejected : access deny) id=31197-17(in reply to end of command )


L. Mark Stone wrote:
qadir52786 wrote:Facing same issue after changing server ip address


Please update if any one have solution for this


Thank you


You don't say how you made the IP address change, but a Zimbra server's IP address is used in a variety of places. If you are having mail deferred issues, I would to see if you updated zimbraMtaMyNetworks?

Code: Select all

zmprov gs `zmhostname` zimbraMtaMyNetworks

Let us know?
Mark
qadir52786
Posts: 40
Joined: Sat Sep 13, 2014 3:58 am

Re: Mails do get stuck in deferred queue Temporary MTA failure on relaying[resolved]

Postby qadir52786 » Fri Oct 12, 2018 3:09 pm

[zimbra@mail root]$ zmprov gs `zmhostname` zimbraMtaMyNetworks
# name mydomain.com
zimbraMtaMyNetworks: 192.168.2.0/24
the above is the same ip that i had change

right now when i send mail its got in to deferred when i do re-queue it got deliver .error shows like follows

host 127.0.0.1[127.0.0.1]said 451 4.5.0 id=31197-17 temporary mta failure on relaying mta() during frw-connect (negative greetings: 554 5.7.1 <lovalhost[127.0.0.1]> client host rejected : access deny) id=31197-17(in reply to end of command )


L. Mark Stone wrote:
qadir52786 wrote:Facing same issue after changing server ip address


Please update if any one have solution for this


Thank you


You don't say how you made the IP address change, but a Zimbra server's IP address is used in a variety of places. If you are having mail deferred issues, I would to see if you updated zimbraMtaMyNetworks?

Code: Select all

zmprov gs `zmhostname` zimbraMtaMyNetworks

Let us know?
Mark
User avatar
DualBoot
Outstanding Member
Outstanding Member
Posts: 768
Joined: Mon Apr 18, 2016 8:18 pm
Location: Earth
ZCS/ZD Version: ZCS FLOSS - 8.7.11 Mutli servers

Re: Mails do get stuck in deferred queue Temporary MTA failure on relaying[resolved]

Postby DualBoot » Mon Oct 15, 2018 9:16 am

Hello,

127.0.0.1 is missing in the allow networks.

Regards,
phoenix
Ambassador
Ambassador
Posts: 25718
Joined: Fri Sep 12, 2014 9:56 pm

Re: Mails do get stuck in deferred queue Temporary MTA failure on relaying[resolved]

Postby phoenix » Mon Oct 15, 2018 10:00 am

qadir52786 wrote:host 127.0.0.1[127.0.0.1]said 451 4.5.0 id=31197-17 temporary mta failure on relaying mta() during frw-connect (negative greetings: 554 5.7.1 <localhost[127.0.0.1]> client host rejected : access deny) id=31197-17(in reply to end of command )
See the comment above from DualBoot, it's mentioned in the error message. I guess at some point you've removed that IP fro the Trusted Networks and it's caused this problem.
Regards

Bill

Rspamd: A high performance spamassassin replacement

If you'd like to see this implemented in a future version of ZCS then please vote on Bugzilla entries 97706 & 108168
qadir52786
Posts: 40
Joined: Sat Sep 13, 2014 3:58 am

Re: Mails do get stuck in deferred queue Temporary MTA failure on relaying[resolved]

Postby qadir52786 » Mon Oct 15, 2018 1:30 pm

phoenix wrote:
qadir52786 wrote:host 127.0.0.1[127.0.0.1]said 451 4.5.0 id=31197-17 temporary mta failure on relaying mta() during frw-connect (negative greetings: 554 5.7.1 <localhost[127.0.0.1]> client host rejected : access deny) id=31197-17(in reply to end of command )
See the comment above from DualBoot, it's mentioned in the error message. I guess at some point you've removed that IP fro the Trusted Networks and it's caused this problem.



How to solve that problem sir ...
phoenix
Ambassador
Ambassador
Posts: 25718
Joined: Fri Sep 12, 2014 9:56 pm

Re: Mails do get stuck in deferred queue Temporary MTA failure on relaying[resolved]

Postby phoenix » Mon Oct 15, 2018 1:33 pm

Why did you remove it in the first place (it is always enabled by default)? An internet search works wonders for most problems: https://www.startpage.com/do/dsearch?query=%2B%22zcs+%2B%22trusted+networks%22+%2Bmodify&cat=web&pl=opensearch&language=english
Regards

Bill

Rspamd: A high performance spamassassin replacement

If you'd like to see this implemented in a future version of ZCS then please vote on Bugzilla entries 97706 & 108168
qadir52786
Posts: 40
Joined: Sat Sep 13, 2014 3:58 am

Re: Mails do get stuck in deferred queue Temporary MTA failure on relaying[resolved]

Postby qadir52786 » Mon Oct 15, 2018 4:04 pm

phoenix wrote:Why did you remove it in the first place (it is always enabled by default)? An internet search works wonders for most problems: https://www.startpage.com/do/dsearch?query=%2B%22zcs+%2B%22trusted+networks%22+%2Bmodify&cat=web&pl=opensearch&language=english



Thanks a lot sir ... problem resolve ..


Thank you all ..

Return to “Administrators”

Who is online

Users browsing this forum: Baidu [Spider] and 28 guests