Re: Getting error 5.7.1 on new ISP

<Why?>

I would prefer to use a smart host for just this very reason. When I did
not use a smart host a couple of years ago my mail started getting blocked
by various servers just as it is now because of some DNSNo issues about
reverse lookups. When I configured Exchange 2003 to go the smart host route
I did not have this issue. Also, my server spends less time with DNS
lookups and connections. The mail just goes.

Well, now smart host is not something that my ISP is offering. They want me
to setup Exchange to authenticate with their SMTP smart host for one layer
of protection. Then a second layer is setup where when the mail from my
Exchange server goes through their SMTP for routing it checks the "mail
from" addresses and they must be on a user list. They charge for more than
10.

<Why do you think the error is on your side?>

I believe it is on the ISP side or on the system that these very few
contacts are using. I just don't know what it is. 99% of my email does not
have a problem, but these few people are rejecting it at their server. I
don't know exactly why or what else I need to do, but I am hoping that I
might find it out here.


"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uYRQ$OWfIHA.5348@xxxxxxxxxxxxxxxxxxxxxxx
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 Ichecked 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

  • Web mail blocked patch doesnt work
    ... We use Exchange 2000. ... 0.719: Setup encountered an error: Setup cannot continue because one or ... more pre-requisites required to install Hotfix for Exchange 2000 Server ...
    (microsoft.public.mac.explorer)
  • Re: Exchange 2003 SP2 - able to send but not receive email
    ... product and not part of Exchange Server itself. ... OWA already setup and running - My whole goal is to setup this server to ... settings it successfully saved my settings - ...
    (microsoft.public.exchange.admin)
  • RE: To Setup Exchange or not to Setup Exchange...That is the Question.
    ... enough rescources to handle the load that Exchange will put on it. ... into your server in no time, so you will either have to have a very fast RAID ... You can also setup RPC over HTTP for your sales people to reteive e-mail ... phones can download a simple POP client to the phone to get E-mail. ...
    (microsoft.public.exchange.setup)
  • Re: mail not sent outside
    ... How is it possible that I can't reach the smart host anymore if I type the ... So, what's wrong with Exchange?? ... sending email server do not match. ... And then they may do reverse dns. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 SP2 - able to send but not receive email
    ... need to be created by whomever is responsible for you external DNS Records" ... setup the mailbox's in pop3 connector right? ... product and not part of Exchange Server itself. ... OWA already setup and running - My whole goal is to setup this server to ...
    (microsoft.public.exchange.admin)
Loading