Re: Getting error 5.7.1 on new ISP

Jordan <nospam@xxxxxxxx> wrote:
Yes it would be a waste to enter the users names on the XO site (time
and money). However I hope to get some recommendation or solution to
why my Exchange 2003 server cannot send email to some domains.

I checked all the black lists I could think of and the IPs I got from
XO were not on the list. I also checked a revers lookup of the IP
address and it did resolve to my fqdn of my exchange server. What
could be wrong?

Why do you think the error is on your side?

You didn't answer my questions.....



"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:eTxX8$UfIHA.1900@xxxxxxxxxxxxxxxxxxxxxxx
Jordan <nospam@xxxxxxxx> wrote:
Just changed over to a new ISP (XO Communications). I wanted to
just change my Exchange 2003 SP2 server to use their SMTP server as
a smart host

Why? That's not the best way to go. Much better to deliver directly
whenever possible, for reasons of
performance/efficiency/security/ease of troubleshooting.

but they have this dumb rule where I have to setup every
user on their system as well so when mail comes from jsmith, bjones,
jdoe, etc @mydomain.com it comes from an address they know. They
won't just allow it to come from my IP. This is a hassle to keep up
to date and they also charge per account.

Oh, don't do that. That's insane. If you've got a business account,
complain - and if you don't have a business account and must
absolutely use a smarthost then find someone else (DynDNS MailHop
Outbound works & is inexpensive).

Instead I requested that they setup a ptr record for
myemailserver.mydomain.com which is my Exchange 2003 server's
external IP address (internal address is 192.168.x.x). Now even
though that has been setup for 5 days and I can reverse lookup the
IP address 209.x.x.x which resolves to myemailserver.mydomain.com I
am getting 5.7.1 no relaying messages from some companies. Here is
the exact return message:
====================

Your message did not reach some or all of the intended recipients.

Subject: Test
Sent: 3/3/2008 11:08 AM

The following recipient(s) could not be reached:

EI_Sales@xxxxxxxxxxxxxxxxxxx on 3/3/2008 11:08 AM
You do not have permission to send to this recipient. For
assistance, contact your system administrator.
<myemailserver.mydomain.com #5.7.1 smtp;501 5.7.1 This
system is not configured to relay mail (r) from
<jcnolan@xxxxxxxxxxxx> to <EI_Sales@xxxxxxxxxxxxxxxxxxx> for
209.x.x.x>

That's not an error from your server and if you've got a static IP &
a PTR, you're pretty good (although you should perhaps do an SPF
record as well).

Are these recipients people you could successfully e-mail before you
changed ISPs? The issue would appear to be in their side.



.

Relevant Pages

  • Re: Exchange in a Child domain
    ... Service (RUS) problem. ... Do your recipients have valid e-mail addresses, ... MVP - Exchange ... in the child domain on the parent domain Exchange Server. ...
    (microsoft.public.exchange.setup)
  • Re: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)
  • Re: missing attachments to some internet recipients
    ... If messages are sent using the Exchange family of mail programs ... The Exchange user can turn off the RTF option for messages to selected ... Note that if sending via an Exchange server, ... some recipients. ...
    (microsoft.public.internet.mail)
  • Re: Getting error 5.7.1 on new ISP
    ... Exchange 2003 server cannot send email to some domains. ... complain - and if you don't have a business account and must absolutely ... Your message did not reach some or all of the intended recipients. ...
    (microsoft.public.exchange.admin)
  • Exchange 2003 SP1 periodicaly losses connection to active directory for about 30 minutes
    ... We have active directory in two servers but the mail server fails to ... the promotion of the server to active directory the exchange was up. ... After a Domain Controller is promoted to a Global Catalog, ...
    (microsoft.public.exchange.connectivity)