"None of your e-mail accounts could send to this recipient".

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Kb seems to recognise there's a problem, using MSO2003 SP1, but offers no
fix. Any ideas? I have even tried sending in plain text, single addresses
etc, but nothing.
 
Try configuring your account to authenticate to the SMTP server that you are
sending thru. (Known issue and MS is working on a fix. No ETA on when it
will be available.)
 
I have done this already. Any other ideas as to why this has 'suddenly'
happened? It appears to affect Hotmail accounts primarily. What changes have
been made to the way Hotmail handles emails not generated on their own (or
MSN) server?
Why did MS not test this apparent change out fully, in consideration that
there are a large number of cable ISPs now, and the majority of those on HSI
use such an ISP as primary?
 
Neo,

Thanks for the advice, I have logging set as on now.
I then did a quick test and sent the same email to one of those hotmail
accounts that failed yesterday, and it failed again (code 450). I then sent
it to my own hotmail account, and it was successful (code 250).
I can post the log, or any part of it, if you feel it will assist with this
problem.
I can only say that, from the experience thus far, the problem appears to
affect some hotmail accounts and not others, and is not random in its use,
e.g., some hotmail accounts will always be OK, others will always fail.
Any further suggestions?
Thanks,
 
Are you sending via a Hotmail account, or through a POP3 account? The
error codes you give below are SMTP error codes (SMTP is used with POP3
accounts), but you're talking about Hotmail.

The 450 code makes me think that you may need to authenticate to your
outgoing server (set up on the "Outgoing server" tab for the account).
 
Jeff,

Thanks for the reply.
The situation is this: I am using Outlook 2003 as my mail app for my ISP
email account with Comcast. I use a POP3 incoming and SMTP outgoing server
configuration, with the outgoing server being authenticated.
I have used the same setup for some time now, tho I did change to MSO2003
from XP a couple of months back.
Recently I have been experiencing problems when sending mail (especially) to
some Hotmail accounts, not all of them, just some, but those that I do have
problems with are regularly problematic, as compared to others that I have no
difficulty at all.

I am aware that KB holds an article on this problem, and it states that MS
are working on it. My question is now basically, as the article gives little
or no real info (just the error message), and the fact that this does not
appear to error on every email, or on every email to a specific provider
(e.g. MSN hotmail), then is my problem related to the article, or is there
something else wrong here.

This has occurred more and more recently, and is becoming something of a
situation now, where certain hotmail accounts do not appear to be accessible
using my ISP/Outlook set up.

I have logging on, and can provide dumps as requested, if you feel that
would assist.

Thanks very much for your help, and a Happy New Year.

Tony
 
What is the KB article you're referring to? If you could provide logs from
a period in which you get this error, it would help determine whether the
problem is with the Outlook/Comcast communication or between Comcast and
Hotmail.
 
Jeff,
The KB article is 872896. This refers to error 450, though I have also
experienced (on the same email accounts) error 550 - [PERMFAIL] destination
not valid within DNS, which sometimes arrived either after, or instead of,
the 450 error for the same address(es).

The log dump follows here:
Please note log times 07:53:17 thru 07:53:33 refer to the failed attempt,
and log times 07:56:34 thru 07:56:45 refer to a successful trasmission. Both
addresses were single and to hotmail accounts.


2004.12.30 07:53:17 SMTP (smtp.comcast.net): Begin execution
2004.12.30 07:53:17 SMTP (smtp.comcast.net): Port: 25, Secure: no, SPA: no
2004.12.30 07:53:17 SMTP (smtp.comcast.net): Finding host
2004.12.30 07:53:17 SMTP (smtp.comcast.net): Connecting to host
2004.12.30 07:53:17 SMTP (smtp.comcast.net): Connected to host
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 220 comcast.net -
Maillennium ESMTP/MULTIBOX sccrmhc13 #5
2004.12.30 07:53:26 SMTP (smtp.comcast.net): [tx] EHLO xpmain
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-comcast.net
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-7BIT
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-8BITMIME
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-AUTH CRAM-MD5 LOGIN
PLAIN
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-DSN
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-EXPN
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-HELP
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-NOOP
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-PIPELINING
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-SIZE 15728640
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-STARTTLS
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250-VERS V04.80c++
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 250 XMVP 2
2004.12.30 07:53:26 SMTP (smtp.comcast.net): Authorizing to server
2004.12.30 07:53:26 SMTP (smtp.comcast.net): [tx] AUTH LOGIN
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 334 VXNlcm5hbWU6
2004.12.30 07:53:26 SMTP (smtp.comcast.net): [tx] dG9ueXNjb3R0dXM=
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 334 UGFzc3dvcmQ6
2004.12.30 07:53:26 SMTP (smtp.comcast.net): [tx] *****
2004.12.30 07:53:26 SMTP (smtp.comcast.net): <rx> 235 Authentication
successful
2004.12.30 07:53:26 SMTP (smtp.comcast.net): Authorized to host
2004.12.30 07:53:26 SMTP (smtp.comcast.net): Connected to host
2004.12.30 07:53:26 SMTP (smtp.comcast.net): [tx] MAIL FROM: <*****>
2004.12.30 07:53:27 SMTP (smtp.comcast.net): <rx> 250 ok
2004.12.30 07:53:27 SMTP (smtp.comcast.net): [tx] RCPT TO: <*****>
NOTIFY=SUCCESS,FAILURE,DELAY
2004.12.30 07:53:32 SMTP (smtp.comcast.net): <rx> 450 [TEMPFAIL] destination
not valid within DNS
2004.12.30 07:53:32 SMTP (smtp.comcast.net): End execution
2004.12.30 07:53:33 Tony: ReportStatus: RSF_COMPLETED, hr = 0x00000000
2004.12.30 07:53:33 Tony: Synch operation completed


2004.12.30 07:56:34 SMTP (smtp.comcast.net): Begin execution
2004.12.30 07:56:34 SMTP (smtp.comcast.net): Port: 25, Secure: no, SPA: no
2004.12.30 07:56:34 SMTP (smtp.comcast.net): Finding host
2004.12.30 07:56:34 SMTP (smtp.comcast.net): Connected to host
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 220 comcast.net -
Maillennium ESMTP/MULTIBOX sccrmhc12 #142
2004.12.30 07:56:44 SMTP (smtp.comcast.net): [tx] EHLO xpmain
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-comcast.net
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-7BIT
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-8BITMIME
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-AUTH CRAM-MD5 LOGIN
PLAIN
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-DSN
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-EXPN
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-HELP
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-NOOP
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-PIPELINING
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-SIZE 15728640
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-STARTTLS
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250-VERS V04.80c++
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250 XMVP 2
2004.12.30 07:56:44 SMTP (smtp.comcast.net): Authorizing to server
2004.12.30 07:56:44 SMTP (smtp.comcast.net): [tx] AUTH LOGIN
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 334 VXNlcm5hbWU6
2004.12.30 07:56:44 SMTP (smtp.comcast.net): [tx] dG9ueXNjb3R0dXM=
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 334 UGFzc3dvcmQ6
2004.12.30 07:56:44 SMTP (smtp.comcast.net): [tx] *****
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 235 Authentication
successful
2004.12.30 07:56:44 SMTP (smtp.comcast.net): Authorized to host
2004.12.30 07:56:44 SMTP (smtp.comcast.net): Connected to host
2004.12.30 07:56:44 SMTP (smtp.comcast.net): [tx] MAIL FROM: <*****>
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250 ok
2004.12.30 07:56:44 SMTP (smtp.comcast.net): [tx] RCPT TO: <*****>
NOTIFY=SUCCESS,FAILURE,DELAY
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250 ok; [simple] forward
to <*****>
2004.12.30 07:56:44 SMTP (smtp.comcast.net): [tx] DATA
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 354 Please start mail input.
2004.12.30 07:56:44 SMTP (smtp.comcast.net): [tx]
..
2004.12.30 07:56:44 SMTP (smtp.comcast.net): <rx> 250 Mail queued for
delivery.
2004.12.30 07:56:44 SMTP (smtp.comcast.net): End execution

It goes without saying that all apparent receipts of mail are successful.

Hope this helps, and thanks again for taking the time to review this matter.

I can suplly the full log to you for the whole transmission time between
send/receive for both sets of transactions if you wish.

Thanks again,

Tony
 
Did both addresses have the same domain (I assume "@hotmail.com")? If so,
I think this is a problem at Comcast, either with their mail or DNS
servers. They're claiming that the domain for the rejected address does
not exist in DNS, which hotmail.com certainly does.

I don't think the KB article you mention is relevant to this, though I
thank you for pointing me to it. I need to follow up to find out who wrote
it and what they're talking about, because if it's describing what I think
it is, the resolution is as Neo mentioned earlier in the thread -
authenticating to the outgoing server should solve the problem.

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

Jeff,
The KB article is 872896. This refers to error 450, though I have also
experienced (on the same email accounts) error 550 - [PERMFAIL]
destination not valid within DNS, which sometimes arrived either after,
or instead of, the 450 error for the same address(es).

The log dump follows here: Please note log times 07:53:17 thru 07:53:33
refer to the failed attempt, and log times 07:56:34 thru 07:56:45 refer
to a successful trasmission. Both addresses were single and to hotmail
accounts.
Click to expand...

<snip the log...>
 
Did both addresses have the same domain (I assume "@hotmail.com")? If so,
I think this is a problem at Comcast, either with their mail or DNS
servers. They're claiming that the domain for the rejected address does
not exist in DNS, which hotmail.com certainly does.

I don't think the KB article you mention is relevant to this, though I
thank you for pointing me to it. I need to follow up to find out who wrote
it and what they're talking about, because if it's describing what I think
it is, the resolution is as Neo mentioned earlier in the thread -
authenticating to the outgoing server should solve the problem.
Click to expand...

Actually, I think the KB *is* relevant, in that were it not for the bug in
SP-1 the message would either have stayed in your Outbox or the
non-delivery receipt would have given the server error message rather than
the "none of your email accounts..." message...
 
Looking at this log, it looks like Outlook is talking to 2 different SMTP
servers.

#1 - Maillennium ESMTP/MULTIBOX sccrmhc13 #5 (This one failed w/ 450)
#2 - Maillennium ESMTP/MULTIBOX sccrmhc12 #142 (This one worked)

Right about now, I would log a few more tries and then share this
information with Comcast because it is possible that one of their SMTP
servers is misconfigured or having issues.

Logicalman said:
Jeff,
The KB article is 872896. This refers to error 450, though I have also
experienced (on the same email accounts) error 550 - [PERMFAIL]
destination
not valid within DNS, which sometimes arrived either after, or instead of,
the 450 error for the same address(es).
Click to expand...
<snip>
 
I agree with Neo - I missed that you were hitting two different servers
when I looked at the logs.

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

Looking at this log, it looks like Outlook is talking to 2 different SMTP
servers.

#1 - Maillennium ESMTP/MULTIBOX sccrmhc13 #5 (This one failed w/ 450)
#2 - Maillennium ESMTP/MULTIBOX sccrmhc12 #142 (This one worked)

Right about now, I would log a few more tries and then share this
information with Comcast because it is possible that one of their SMTP
servers is misconfigured or having issues.

Logicalman said:
Jeff,
The KB article is 872896. This refers to error 450, though I have also
experienced (on the same email accounts) error 550 - [PERMFAIL]
destination not valid within DNS, which sometimes arrived either after,
or instead of, the 450 error for the same address(es).
Click to expand...
<snip>
Click to expand...
 
Neo, Jeff,

Thanks for the advice, I will do as you say.
Just to clarify, it would appear that the server accessing SMTP sever #5 is
having problems, whereby other other server #142 appears OK.

Prior to contacting Comcast on this matter, I will initiate further logs,
and send single emails to the error-prone accounts and qualify that the
server numbers are the same in all cases via the logs (now I am aware of what
I am looking for).

One thing I still do not fathom though, is how does the Comcast server
determine which SMTP server it will use for the delivery. If this is random
(to an extent) then it is more than a coincidence that the same addressees
are returning errors notwithstanding what order they are sent in.
Also, whereby I may have multiple addressees to a single email instance
posted, can multiple SMTP servers be used by Comcast in determining which
sever(s) to use?

Thanks again for all you help, the both of you, I wish you each a very Happy
New Year, and I will post any results/replies back to you, also what my
examination of the log revelas concerning server numbers and their responses.

Tony

Jeff Stephenson said:
I agree with Neo - I missed that you were hitting two different servers
when I looked at the logs.

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

Looking at this log, it looks like Outlook is talking to 2 different SMTP
servers.

#1 - Maillennium ESMTP/MULTIBOX sccrmhc13 #5 (This one failed w/ 450)
#2 - Maillennium ESMTP/MULTIBOX sccrmhc12 #142 (This one worked)

Right about now, I would log a few more tries and then share this
information with Comcast because it is possible that one of their SMTP
servers is misconfigured or having issues.

Logicalman said:
Jeff,
The KB article is 872896. This refers to error 450, though I have also
experienced (on the same email accounts) error 550 - [PERMFAIL]
destination not valid within DNS, which sometimes arrived either after,
or instead of, the 450 error for the same address(es).
Click to expand...
<snip>
Click to expand...
Click to expand...
 
One thing I still do not fathom though, is how does the Comcast server
determine which SMTP server it will use for the delivery.
Click to expand...

It is essentially random.
If this is random (to an extent) then it is more than a coincidence that
the same addressees are returning errors notwithstanding what order they
are sent in. Also, whereby I may have multiple addressees to a single
email instance posted, can multiple SMTP servers be used by Comcast in
determining which sever(s) to use?
Click to expand...

Any given send/receive cycle in Outlook will only talk to a single SMTP
server. If that server happens to be misconfigured, you will have
problems, otherwise things will go smoothly.
 
Back
Top