Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

cannot send emails to sonicwall.com

MPERU99MPERU99 Newbie ✭

I was able to send emails to sonicwall.com now all of the sudden i am getting rejected from sonicwall.com, Notice the Delivery not authorized from the remote server.. anyone else having issues?

Excerpt::

Delivery has failed to these recipients:

[email protected]

Subject: RE: Regarding 43661092 - Address group issue

Remote Server returned: '554 5.7.1 Delivery not authorized, CM=re 202104132021470183089;16'

Category: MySonicWall
Reply

Best Answers

Answers

  • ThKThK Enthusiast ✭✭

    @MPERU99 i had same issue one or two months ago. We use the HES and were not able to sent email to sonicwall.com. not purchase no support no communication with the SE. We finally noticed it when i got an invitation for a video conferenz with the SE an he didnt get our answer...

    So the issue was something in the routing on the HES background. You should ask the support as well. We doublecheck emails to sonicwall.com by sending tests from private accounts which worked. So we fix this to be an problem with the HES.

    -- Thomas

  • MPERU99MPERU99 Newbie ✭

    I forgot to mention, that other people from my organization can email out to sonicwall, its seems to be my email address.

  • RobWRobW Newbie ✭

    There's your answer.

    See other posts about comments/posts being deleted for the same cause.

  • MPERU99MPERU99 Newbie ✭

    I was told yesterday by someone in support , they know that they have an issue and some emails are being blocked. - currently working with guy from corporate to figure out why mine specifically. as i am still able to login to mysonicwall.com just fine.. create and respond to cases just fine.. Other employees from my company can email just fine. so its not a domain/ip blacklist issue.

  • RobWRobW Newbie ✭

    That is so strange, what e-mail provider do you use?

  • MPERU99MPERU99 Newbie ✭

    we host our own email server. (non exchange - but exchange compatible)

    • known facts :
    • was working fine until yesterday
    • yesterday morning I applied the renewal key to ES5000 , sonicwall says this should not have changed anything.
    • ES5000 only takes on incoming emails - not out going
    • Other company workers can email sonicwall with no issues.
    • Sonicwall says my email / domain / IP is not blacklisted.
    • I can email sonciwall using gmail account
    • I can login to mysonicwall.com - respond to cases, create cases, download softwares
    • sonciwall can email me, i cannot reply back.
  • ThKThK Enthusiast ✭✭
    edited April 14

    @MPERU99 try to log into the es with your email account. as you check the SPAM reports. I this working? Check within user,groups,domain if there is a (your) userlisted as locked

    This can happen if you have activated flood protection on outgoing antivirus ...

  • MPERU99MPERU99 Newbie ✭
    edited April 14

    Ran a SMPT test using SMTP_diagtool from the mail server, its definately blocked on Sonicwall end.

    • tech im working with admitted from diagtool log they are blocking it somewhere along the way. they just dont know where. The diagtool log clearly shows connection to sonicwall mail server , accepting commands

    Connected.

    220 mail1.sonicwall.com ESMTP SonicWall (10.0.9.5115)

    EHLO (our mailserver-retracted)

    250-mail1.sonicwall.com

    250-8BITMIME

    250-ENHANCEDSTATUSCODES

    250-DSN

    250-STARTTLS

    250 SIZE

    RSET

    250 2.0.0 Ok

    MAIL FROM: <email retracted>

    250 2.1.0 MAIL CM

    RCPT TO: <[email protected]>

    250 2.1.5 <[email protected]> CM

    DATA

    554 5.7.1 Delivery not authorized, CM=re  202104141523360292005;15

    Error: SMTP protocol error. 554 5.7.1 Delivery not authorized, CM=re  202104141523360292005;15.

    Failed to send messageForcing disconnection from SMTP server.

    QUIT

    Disconnected.

    Connecting to mail server.

    research into RFC1893 indicates  that any x.7.1 error is 
    
    :X.7.1   Delivery not authorized, message refused
              The sender is not authorized to send to the destination.
              This can be the result of per-host or per-recipient
              filtering.  This memo does not discuss the merits of any
              such filtering, but provides a mechanism to report such.
              This is useful only as a permanent error.
    
    X.7.X   Security or Policy Status
    
              The security or policy status codes report failures
              involving policies such as per-recipient or per-host
              filtering and cryptographic operations.  Security and policy
              status issues are assumed to be under the control of either
              or both the sender and recipient.  Both the sender and
              recipient must permit the exchange of messages and arrange
              the exchange of necessary keys and certificates for
              cryptographic operations.
    
  • MPERU99MPERU99 Newbie ✭
  • MPERU99MPERU99 Newbie ✭

    ** correction on this.. no one from our organization can email so sonicwall- i thought it was just myself.

  • MichaelFMichaelF Newbie ✭

    Unfortunately snwlhostedeu.com is absolutely not reachable.

    DNS checks shows a totally unknown IP address for snwhlhostedeu.com.

    Does the DNS has been hijacked??

  • MPERU99MPERU99 Newbie ✭

    Emails are now flowing between our organization and sonicwall, It was on sonicwalls end..

    Good job Sonciwall for fixing this.

  • BWCBWC Cybersecurity Overlord ✭✭✭

    Hi guys,

    maybe this is related, because HES customers reported about problems sending mails via the HES outbound gateway. It seems like a DNS misconfiguration. On SNWL's end because one of the authoritative servers can't resolve, whichs results in consequential problems resolving the HES outbound server name for example. This always depends what's in the resolver cache.

    snwlhostedeu.com.	3600	IN	NS	sjl0vm-heswd01.colo.sonicwall.com.
    snwlhostedeu.com.	3600	IN	NS	ns1.snwlhostedeu.com.
    snwlhostedeu.com.	3600	IN	NS	ns2.snwlhostedeu.com.
    

    But only two of them got resolved:

    ns1.snwlhostedeu.com.	3600	IN	A	173.240.221.20
    ns2.snwlhostedeu.com.	3600	IN	A	173.240.221.20
    

    --Michael@BWC

  • MPERU99MPERU99 Newbie ✭

    *updated info for future references.

    Supposedly our public IP was being reject by SNWL's grid ( not sure if they mean SendGrid or what they are referring to as grid )

    it has since been greylisted to allow email flow.

Sign In or Register to comment.