Blocked MTA-BLOCKED {TempFailedInbound} After Upgrade of Ubuntu to 22.04

Discussion in 'Installation/Configuration' started by jaypabs, Nov 29, 2022.

  1. jaypabs

    jaypabs Member

    After an upgrade of my server 2 I cannot send email on it. In server 1, it still works fine.
    Here's the error message when I run this command
    # service amavis status

    Code:
    Nov 29 21:07:12 server2 amavis[79365]: (79365-06) (!)rw_loop: leaving rw loop, no progress, last event (select) 35.035 s ago
    Nov 29 21:07:12 server2 amavis[79365]: (79365-06) (!)mxjtSob_KOvs FWD from <[email protected]> -> <[email protected]>,  451 4.5.0 From MTA() during fwd-connect (No greeting, dt: 35.036 s): id=79365-06
    Nov 29 21:07:12 server2 amavis[79365]: (79365-06) Blocked MTA-BLOCKED {TempFailedInbound}, [127.0.0.1] <[email protected]> -> <[email protected]>, Message-ID: <[email protected]>, mail_id: mxjtSob_KOvs, Hits: 2.753, size: 687, 35205 ms
    
    Error message from /var/log/mail.log:
    Code:
    Nov 29 21:14:37 server2 postfix/master[79909]: warning: process /usr/lib/postfix/sbin/smtpd pid 85755 exit status 1
    Nov 29 21:14:37 server2 postfix/master[79909]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling
    Nov 29 21:14:37 server2 amavis[79958]: (79958-03) (!)kJPKOY0oFHtq FWD from <[email protected]> -> <[email protected]>,  451 4.5.0 From MTA() during fwd-connect (No greeting, dt: 1.019 s): id=79958-03
    Nov 29 21:14:37 server2 amavis[79958]: (79958-03) Blocked MTA-BLOCKED {TempFailedInbound}, [127.0.0.1] <[email protected]> -> <[email protected]>, Message-ID: <[email protected]>, mail_id: kJPKOY0oFHtq, Hits: -0.001, size: 460, 1452 ms
    Nov 29 21:14:37 server2 postfix/lmtp[85749]: 112117C06EB: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.9, delays=0.39/0.02/0/1.5, dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 id=79958-03 - Temporary MTA failure on relaying, From MTA() during fwd-connect (No greeting, dt: 1.019 s): id=79958-03 (in reply to end of DATA command))
    
    In Ubuntu 20.04, I don't remember I setup anything in Amavis. Now, in Ubuntu 22.04, I think Amavis is the one causing this problem. But I don't know where to fix it.
    Any help is highly appreciated.
    Thanks
     
  2. pyte

    pyte Well-Known Member HowtoForge Supporter

    Your postfix is not working correctly.
    Check the status of postfix and have a look around the logs for "error" and "fatal" messages.
     
  3. jaypabs

    jaypabs Member

    Thanks for the reply. Here's the error message in /var/log/mail. Err:
    Code:
    Nov 29 21:47:10 server2 postfix/smtps/smtpd[100743]: fatal: no SASL authentication mechanisms
    Nov 29 21:47:11 server2 postfix/smtpd[102045]: fatal: no SASL authentication mechanisms
    I'm using sendinblue to send email. Don't know what I'm missing.
     
  4. jaypabs

    jaypabs Member

    Here's an additional error messages:
    Code:
    Nov 29 21:54:49 server2 postfix/smtpd[107134]: warning: SASL: Connect to private/auth failed: Connection refused
    Nov 29 21:54:49 server2 postfix/smtpd[107134]: fatal: no SASL authentication mechanisms
    Nov 29 21:54:50 server2 postfix/master[106512]: warning: process /usr/lib/postfix/sbin/smtpd pid 107131 exit status 1
    Nov 29 21:54:50 server2 postfix/master[106512]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling
    Nov 29 21:54:50 server2 postfix/master[106512]: warning: process /usr/lib/postfix/sbin/smtpd pid 107132 exit status 1
    
    It says bad command startup -- throttling.
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    Most likely dovecot has not been started as the authentication from postfix is handled by dovecot.
     
    pyte likes this.
  6. jaypabs

    jaypabs Member

    I have already restart dovecot, as well as amavis and postfix. Anything I'm still missing?
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you run an ispconfig update with reconfigure services as required after upgrading OS to Ubuntu 22.04?
     
  8. jaypabs

    jaypabs Member

    Oh, I did not. Let me run it and update you as soon as I finished updating it.
     
  9. jaypabs

    jaypabs Member

    @till
    The error is gone. And it seems it is sending correctly. Except that the email did not arrive on my mailbox.
    Please see log below:
    Code:
    Nov 29 22:36:20 server2 postfix/pickup[128101]: AF9BF7C0648: uid=5008 from=<[email protected]>
    Nov 29 22:36:20 server2 postfix/cleanup[131709]: AF9BF7C0648: message-id=<[email protected]>
    Nov 29 22:36:20 server2 postfix/qmgr[128102]: AF9BF7C0648: from=<[email protected]>, size=690, nrcpt=1 (queue active)
    Nov 29 22:36:21 server2 postfix/smtpd[129265]: connect from localhost[127.0.0.1]
    Nov 29 22:36:21 server2 postfix/smtpd[129265]: 07A8E7C02A0: client=localhost[127.0.0.1]
    Nov 29 22:36:21 server2 postfix/cleanup[131709]: 07A8E7C02A0: message-id=<[email protected]>
    Nov 29 22:36:21 server2 postfix/smtpd[129265]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
    Nov 29 22:36:21 server2 amavis[128201]: (128201-10) Passed CLEAN {RelayedInbound}, [127.0.0.1] <[email protected]> -> <[email protected]>, Message-ID: <[email protected]>, mail_id: 96XH5ZCVm2wp, Hits: 2.753, size: 690, queued_as: 07A8E7C02A0, 314 ms
    Nov 29 22:36:21 server2 postfix/lmtp[131712]: AF9BF7C0648: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.38, delays=0.06/0/0/0.31, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 07A8E7C02A0)
    Nov 29 22:36:21 server2 postfix/qmgr[128102]: 07A8E7C02A0: from=<[email protected]>, size=1426, nrcpt=1 (queue active)
    Nov 29 22:36:21 server2 postfix/qmgr[128102]: AF9BF7C0648: removed
    Nov 29 22:36:21 server2 dovecot: lmtp(132266): Connect from local
    Nov 29 22:36:21 server2 dovecot: lmtp([email protected])<132266><h6iZBuUYhmOqBAIAE5g4ZQ>: sieve: msgid=<[email protected]>: stored mail into mailbox 'INBOX'
    Nov 29 22:36:21 server2 dovecot: lmtp(132266): Disconnect from local: Logged out (state=READY)
    Nov 29 22:36:21 server2 postfix/lmtp[131712]: 07A8E7C02A0: to=<[email protected]>, relay=server2.mydomain.com[private/dovecot-lmtp], delay=0.11, delays=0.05/0.02/0.02/0.03, dsn=2.0.0, status=sent (250 2.0.0 <[email protected]> h6iZBuUYhmOqBAIAE5g4ZQ Saved)
    Nov 29 22:36:21 server2 postfix/qmgr[128102]: 07A8E7C02A0: removed
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    The mail has been sent and is stored in the mailbox according to the log. Check your spam folder and other filters that you might have set up to move or filter that mail.
     
  11. jaypabs

    jaypabs Member

    When I send a test mail to my gmail account. The mail delivered correctly. But it does not deliver on my email hosted on this server.
     
  12. till

    till Super Moderator Staff Member ISPConfig Developer

    The email was received in your inbox, see line "sieve: msgid=<[email protected]>: stored mail into mailbox 'INBOX'"
     
  13. jaypabs

    jaypabs Member

    I think the mail did not synchronize on my database. I am sending this email on my server 2.
    How do I know that the mail synchronize on server 1? Where can I find this in the database?
     
  14. till

    till Super Moderator Staff Member ISPConfig Developer

    That#s not in ISPConfig database, ISPConfig is not the software that syncs emails. If you sync mails, then you must have set up some config in dovecot to do this via dsync or use software like unison to sync the files or use a shared filesystem, there are many ways to do that.
     
  15. jaypabs

    jaypabs Member

    Thanks a lot. At last I fixed it!
     

Share This Page