There's no need to look any further. The 450 is sent as a status code
by the receiving MTA. They think it's cute to send a 450 instead of a
550 status so spammers will continue to retry sending to a address
that doesn't exist (they won't, but you will).
How do you know the us...@xyz.com is a valid address?
---
Rich Matheisen
MCSE+I, Exchange MVP
"Rich Matheisen [MVP]" wrote:
> On Wed, 1 Oct 2008 13:49:08 -0700, Gabe G
> <Ga...@discussions.microsoft.com> wrote:
>
> >I have 2-3 emails stuck in the queue to a particular domain, let's say
> >xyz.com. When I pull up one of the delayed messages, I see a field called
> >"Last Error" and in that field it says "450 4.5.0 No recipient succeeded".
> >The status of the message is in Retry mode. I can get to a the xyz.com
> >website, but emails to that domain seem to hang. Where should I start
> >looking? The email address (us...@xyz.com) is a valid one.
>
You know Rich, that's a great question.... I was told by the users (there
are two of them trying to send to that same address) that the address was
valid, but I can follow up with that. So does the message indicate that
there is no mailbox at that email address? I hope that was the gist of what
you were trying to tell me :)
Gabe
>
>
>"Rich Matheisen [MVP]" wrote:
>
>> On Wed, 1 Oct 2008 13:49:08 -0700, Gabe G
>> <Ga...@discussions.microsoft.com> wrote:
>>
>> >I have 2-3 emails stuck in the queue to a particular domain, let's say
>> >xyz.com. When I pull up one of the delayed messages, I see a field called
>> >"Last Error" and in that field it says "450 4.5.0 No recipient succeeded".
>> >The status of the message is in Retry mode. I can get to a the xyz.com
>> >website, but emails to that domain seem to hang. Where should I start
>> >looking? The email address (us...@xyz.com) is a valid one.
>>
>
>You know Rich, that's a great question.... I was told by the users (there
>are two of them trying to send to that same address) that the address was
>valid, but I can follow up with that. So does the message indicate that
>there is no mailbox at that email address? I hope that was the gist of what
>you were trying to tell me :)
You can accept the text of the message at face value if you want to,
but all it realy says is that the failure was a transient and that you
should try again. "No recipient succeeded" /could/ mean almost
anything.
"Rich Matheisen [MVP]" wrote:
At some point, Exchange will quit trying to resend and will send an NDR to
the sender.... which means that it will end up in my mailbox to deal with
again :) Since the condition could mean almost anything, would I just tell
the user that there is an issue with the recipient mail server?
[ snip ]
>At some point, Exchange will quit trying to resend and will send an NDR to
>the sender.... which means that it will end up in my mailbox to deal with
>again :) Since the condition could mean almost anything, would I just tell
>the user that there is an issue with the recipient mail server?
Your SMTP protocol logs will tell you that. If they say the recipient
address is correct and you see the receiving server refuse the email
claiming that the address doesn't exist you sure can tell them that.
Have them call their correspondent and pass on the problem to /their/
admin to resolve. :-)