No transport provider was available for delivery of your request

[David Cook]

Can someone tell me what causes the
"No transport provider was available for delivery of your request"
symptom from Outlook? It seems to have something to do with
only CERTAIN people's DESTINATION email-sub-address, and it seems
to only happen intermittently (e.g. once every month or two).

My ISP is Comcast, though I'm uncertain whether that's relevant.

It happened again today, on an email I addressed to 3 people. The full
rejection msg was:

-------
Your message did not reach some or all of the intended recipients.

Subject: It's done

Sent: 8/18/2005 9:08 AM

The following recipient(s) could not be reached:

'Alice Kalivas' on 8/18/2005 9:08 AM

No transport provider was available for delivery to this recipient.



'Barbara Appleby' on 8/18/2005 9:08 AM

No transport provider was available for delivery to this recipient.



'Carolyn Males' on 8/18/2005 9:08 AM

No transport provider was available for delivery to this recipient.

----

Notice that all 3 people addresses are SPECIFICALLY mentioned as not
receiving it. (And they didn't).



So, then I turn around a FORWARD the original msg over to each of them
SEPARATELY! And, it goes out

ok to TWO of the THREE people just fine, yet ONE of the people fails again
with the same rejection msg. So, I

try again to forward to just THAT person, and AGAIN it fails the same way.
So, it's clearly SOMETHING to

do with the specifics of THAT sub-networks destination address.



But, hours or a day later, I can THEN forward it even to that one PERSON's
email address, which seems to indicate

that the error was some TEMPORARY condition.



Can anyone shed any light on how I might SOLVE this intermittent problem?
(I've been experiencing it

over the last 2 or 3 years, about once every 2 or 3 months. Thus, it's
happened a total of 8 or 10 times.)



TIA...



Dave

 

[N. Miller]

Can anyone shed any light on how I might SOLVE this intermittent problem?
(I've been experiencing it

over the last 2 or 3 years, about once every 2 or 3 months. Thus, it's
happened a total of 8 or 10 times.)

Don't use the Comcast email servers. It would seem that one of your
recipients is using a service which blocks email from Comcast servers, from
time to time.

--
Norman
~I'll be there, by your side
~in the land of Twilight.
~In your dream I will go
~'till we find the Sunlight.

 

[David Cook]

Norman -

That seems like an IDIOTIC response! You give no REASON why
it might be an issue with a Comcast server.

That's too much like the doctor who said "If your arm hurts when you
raise
it over your head, quit raising it over your head!"

So, I'll politely pretend that you are a nice person and ignore your rude
answer.

Dave (base poster)

 

[ChrisB]

Hi David

You don't say what version of OL you are using? If you take a look at the
Microsoft site and do a search for "no transport provider..." you will see
quite a few articles on this problem which might help - but problem/solution
will depend on your version.

Good luck!

Chris

 

[Lanwench [MVP - Exchange]]

In

Norman -

That seems like an IDIOTIC response! You give no REASON why
it might be an issue with a Comcast server.

That's too much like the doctor who said "If your arm hurts when
you raise
it over your head, quit raising it over your head!"

So, I'll politely pretend that you are a nice person and ignore
your rude answer.

Dave (base poster)

Wow, I have to say, "base" is a good word to use there, albeit slightly
atavistic. You asked for free technical support in a newsgroup. You got a
reply that was not rude, insulting, or in any way offensive....it may not be
the correct answer to your question, but caveat emptor in usenet. All you
need to do with posts you don't like is ignore them. Play nice with the
other kids in here - everyone is volunteering their time to try to help
others. If you want a better hit rate & one on one support, I suggest you
call Microsoft support. There's a flat rate per incident.

NB: That error message is most commonly encountered when one is using a
version of Outlook prior to OL2002 and is using both Internet e-mail and
Outlook in the same profile. However, you have not provided any detail about
your version of Outlook, your mode, service pack level, email account
type(s), or network connection type, so it is difficult to hazard a guess.
N. Miller's reply may not be as off-base as you think. However, I suggest
you post with more detail, and also mention what you have googled
for/found/tried already.

Pax.

 

[N. Miller]

Norman -

That seems like an IDIOTIC response!

It was not.

You give no REASON why
it might be an issue with a Comcast server.

Actually, I did: "It would seem that one of your recipients is using a
service which blocks email from Comcast servers, from time to time."
I am curious: What part of "...using a service which blocks email from
Comcast servers..." makes it not a reason for this to be an issue with a
Comcast server?

That's too much like the doctor who said "If your arm hurts when you
raise it over your head, quit raising it over your head!"

More like, "If you get a sharp pain in your eye when you drink your coffee,
take the spoon out of the cup".

So, I'll politely pretend that you are a nice person and ignore your rude
answer.

It was not rude.

--
Norman
~I'll be there, by your side
~in the land of Twilight.
~In your dream I will go
~'till we find the Sunlight.

 

[David Cook]

No, that wasn't it at all.

The problem gets ERRONEOUSLY triggered when one of the
email addresses in the list of addresses is invalid.

What is MADDENING is that the diagnostic msg goes on to show
that all the OTHER valid addressees ALSO failed. (But, of course, there
is nothing wrong with the others.)

I set up some experiments to test outgoing msgs with multiple recipients.
The goofy 'no transport provider' REALLY means only that ONE of the
email addresses is bad. But, the foolish diagnostic never tells you WHICH
of them is bad (even tho it OUGHT to know which one is bad).

This is NO WAY TO RUN A RAILROAD.

Sigh. Now the question becomes: Is this erroneous code in some piece of
Outlook-2000 (which is my client)? (Or, is it dependent on the
server-side.)
My quess is that it is probably Outlook-2000 dependency. Maybe there
is even a patch for this!? Is this a known problem?

Can someone at Microsoft please tell me what sub-system is faulty?
(Do I blame Comcast on the server side or is the problem somewhere in
the client-side of Outlook?)


Certainly someone else has encountered and fixed this problem before.

Dave [the base-poster]