Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Outlook / New Users / November 2005

Tip: Looking for answers? Try searching our database.

Sending/forwarding Messages to my .msn account

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Larry D Gibbs - 11 Nov 2005 17:16 GMT
I am a Comcast customer and use my comcast e-mail account for somethings. I
also have a .msn account that I like to forward some of my messages to for
holding purposes. I used to be able to do this but for about a week or so
when I forward message from my computer to my .msn account they never
arrive. Does anyone else have this problem and can it be fixed? I am able to
receive messages from out side sources to both of my accounts. The only
problem I have is either send or forwarding message from my comcast account
from my home computer.

Signature

Larry D Gibbs
gibbsld@msn.com
WWW.LarryGibbs.com

Only left handed people are in their right mind.

Brian Tillman - 11 Nov 2005 19:28 GMT
> I am a Comcast customer and use my comcast e-mail account for
> somethings. I also have a .msn account that I like to forward some of
> my messages to for holding purposes. I used to be able to do this but
> for about a week or so when I forward message from my computer to my
> .msn account they never arrive.

Do they leave your Outbox?

> Does anyone else have this problem
> and can it be fixed? I am able to receive messages from out side
> sources to both of my accounts. The only problem I have is either
> send or forwarding message from my comcast account from my home
> computer.

What exactly are the symptoms and what happened between when it worked and
now?
Signature

Brian Tillman

Larry D Gibbs - 11 Nov 2005 21:27 GMT
They are leaving my outbox but not arriving at me .msn inbox. Everything
seems to be the same with the exception of me not receiving the messages. I
receive messages in both accounts from outside sources. If I send a test
message from my .msn account to my comcast account I get it but if I send a
test message from my comcast account to my msn account I don't get it. If I
send from my comcast account to other people they get the message.

>> I am a Comcast customer and use my comcast e-mail account for
>> somethings. I also have a .msn account that I like to forward some of
[quoted text clipped - 12 lines]
> What exactly are the symptoms and what happened between when it worked and
> now?
Brian Tillman - 14 Nov 2005 14:48 GMT
> They are leaving my outbox but not arriving at me .msn inbox.
> Everything seems to be the same with the exception of me not
[quoted text clipped - 3 lines]
> account to my msn account I don't get it. If I send from my comcast
> account to other people they get the message.

Have you checked the MSN mailbox's junk mail folder to make sure they're not
being filtered out?
Signature

Brian Tillman

Larry D Gibbs - 15 Nov 2005 02:29 GMT
Yes, they are not there either

>> They are leaving my outbox but not arriving at me .msn inbox.
>> Everything seems to be the same with the exception of me not
[quoted text clipped - 6 lines]
> Have you checked the MSN mailbox's junk mail folder to make sure they're
> not being filtered out?
Brian Tillman - 15 Nov 2005 13:47 GMT
> Yes, they are not there either

Well, if you see messages leaving the Outbox but never arriving at the
intended destination and there are no error messages, the next option yuou
have is to see if they're making it to your SMTP server.  Enable diagnostic
logging and see if anything unusual appears.  If you can't decode what you
see, post it here and someone more familiar with the log contents can help.
http://support.microsoft.com/?id=300479
Signature

Brian Tillman

Larry D Gibbs - 17 Nov 2005 02:25 GMT
How do I Enable diagnostic logging?

>> Yes, they are not there either
>
[quoted text clipped - 5 lines]
> contents can help.
> http://support.microsoft.com/?id=300479
Larry D Gibbs - 17 Nov 2005 02:30 GMT
I found out how to Enable diagnostic
logging.

>> Yes, they are not there either
>
[quoted text clipped - 5 lines]
> contents can help.
> http://support.microsoft.com/?id=300479
Larry D Gibbs - 17 Nov 2005 02:35 GMT
Here is the log after I sent a message to gibbsld@msn.com. The message never
arrived.

2005.11.16 18:30:58 <<<< Logging Started (level is LTF_TRACE) >>>>
2005.11.16 18:30:58 mail.comcast.net: Synch operation started (flags =
00000001)
2005.11.16 18:30:58 mail.comcast.net: UploadItems: 1 messages to send
2005.11.16 18:30:58 SMTP (SMTP.comcast.net): Begin execution
2005.11.16 18:30:58 SMTP (SMTP.comcast.net): Port: 25, Secure: no, SPA: no
2005.11.16 18:30:58 SMTP (SMTP.comcast.net): Finding host
2005.11.16 18:30:58 SMTP (SMTP.comcast.net): Connecting to host
2005.11.16 18:30:58 SMTP (SMTP.comcast.net): Connected to host
2005.11.16 18:30:59 SMTP (SMTP.comcast.net): <rx> 220 comcast.net -
Maillennium ESMTP/MULTIBOX sccrmhc12 #146
2005.11.16 18:30:59 SMTP (SMTP.comcast.net): [tx] EHLO larryvghd6pa75
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-comcast.net
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-7BIT
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-8BITMIME
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-AUTH CRAM-MD5 LOGIN
PLAIN
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-DSN
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-EXPN
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-HELP
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-NOOP
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-PIPELINING
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-SIZE 15728640
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-STARTTLS
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250-VERS V05.00c++
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): <rx> 250 XMVP 2
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): Authorized to host
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): Connected to host
2005.11.16 18:31:02 SMTP (SMTP.comcast.net): [tx] MAIL FROM: <*****>
2005.11.16 18:31:03 SMTP (SMTP.comcast.net): <rx> 250 ok
2005.11.16 18:31:03 SMTP (SMTP.comcast.net): [tx] RCPT TO: <*****>
2005.11.16 18:31:03 SMTP (SMTP.comcast.net): <rx> 250 ok; [simple] forward
to <*****>
2005.11.16 18:31:03 SMTP (SMTP.comcast.net): [tx] DATA
2005.11.16 18:31:03 SMTP (SMTP.comcast.net): <rx> 354 Please start mail
input.
2005.11.16 18:31:03 SMTP (SMTP.comcast.net): [tx]
.
2005.11.16 18:31:03 SMTP (SMTP.comcast.net): <rx> 250 Mail queued for
delivery.
2005.11.16 18:31:03 SMTP (SMTP.comcast.net): End execution
2005.11.16 18:31:03 mail.comcast.net: ReportStatus: RSF_COMPLETED, hr =
0x00000000
2005.11.16 18:31:03 mail.comcast.net: Synch operation completed

>> Yes, they are not there either
>
[quoted text clipped - 5 lines]
> contents can help.
> http://support.microsoft.com/?id=300479
Larry D Gibbs - 17 Nov 2005 03:27 GMT
I sent an e-mail to my msn account directly from the Comcast.net e-mail site
and it arrived right on time so my problem has to be with my outlook 2003
setup in some way.

> Here is the log after I sent a message to gibbsld@msn.com. The message
> never arrived.
[quoted text clipped - 53 lines]
>> contents can help.
>> http://support.microsoft.com/?id=300479
Brian Tillman - 17 Nov 2005 14:03 GMT
> Here is the log after I sent a message to gibbsld@msn.com. The
> message never arrived.
...snip...
> 2005.11.16 18:31:03 SMTP (SMTP.comcast.net): <rx> 250 Mail queued for
> delivery.

This line proves that the problem is not Outlook.  Comcast's server accepted
the message from Outlook.  Outlook's done with it and no longer has any
control.  Your problem is on Comcast's end and this proves it, no matter how
much they may wish to deny it.
Signature

Brian Tillman

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.