Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)

1,821 views
Skip to first unread message

Scott Calkins

unread,
Jan 12, 2003, 12:58:17 PM1/12/03
to
I get the following error when trying to forward or sometimes send a e-mail
in Outlook xp. The error is not coming from my mail server, but seems to be
internal. Sometimes I can send a e-mail to a certain address, but will get
the error when I try and forward a e-mail to the same address. Any ideas on
what-where this "list of allowed rcpthosts" and where I can change it?

>Your message did not reach some or all of the intended recipients.
>Subject: FW: warning of a new scam going around
>Sent: 1/12/2003 10:45 AM
>The following recipient(s) could not be reached:
>Ray Schulte on 1/12/2003 10:45 AM
>553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)


Lanwench [MVP - Exchange]

unread,
Jan 12, 2003, 1:21:47 PM1/12/03
to
It is from your SMTP server. If you use POP/IMAP, etc., contact your ISP or
whomever hosts the mail. If you're using Exchange/MAPI, check with your
Exchange admin.

Scott Calkins

unread,
Jan 12, 2003, 4:56:13 PM1/12/03
to
Nope it is not in the server, Outlook never even connects with the server
before it bounces back that error. Plus I have tried 3 totaly different
server/accounts, all come back with the error a fraction of a second after
hitting the send.

Lanwench [MVP - Exchange]

unread,
Jan 13, 2003, 9:15:13 AM1/13/03
to
No, that is a server error message. See
http://www.mailtraq.com/KB01120806.html for one possible explanation.

What is your mail setup? Are you using Exchange?

Jeff Stephenson [MS]

unread,
Jan 13, 2003, 12:28:23 PM1/13/03
to
This is from the server, and probably indicates that you have to
authenticate to it before being allowed to send outside the domain for which
it is responsible. You can set up authentication on the "Outgoing Server"
tab of your account. You'll need to find out the type of authentication
required by your ISP.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


"Scott Calkins" <sc...@dragonsetc.com> wrote in message
news:Z0iU9.6026$Dq.6...@newsread2.prod.itd.earthlink.net...

Scooby

unread,
Jan 15, 2003, 12:13:02 PM1/15/03
to
I get this error as well. I don't think its a server authentication issue. I
get the reply message as soon as I hit the send button. Way to fast for the
server to reply. Besides when I examine the email address of the sender
there isn't anything but System Administrator. Unfortunately, I can't figure
out how to view the internet headers for the email address like I could in
older versions of Outlook.


"Jeff Stephenson [MS]" <steph...@online.microsoft.com> wrote in message
news:eVycjkyuCHA.1848@TK2MSFTNGP09...

Jeff Stephenson [MS]

unread,
Jan 15, 2003, 12:44:51 PM1/15/03
to
This message is definitely a result of an SMTP server rejecting one of your
recipient addresses as requiring relay when relaying is not allowed. I
don't know *why* relaying isn't allowed in your case, but it usually is a
result of not being authenticated. Note that the message is not *sent* by
the server in question - Outlook, during the SMTP exchange with the server,
was told that the recipient in question was rejected and it then generated a
non-delivery receipt for that user. To see the headers, right-click on the
message and select "Options...".

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


"Scooby" <As...@first.com> wrote in message
news:yEgV9.72373$%n.25403@sccrnsc02...

Scooby

unread,
Jan 15, 2003, 11:22:41 PM1/15/03
to
Jeff, thanks for the reply.

Whats even more concerning about this problem is most of the time its ok.
The messages get through. On occasions however, it happens. Whats the
difference? I haven't determined that. But it wasn't an issue 3 weeks ago
before I started using Outlook XP.


"Jeff Stephenson [MS]" <steph...@online.microsoft.com> wrote in message

news:Oeo5I3LvCHA.1776@TK2MSFTNGP09...

Jeff Stephenson [MS]

unread,
Jan 16, 2003, 12:12:50 PM1/16/03
to
Do you have any authentication set up for the outgoing server? It may be
that your ISP requires a POP login before you send and that most of the time
you have done so, but every now and then you send without having done a POP
download within the required time interval. Outlook 2000 and prior always
did a receive before the send when you hit the Send/Receive button, whereas
Outlook 2002 does them in parallel. This means that the send might start
before you're logged in to POP, in which case you'll get the errors you're
seeing.

Try going clicking the "More Settings..." button on your account, going to
the "Outgoing Server" tab, and set up to log in to the POP server before
sending.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


"Scooby" <As...@first.com> wrote in message

news:lsqV9.5161$1q3.1604@sccrnsc01...

Myself

unread,
Jan 24, 2003, 2:46:41 AM1/24/03
to
Are you using any kind of antivirus software which monitors
your email?

I had a similar problem while using norton antivirus.
When I configured it in the first place obviously I
did so as administrator. An unpriviledged account
exhibited this error until I set that account to
have admin priviledges, logged into that account,
configured the antivirus email component from there,
logged out, de-escalated priviledge on that account
and it was fixed after that.

But it is definitely NOT a server issue with respect
to remote server; it may be the internal antivirus
virtual smtp server thats having a problem;

Check the mail headers for the reject messages.
Post them on here. I think it will show that
these messages come from the Admin account of the
local machine...


"Scott Calkins" <sc...@dragonsetc.com> wrote in

news:Z0iU9.6026$Dq.6...@newsread2.prod.itd.earthlink.net:

0 new messages