Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Outlook Express / OE 6.x / September 2004

Tip: Looking for answers? Try searching our database.

can't send through comcast

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
angel - 29 Sep 2004 04:16 GMT
Hi everyone.  Has anyone had any knowledge or experience
with sending messages using comcast.  I have this error
message (no matter which network I'm on:
An unknown error has occurred. Protocol: SMTP, Port: 0,
Secure(SSL): No, Error Number: 0x800C0131

When I do an remove then add account and restart it MIGHT
work once, then it becomes corrupted again.  Any ideas
would be greatly appreciated.  I have reinstalled (run)
the OE SP1 and still it doesn't last.
Many thanks,
Angel
Bruce Hagen - 29 Sep 2004 04:21 GMT
This applies to OE, but I'm not sure if Comcast is the same issue.

http://insideoe.tomsterdam.com/problems/errors.htm#foldersdbx
Signature

Bruce Hagen
  ~IB-CA~

> Hi everyone.  Has anyone had any knowledge or experience
> with sending messages using comcast.  I have this error
[quoted text clipped - 8 lines]
> Many thanks,
> Angel
Kath Adams - 29 Sep 2004 07:07 GMT
> Hi everyone.  Has anyone had any knowledge or experience
> with sending messages using comcast.  I have this error
[quoted text clipped - 8 lines]
> Many thanks,
> Angel

Might you be trying to send via one ISP while connected to another ISP?
(Clue - "I have this error message no matter which network I'm on").
http://insideoe.tomsterdam.com/problems/errors.htm#550relay
Signature

Kath Adams
MS MVP - Windows (IE/OE)
Not many people are named after plane crashes

N. Miller - 29 Sep 2004 09:56 GMT
> Might you be trying to send via one ISP while connected to another ISP?
> (Clue - "I have this error message no matter which network I'm on").
> http://insideoe.tomsterdam.com/problems/errors.htm#550relay

That shouldn't be an issue with Comcast. They use SMTP AUTH, and I guaranty
you that I can send through the Comcast SMTP servers from an SBC Global
connection; I have actually done it.

Signature

Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

Kath Adams - 29 Sep 2004 10:56 GMT
>> Might you be trying to send via one ISP while connected to another
>> ISP? (Clue - "I have this error message no matter which network I'm
[quoted text clipped - 3 lines]
> guaranty you that I can send through the Comcast SMTP servers from an
> SBC Global connection; I have actually done it.

Thanks for that Norman, I didn't know.

Signature

Kath Adams
MS MVP - Windows (IE/OE)
Not many people are named after plane crashes

N. Miller - 30 Sep 2004 09:53 GMT
> > That shouldn't be an issue with Comcast. They use SMTP AUTH, and I
> > guaranty you that I can send through the Comcast SMTP servers from an
> > SBC Global connection; I have actually done it.

> Thanks for that Norman, I didn't know.

When SBC started pushing us to migrate to their Yahoo! contracted service,
they gave us SMTP AUTH servers. Unlike mail.pacbell.net, which I could still
use if I had to, but can only be accessed from an SBC Global IP connection,
smtp.pacbell.yahoo.com can be accessed from any IP connection which permits
port 25 outbound to foreign servers.

I think that more ISPs will be moving to SMTP AUTH because it affords better
security of the servers against email abuse. The next step will be for mail
service providers to adopt RFC 2476; as more ISPs start blocking port 25
outbound except to their own servers. RFC 2476 provides for mail submissions
to be made to MSAs on TCP port 587. SMTP AUTH is still expected; but I
believe there is another authentication scheme available, as well.

Spammers have done their damndest to get a free ride, and their efforts are
reshaping the way the Internet works; the rest of us are having to pay for
their abuse of the Internet.

Signature

Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

N. Miller - 29 Sep 2004 09:58 GMT
> Hi everyone.  Has anyone had any knowledge or experience
> with sending messages using comcast.  I have this error
> message (no matter which network I'm on:
> An unknown error has occurred. Protocol: SMTP, Port: 0,
                                                  ^^^^^^
> Secure(SSL): No, Error Number: 0x800C0131

> When I do an remove then add account and restart it MIGHT
> work once, then it becomes corrupted again.  Any ideas
> would be greatly appreciated.  I have reinstalled (run)
> the OE SP1 and still it doesn't last.

What is changing the SMTP port to '0'? It should be '25'. Do you have some
kind of mail proxy, spam checker, or anti virus running? If so, disable it.

Signature

Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

Tom Koch - 29 Sep 2004 17:32 GMT
> > Hi everyone.  Has anyone had any knowledge or experience
> > with sending messages using comcast.  I have this error
[quoted text clipped - 11 lines]
> some kind of mail proxy, spam checker, or anti virus running? If so,
> disable it.

Good catch! The port can also be changed in OE.
Click Tools, then click Accounts and click the Mail tab.
Double-click the account (or click Properties), then click the Advanced
Tab.
Set the Outgoing port to 25.

Signature

----Please post questions and replies in the newsgroups----
Tom Koch - MVP for Internet Explorer and Outlook Express
Awareness is free.
Inside Outlook Express:   http://insideOE.tomsterdam.com

 
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.