Error message : "553 sorry ..."

[JR]

Just lately, every email being sent via Outlook 2002 fails
and generates the following :553 sorry, that domain isn't
in my list of allowed rcpthosts (#5.7.1)

I've followed MS KB article OL2002 advice re: outgoing
server settings but it makes no difference.

I can send by webmail so it isn't the ISP but what else
could it be please please please?

Thank you.

 

[Vanguardx]

Just lately, every email being sent via Outlook 2002 fails
and generates the following :553 sorry, that domain isn't
in my list of allowed rcpthosts (#5.7.1)

I've followed MS KB article OL2002 advice re: outgoing
server settings but it makes no difference.

I can send by webmail so it isn't the ISP but what else
could it be please please please?

Thank you.

Are you using the SMTP server that is *ON* the same domain as you login
to get Internet access? That is, are you using your ISP's SMTP server,
or are you using some off-domain SMTP server (like yours or one that is
not managed by your ISP)? It is likely that your ISP forbids SMTP
traffic from crossing the network and going outside to an SMTP server
they don't control. That is to eliminate spam abuse.

Likewise, a domain may not permit outside SMTP traffic from coming into
their network to use their SMTP server. That's because you never
authenticated with them so they don't know who the hell you are.
Without ever authenticating to the domain for whose SMTP server you are
trying to use, they don't know if you have permissions (and have paid
for access) to their resources. If they still do permit off-domain
inbound SMTP traffic, they may require that you authenticate to their
SMTP server to prove you have an account with them.

If you configured Outlook to "send before receive" then there is no
prior POP3 session which provided your authentication to use their
resources that can get reused by a following SMTP session (since you are
doing SMTP before POP3). In that case, make sure you enable
authentication for the SMTP server.

 

[JR]

Thanks for your response and help.

The ISP's server is on the same domain as my email
address. Outlook is configured that the outgoing server
requires authentication and should use the same settings
as for incoming mail.

I await your help again with thanks.

J

 

[Vanguardx]

Thanks for your response and help.

The ISP's server is on the same domain as my email
address.

That's always true. The e-mail address has the domain to which messages
are sent and the mail server to handle them is going to be on that
domain to receive them. You need to use the SMTP server for whatever
network to which you are *connected*. Maybe that's what you meant, that
you using the SMTP server on the network you use to get your Internet
connection. For example, if you are dialing in or have DSL/cable to
Earthlink then you use Earthlink's SMTP server despite whatever is your
e-mail address.

Outlook is configured that the outgoing server
requires authentication and should use the same settings
as for incoming mail.

It is possible although not probable that the ISP requires different
login credentials for POP3 and SMTP authentication. It is unlikely but
you could check with your ISP. By the way, what does your ISP say?
Often they won't help except for users of Outlook Express, so you can
easily test using OE to see if SMTP works using that e-mail client.

Enable transport logging and look in there to see what is happening
during the SMTP portion of your mail session. Once you have the log and
can show to your ISP that you are indeed connecting to their SMTP server
to send outbound messages but which fail, you can then call them up and
have proof that their mail server is screwed up.

Then contact whomever manages the SMTP relay to which you connect.
Apparently they are relaying SMTP traffic to another domain which isn't
theirs or there is misconfiguration. Many ISPs run regional mail
servers to provide load balancing and sufficient bandwidth but may relay
those messages to other internal mail servers.

You might also want to check the settings for the SMTP server. Make
sure there are no leading or trailing spaces in the server name. If you
are using an IP name, like mail.mydomain.com, instead of an IP address,
like 12.12.12.12, then check that there isn't an entry in your 'hosts'
file (no filename extension); otherwise, the IP name gets checked in the
hosts file first and will use whatever IP address is specified there
instead of what your DNS server (which is probably the ISP's DNS server)
reports back as the IP address (computers connect using IP addresses,
not IP names).