Email sending

[Nate Rosenthal]

I have used outlook 2003 for years with comcast as my ISP. Today I am having
problems sending out emails from outlook. My outgoing server says
smtp.comcast.net as it always has. It goes into the outbox and just stays
there.

FWIW, I am also having issues with thunderbird and there it just goes on and
on until it times out.

When I send from gmail or comcast or from my business' webmail domain, there
is no problem.

 

[John Blessing]

I have used outlook 2003 for years with comcast as my ISP. Today I
am having problems sending out emails from outlook. My outgoing
server says smtp.comcast.net as it always has. It goes into the
outbox and just stays there.

FWIW, I am also having issues with thunderbird and there it just goes
on and on until it times out.

When I send from gmail or comcast or from my business' webmail
domain, there is no problem.

Must be a problem with comcast's smtp server. Wait and it will no doubt
rectify itself
--
John Blessing

http://www.LbeHelpdesk.com - Help Desk software
http://www.room-booking-software.com - Schedule rooms & equipment
bookings http://www.lbetoolbox.com - De-Duplicates MS Outlook
http://www.repeatmail.com - schedule mass individual emails

 

[Nate Rosenthal]

Must be a problem with comcast's smtp server. Wait and it will no doubt
rectify itself
--
John Blessing

http://www.LbeHelpdesk.com - Help Desk software
http://www.room-booking-software.com - Schedule rooms & equipment
bookings http://www.lbetoolbox.com - De-Duplicates MS Outlook
http://www.repeatmail.com - schedule mass individual emails

 

[Nate Rosenthal]

That would be my guess, seeing that it came out of nowhere. cComcast is not
being very helpful, since they "don't support" outlook 2003.

Thanks

 

[N. Miller]

I have used outlook 2003 for years with comcast as my ISP. Today I am having
problems sending out emails from outlook. My outgoing server says
smtp.comcast.net as it always has. It goes into the outbox and just stays
there.

FWIW, I am also having issues with thunderbird and there it just goes on and
on until it times out.

When I send from gmail or comcast or from my business' webmail domain, there
is no problem.

Comcast has, of late, been imposing a block on outbound port 25 under
certain conditions. If you exceed some quota of SMTP traffic, that will
trigger a block.

I'd suggest using Telnet at a command prompt to see if this might be the
case. The command would look like this: "telnet smtp.comcast.net 25" (just
type the part between the quote marks). If the result looks like this, you
are blocked:

| C:\Documents and Settings\User>telnet smtp.comcast.net 25
| Connecting To smtp.comcast.net...Could not open connection to the host, on port
| 25: Connect failed

The solution is to change the port number under account properties to use
port 587.

 

[Tony]

Comcast has, of late, been imposing a block on outbound port 25 under
certain conditions. If you exceed some quota of SMTP traffic, that will
trigger a block.

I'd suggest using Telnet at a command prompt to see if this might be the
case. The command would look like this: "telnet smtp.comcast.net 25" (just
type the part between the quote marks). If the result looks like this, you
are blocked:

| C:\Documents and Settings\User>telnet smtp.comcast.net 25
| Connecting To smtp.comcast.net...Could not open connection to the host,
on port
| 25: Connect failed

The solution is to change the port number under account properties to use
port 587.

This also just happened to me. Thing is I have not changed my email
practices any for the last 10 or so years that I've been using outgoing port
25 on Comcast. So I guess I can't figure out just what I may have exceeded.
Is there a way to re-establish the use of port 25? The reason I ask is that
port 587 apparently requires authentication. At least that's the only way I
could get it to work. So now I have to log in twice - once on first receive,
again on first send.