This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

451 Error occurred forwarding data - Ony happens sending to Microfocus

Hello,

Can't answer to any emails from MicroFocus because SMG is always showing "451 Error occurred forwarding data", "Temporary failure sending message to : microfocus.com" and then error delivering emails.

Only to MicroFocus.

Anyone had something like this before?

Regards,

José Albuquerque

Tags:

  • 0  

    In my case it seems to work. I.e. to support.case@microfocus.com.

    SMG is responsible for inbound and outbound.


    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to   

    Happy new year.

    Still the same old same old....

    Recipient: support.case@microfocus.com
    Filter: Message Received
    Delivery Status: 451 Error occurred forwarding data
    Connection Status: Temporary failure sending message to : microfocus.com

    [139764627904256] 2023-01-02 08:41:16 (SMTP) Processing SMTP client connection from 10.166.11.32 (client count 1)
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> Client connected from known address (internal/trusted)
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> Processing connection from 10.166.11.32
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> Skipping connection drop tests for 10.166.11.32
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [g->c] 220 mail.montepio-rdl.pt
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [c->g] EHLO slmrdlvgw01.montepiordl.local
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [g->c] 250-mail.montepio-rdl.pt
    250-STARTTLS
    250 SIZE 40000000
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [c->g] STARTTLS
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [g->c] 220 Ready to start TLS
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> TLS negotiation successful, session is now encrypted [SSL:DHE-RSA-AES256-GCM-SHA384 256bit TLSv1.2]
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [c->g] EHLO slmrdlvgw01.montepiordl.local
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [g->c] 250-mail.montepio-rdl.pt
    250 SIZE 40000000
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [c->g] MAIL FROM:<jose.albuquerque@montepio-rdl.pt> SIZE=252087
    [139764627904256] 2023-01-02 08:41:16 Skip SPF check on private IP address: 10.166.11.32
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> SPF connection test for 10.166.11.32 passed
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [g->c] 250 Sender accepted
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [c->g] RCPT TO:<support.case@microfocus.com>
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> Validating RCPT address against target hosts
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> Requesting host connection
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> Creating new host server connection
    [139764627904256] 2023-01-02 08:41:16 (SRVS)<8891> Lookup MX record list for microfocus.com
    [139764636296960] 2023-01-02 08:41:16 (SMTP) Processing SMTP client connection from 10.166.11.32 (client count 2)
    [139764627904256] 2023-01-02 08:41:17 (SRVS)<8891> Inspecting MX record results
    [139764627904256] 2023-01-02 08:41:17 (SRVS)<8891> MX: smtp.ext.microfocus.com priority 1
    [139764627904256] 2023-01-02 08:41:17 (SRVS)<8891> MX lookup located 1 host
    [139764627904256] 2023-01-02 08:41:17 (SRVS)<8891> Computed SMTP host smtp.ext.microfocus.com
    [139764627904256] 2023-01-02 08:41:17 (SRVS)<8891> Connecting to SMTP host at smtp.ext.microfocus.com
    [139764627904256] 2023-01-02 08:41:17 (SRVS)<8891> Connection established with SMTP host smtp.ext.microfocus.com [129.84.8.96] [129.84.8.96] <fd:18>
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [s->g] 220 m9a0032g.houston.softwaregrp.com ESMTP
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [g->s] EHLO slmrdlvgw01.montepiordl.local
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [s->g] 250-m9a0032g.houston.softwaregrp.com
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [s->g] 250-STARTTLS
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [s->g] 250-SIZE 51200000
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [s->g] 250 m9a0032g.houston.softwaregrp.com
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [g->s] STARTTLS
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [s->g] 220 Ready to start TLS
    [139764627904256] 2023-01-02 08:41:18 (SRVS)<8891> TLS negotiation successful, session is now secure [SSL:ECDHE-RSA-AES256-GCM-SHA384 256bit TLSv1.2]
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [g->s] EHLO slmrdlvgw01.montepiordl.local
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [s->g] 250-m9a0032g.houston.softwaregrp.com
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [s->g] 250-SIZE 51200000
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [s->g] 250 m9a0032g.houston.softwaregrp.com
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [g->s] MAIL FROM:<jose.albuquerque@montepio-rdl.pt> SIZE=252087
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [s->g] 250 Sender accepted
    [139764627904256] 2023-01-02 08:41:18 (SMTP)<8891> [g->s] RCPT TO:<support.case@microfocus.com>
    [139764627904256] 2023-01-02 08:41:19 (SMTP)<8891> [s->g] 250 2.1.5 Recipient OK
    [139764627904256] 2023-01-02 08:41:19 (SMTP)<8891> [g->c] 250 2.1.5 Recipient OK
    [139764627904256] 2023-01-02 08:41:19 (SMTP)<8891> [c->g] DATA
    [139764627904256] 2023-01-02 08:41:19 (SMTP)<8891> [g->c] 354 Ready to receive data
    [139764627904256] 2023-01-02 08:41:19 (SMTP)<8891> Spooling inbound DATA to: /opt/microfocus/smg/smg-smtp/private/1_11010/temp/~3v3lufv5o0.hlv1hr565f24r400sd1afsh.tmp
    [139764627904256] 2023-01-02 08:41:19 (SMTP)<8891> Decoding inbound DATA to: /opt/microfocus/smg/smg-smtp/private/1_11010/temp/~3v3lufv5o0.hm01hr565f24r405gq9a87u.tmp
    [139764627904256] 2023-01-02 08:41:19 (SMTP)<8891> Data received (252111 bytes)
    [139764627904256] 2023-01-02 08:41:19 (CORE) Attempting to connect to GWAVA scan engine 'Message filter engine' at 10.166.12.1:4929
    [139764627904256] 2023-01-02 08:41:19 (CORE) Connection established to GWAVA scan engine 'Message filter engine' at 10.166.12.1:4929
    [139764627904256] 2023-01-02 08:41:19 (CONN)<8891> Detected remote connection to GWAVA scan engine
    [139764627904256] 2023-01-02 08:41:19 (SMTP)<8891> Using remote connection for scan
    [139764627904256] 2023-01-02 08:41:19 (SMTP)<8891> Message direction computed as outbound
    [139764627904256] 2023-01-02 08:41:19 (SMTP)<8891> Requesting message scan from GWAVA service
    [139764627904256] 2023-01-02 08:41:24 (SMTP)<8891> Message scan completed, inspecting results
    [139764627904256] 2023-01-02 08:41:24 (SMTP)<8891> Message allowed
    [139764627904256] 2023-01-02 08:41:24 (SMTP)<8891> [g->s] DATA
    [139764627904256] 2023-01-02 08:41:24 (SMTP)<8891> [s->g] Receive Error: SOCKET: Peer disconnected during data receive
    [139764627904256] 2023-01-02 08:41:24 (SMTP)<8891> [g->s] QUIT
    [139764627904256] 2023-01-02 08:41:24 (SMTP)<8891> [s->g] Receive Error: SOCKET: Peer disconnected during data receive
    [139764627904256] 2023-01-02 08:41:24 (SMTP)<8891> [g->c] 451 Error occurred forwarding data
    [139764627904256] 2023-01-02 08:41:24 (SMTP)<8891> [c->g] QUIT
    [139764627904256] 2023-01-02 08:41:24 (SMTP)<8891> [g->c] 221 Service closing transmission channel
    [139764627904256] 2023-01-02 08:41:24 (SMTP)<8891> Processing complete for connection from 10.166.11.32
    [139764627904256] 2023-01-02 08:41:24 (SMTP)<8891> SMTP client connection finished processing (client count 0)
    [139765470148352] 2023-01-02 08:41:26 Committing OU message tracker data: 1 OUs to be processed
    [139765470148352] 2023-01-02 08:41:26 Processing message tracker data for OU: 1
    [139764627904256] 2023-01-02 08:41:26 Beginning Message Tracker Commit
    [139764627904256] 2023-01-02 08:41:26 Ending Message Tracker Commit: 123ms
    [139765470148352] 2023-01-02 08:41:26 OU message tracker storage complete
    

  • 0   in reply to 

    Looks like the receiving server disconnects you after 5 seconds. Or there's an overly keen firewall in the way. At any rate, it takes 5 seconds between the SMTP connection establishement until your SMG is ready to send the data, and when it attempts to, thje TCP connection has been terminated.

  • Verified Answer

    +1 in reply to   

    Hi José,

    look here:

    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [c->g] EHLO slmrdlvgw01.montepiordl.local
    [139764627904256] 2023-01-02 08:41:16 (SMTP)<8891> [g->c] 250-mail.montepio-rdl.pt

    Both must match. If they do not mact them the recieving SMTP Antospam / Antivirus Gateway will lower the reputation of the sending server and that will cause delaiys, greylisting and so on.

    EHLO slmrdlvgw01.montepiordl.local

    This is configured in the SMTP interface of your SMG.

    Best regards

    Thomas

  • 0   in reply to 

    *If* that is the problem, and the receiver accepts the EHLO, STARTTLS, sender and receipient, and just "hangs up" without presenting any error on the DATA command, then the receiving server is much more badly broken than the hostname of the sender.

    Not saying this shouldn't be fixed.

  • 0 in reply to   

    The behavior depends on how the receiver handles the message.

    EHLO does not judge the provided Hostnamen and STARTTLS does not care that the certificates are ok as long the work at all.

    checking the wrong hostname and then do greylisting or block or delay is done later.

    Micro Focus  also use SMG and that can be configured that way and as far as i remember from our last SMG Roundtables that’s what they do. Increase the sensitivity level slightly and then emails which were accepted before are now above that level.

    The only way to work around this issue is to make the sending server as trustworthy as possible.

    Best regards

    Thomas 

  • 0   in reply to 

    Nevertheless it is *NEVER* acceptable behaviour to just cut the TCP connection without error, which is what happens here. And I highly doubt this is what SMG does when it denies a message. *If* it checks the hostname/DNS entry, it responds with an error immediately after the EHLO.

  • 0   in reply to 

    Thomas, I am not sure if MF support application uses SMG See no evil - I even doubt ...


    Use "Verified Answers" if your problem/issue has been solved!

  • 0  

    I just manually checked this using telnet. Microfocus' SMTP server indeed just cuts the SMTP connection after 5 seconds of inactivity.

  • 0  

    What do you scan for outgoing mails? Only virus or more?


    Use "Verified Answers" if your problem/issue has been solved!