Emails not reaching destination

[Thunder]

Why are my emails not reaching their destination?

I have sent test messages to my own gmail and yahoo accounts and they never
arrive...I have already called my service provider (Comcast) and sent tests
from my Comcast Webmail and they work fine, so it isn't Comcast, but sending
with Outlook, the same test messages never reach the destination - including
some of my contacts.

Using Outlook 2007

 

[Roady [MVP]]

Are these messages still stuck in your Outbox?
Do you get send/receive errors?

If not, the issue is caused by something between Outlook and the recipient.
Most likely your virus scanner integrating with Outlook. Disable this
integration and try again.

 

[Thunder]

No they don't get stuck, they just poof into lala land.
I will try and disable the virus integration and see if that does it, thanks.

 

[florida mum]

Why are my emails not reaching their destination?

I have sent test messages to my own gmail and yahoo accounts and they never
arrive...I have already called my service provider (Comcast) and sent tests
from my Comcast Webmail and they work fine, so it isn't Comcast, but sending
with Outlook, the same test messages never reach the destination - including
some of my contacts.

Using Outlook 2007

 

[florida mum]

I am having a similar problem, I can receive emails from a certain UK based
server, but cannot send email to the same address with out getting the
message - Permanent failure: other address status.
Any ideas? Please!

 

[Roady [MVP]]

This is an unrelated issue to the OP. Start a thread of your own containing
your configuration details. From what it looks like now, this happens
because you specified a wrong address.

 

[Thunder]

Well it wasnt a virus program issue either...I disabled the integration and
it made no difference...

I CAN send messages to myself at my comcast.net address - they go right thru.
I CAN send to anyone from my Comcast email using the Web-based version.
so it isn't Comcast
I get no error messages of any kind and no return email saying the message
was sent to a bad address...;they leave the outbox and disappear, never
arriving at the destination.
I create a new email account in Outlook with all the exact same settings and
then they go thru, but not for long....after an hour or so I am right back to
the same problem!
I hate webmail but if this situation doesn't change I will delete Outlook
and find something better!! This really sucks!

 

[Roady [MVP]]

That's a weird issue to say the least. Does it work correctly in Outlook
Safe Mode?
Start-> Run; outlook.exe /safe

You can enable logging to find out if the messages are correctly delivered
to the email server. If so, the issue is not with Outlook but in the way
your mail server is handling your messages.

Comcast also offers emails to be sent over port 587 instead of the
traditional port 25. Perhaps they handle the incoming emails differently
based on the port as well. It would explain why it will work when you send
to yourself as they will use port 25 for internal communication
(@comcast.net) and don't reroute that traffic to the outside world.

 

[Thunder]

That's a weird issue to say the least. Does it work correctly in Outlook
Safe Mode?
Start-> Run; outlook.exe /safe

made no difference in safe mode

You can enable logging to find out if the messages are correctly delivered
to the email server. If so, the issue is not with Outlook but in the way
your mail server is handling your messages.

how do I do that?


Comcast also offers emails to be sent over port 587 instead of the

traditional port 25. Perhaps they handle the incoming emails differently
based on the port as well. It would explain why it will work when you send
to yourself as they will use port 25 for internal communication
(@comcast.net) and don't reroute that traffic to the outside world.

I am already set to port 587 for outgoing....

 

[N. Miller]

Why are my emails not reaching their destination?

I have sent test messages to my own gmail and yahoo accounts and they never
arrive...I have already called my service provider (Comcast) and sent tests
from my Comcast Webmail and they work fine, so it isn't Comcast, but sending
with Outlook, the same test messages never reach the destination - including
some of my contacts.

Using Outlook 2007

I am starting to wonder if Comcast has a filter on the user agent string.
All mail clients add a user agent string to the headers. You are not the
only Comcast user having trouble with MS Outlook.

When I send email using MS Outlook Express (a different application from MS
Outlook; I do not have Outlook installed on any machine that I use!) I see
this header line in the message:

| X-Mailer: Microsoft Outlook Express 6.00.2900.5512

When I send email using my preferred mail client, I see this:

| X-mailer: Pegasus Mail for Windows (4.41)

This is starting to sound like Comcast is filtering on the header line
stamped by Outlook; may they think a particular version number looks like a
spam engine.

 

[Thunder]

It's not important, screw MS...I installed and am using The Bat! now and have
no issues! All my messages reach their destinations.

 

[N. Miller]

It's not important, screw MS...I installed and am using The Bat! now and have
no issues! All my messages reach their destinations.

If Comcast is filtering on the user agent string, it is not an MS issue. And
The Bat! is a common user agent that spammers put in their user agent
strings (not that they are using The Bat!; but it makes it look that way),
so there are definitely email systems filtering on "The Bat!" in user agent
strings.

 

[Thunder]

Well that's all very fascinating, but I don't speak "techy", how about just
tellin me how to fix the problem - IN ENGLISH!

 

[N. Miller]

"N. Miller" wrote:

Well that's all very fascinating, but I don't speak "techy", how about just
tellin me how to fix the problem - IN ENGLISH!

If it is Comcast filtering on user agent strings, you don't fix it. MS can't
fix it; user agent is hard coded into the application. Comcast can fix it.
Without an example of email going through your system, though, it is tough
to pinpoint the exact problem.

 

[Thunder]

If it is Comcast filtering on user agent strings, you don't fix it. MS can't

fix it; user agent is hard coded into the application. Comcast can fix it.
Without an example of email going through your system, though, it is tough
to pinpoint the exact problem.

And how would u suggest I get you a sample?