• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1228
  • Last Modified:

Have any about a Delivery Status Notification (Failure) code 501

We are receiving the following delivery status notification when we are sending e-mails to a specific domain, let's say domain.com.
The error message is:
"The following recipient(s) could not be reached:
      Krrrrr@domain.com on 10/23/2008 12:07 PM
            There was a SMTP communication problem with the recipient's email server.  Please contact your system administrator.
            <mail.mydomain.com #5.5.0 smtp;501 Failure Bad FROM MX record (cached), Setting G_BADFROM_NOIP> "
I have to specify that we are using our own smtp server (not ISP's server) that is behind a FW in DMZ, while our domain DNS records are administred by our ISP. Have you any ideea about this DSN error?
0
stefan75
Asked:
stefan75
  • 2
1 Solution
 
Karl12347Commented:
It looks like your exchange server is having problems communicating out to the internet. make sure you have host A records for you ISP service provider in your DNS and also that the correct MX records are in you dns.

Hope this helps.
Karl
0
 
RudramCommented:
0
 
stefan75Author Commented:
In fact we are sending external e-mails using a GFI server (in DMZ). Exchange is used only as a local mailserver that is forwarding the external messages to the GFI server. We are receiving emails using another server (an external one), which for the MX record is setup correctly in our DNS. The A and MX records are correctely setup in our DNS. Reverse DNS lookup is setup to point to our smtp (outbound) server that is different then our MX (inbound) server. We're receiving the specified DSN error only when we're sending emails to one particular domain (but we care receive e-mails from it).
0
 
Karl12347Commented:
if it is only one specific domain, have you tried to contact them to see if they are having issues.

Use a MX record lookup website on the internet and then check that the emails are going via the correct path on the internet by using a Tracert or MSlookup.

I have come across problems were the recipents have a static dns entry for our exchange server but then we changed some of our infrastructure and the emails would not work correctly.

definatly sounds like a routing issue on the internet.
Regards
Karl
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now