Re: No answer but new info on 550 5.7.1 email relay errors

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



When any email server queries a domain to know where to send email, it asks
for the MX record. If there isn't one or is wrong then you will have
problems. This is not your problem but the other side. So if your server is
resolving DNS, then this probably ain't the problem.

But I can tell you with almost a guarantee that the reason you are getting
this is because the other side has some type of anti-spam feature and will
not accept email from either your domain or your IP. A lot of servers now
are doing a reverse DNS lookup and if it doesn't pan out then it denies your
email. Plus quite a few SendMail Unix/Linux servers have anti-spam features
that block you because of the IP, especially if it is tagged as DSL or
Cable. Some give this error because of certain words in the email, which
explains why simle email goes through but others do not.

I have business DSL, had a reverse DNS and a static IP and still ran into
trouble. Your only recourse is to forward your Exchange mail via a
smarthost. I started using MailHop Relay at www.dyndns.org and haven't had a
problem since. Sometimes you can use your ISP too and don't have to pay for
it.

Hope that helps

--
Rick Faria - MCSE / A+
RDF Technical Services - www.rdfts.com
Email: support at rdfts dot com


"Trevor Clark" <thetrev68 @ gmail.com> wrote in message
news:uJmLMvDQFHA.2584@xxxxxxxxxxxxxxxxxxxxxxx
> Andy,
>
> I don't have a solution for you, but I can tell you that I've found the
> exact same problem here. I've always just assumed it was a problem on the
> other end.
>
> I'll be watching this thread closely because it is something I would like
> to solve.
>
> -Trevor
>
> "Andy Roth" <AndyRoth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:83D05914-3F88-4CFB-9AB1-3C5B8C44D10C@xxxxxxxxxxxxxxxx
>>I have SBS 2003 Premium with two nics connected directly to the Internet.
>>It
>> is fully patched including Exchange SP1. My ISP's DNS servers are set up
>> as
>> forwarders in my SBS DNS and Exchange is using DNS to send Internet mail.
>>
>> I have Googled the newsgroups on this error and found a lot of questions
>> from others about these errors, but not an answer. There is a Microsoft
>> KB
>> article that has some suggestions but it did not fix my problem.
>>
>> Here's the problem. When sending Internet email to certain domains a
>> user
>> will sometimes (but not always) get an NDR like this:
>>
>> Your message did not reach some or all of the intended recipients.
>>
>> Subject: Business Info
>> Sent: 4/12/2005 9:48 AM
>>
>> The following recipient(s) could not be reached:
>>
>> user@xxxxxxxxxxxxx on 4/12/2005 9:49 AM
>> You do not have permission to send to this recipient. For
>> assistance, contact your system administrator.
>> <mydomain.com #5.7.1 smtp;550 5.7.1 <user@xxxxxxxxxxxxx>...
>> Relaying denied>
>>
>> If the email is resent, sometimes it will go through without an error.
>>
>> When the NDR happens the Event log shows:
>>
>> This is an SMTP protocol error log for virtual server ID 1, connection
>> #15.
>> The remote host "xxx.xxx.xxx.xxx", responded to the SMTP command "rcpt"
>> with
>> "550 5.7.1 <user@xxxxxxxxxxxxxxx>... Relaying denied ". The full command
>> sent was "RCPT TO:<user@xxxxxxxxxxxxxxx> ". This will probably cause
>> the
>> connection to fail.
>>
>> Here's the new stuff. On every domain we are having a problem like this
>> with, I found that when I used Telnet to connect to the recipient's mail
>> server if I typed "telnet theirserver.com 25" I got a response like the
>> following:
>>
>> 220 admin.theirDNShostsdomain.com ESMTP Sendmail 8.10.2/8.10.2; Wed, 13
>> Apr
>> 2005 08:42:1
>> 6 -0400
>>
>> When I type helo (or ehlo), mail from, and then the rcpt command I get
>> the
>> relay error every time.
>>
>> But if I type "telnet mail.theirdomain.com 25" I get a response like:
>>
>> 220 mailserver.theirdomain.com Microsoft ESMTP MAIL Service, Version:
>> 6.0.3790.211 ready at
>> Wed, 13 Apr 2005 09:45:18 -0400
>>
>> When I type helo (or ehlo), mail from, and then the rcpt command I do not
>> get the relay error.
>>
>> Domains that do not have this problem resolve to the correct mail server
>> without having to type full host name of their mail server. I tested
>> this on
>> 14 domains we were having this problem with and got the same kind of
>> response
>> from all of them. I am guessing that it is some kind of DNS problem that
>> makes the recipient domain resolve to the correct mail server sometimes
>> but
>> to the email server of the recipient domain's DNS host at other times.
>>
>> I don't know if this is a problem with my configuration, or if the DNS
>> for
>> the recipient mail servers is set up wrong. I checked dnsreports.com for
>> those domains but I don't know enough about DNS to know what it is
>> telling
>> me.
>>
>> I appreciate any help I can get on this. Some of my users are driving me
>> crazy about it.
>>
>> Andy
>
>


.



Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)