I can receive email but cannot send it.

The drama continues... I just spoke with SBC again to try and get the block
lifted from our account. "John" told me port 25 was unblocked and the
problem has nothing to do with SBC because our incoming and outgoing are both
mail.watcoresources.com. John hasn't entirely convinced me that the problem
isn't SBC. So I guess I'm back to the drawing board. He says the problem is
with STP, our webhosting and webmail service. I started with them and this
problem last week and they say their system is working perfectly but asked me
to send ping and tracert reports. I sent those but didn't get anywhere.

I will try to get a log from connecting to the SBC server. I tried what you
suggested about taking the outgoing mail scan off of my boss's anti-virus and
we ge the same error message now. I guess that's good! :-)

Anything else you can think of?



"Jeff Stephenson [MSFT]" wrote:

On Tue, 18 Jan 2005 10:01:04 -0800, AnneKS wrote:

I'll send it in a "prettier" format if you want but for now here's the log:

That looks like a log when trying to connect to the non-SBC SMTP server -
Outlook wasn't able to make a connection. Could you get a log from
attempting to send through the SBC server? I'm curious as to why that
message is being rejected...

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights

One other thing - I can use webmail directly on the internet just fine - send
and receive. There's just something between it and Outlook.

"AnneKS" wrote:

The drama continues... I just spoke with SBC again to try and get the block
lifted from our account. "John" told me port 25 was unblocked and the
problem has nothing to do with SBC because our incoming and outgoing are both
mail.watcoresources.com. John hasn't entirely convinced me that the problem
isn't SBC. So I guess I'm back to the drawing board. He says the problem is
with STP, our webhosting and webmail service. I started with them and this
problem last week and they say their system is working perfectly but asked me
to send ping and tracert reports. I sent those but didn't get anywhere.

I will try to get a log from connecting to the SBC server. I tried what you
suggested about taking the outgoing mail scan off of my boss's anti-virus and
we ge the same error message now. I guess that's good! :-)

Anything else you can think of?



"Jeff Stephenson [MSFT]" wrote:

On Tue, 18 Jan 2005 10:01:04 -0800, AnneKS wrote:

I'll send it in a "prettier" format if you want but for now here's the log:

That looks like a log when trying to connect to the non-SBC SMTP server -
Outlook wasn't able to make a connection. Could you get a log from
attempting to send through the SBC server? I'm curious as to why that
message is being rejected...

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights

AnneKS wrote:
but asked me to send ping and tracert reports. I sent those but didn't
get
anywhere.

And what were the results of the Ping command?

Here are the ping results for the mail server we've been using.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Anne Jonesping mail.watcoresources.com

Pinging mail.watcoresources.com [64.119.175.105] with 32 bytes of data:

Reply from 64.119.175.105: bytes=32 time=41ms TTL=107
Reply from 64.119.175.105: bytes=32 time=41ms TTL=107
Reply from 64.119.175.105: bytes=32 time=41ms TTL=107
Reply from 64.119.175.105: bytes=32 time=40ms TTL=107

Ping statistics for 64.119.175.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 41ms, Average = 40ms

C:\Documents and Settings\Anne Jones


"Gordon" wrote:

AnneKS wrote:
but asked me to send ping and tracert reports. I sent those but didn't
get
anywhere.

And what were the results of the Ping command?

Another update!

All is well! Turns out we needed to reduce the MTU setting on our D-Link DI
604C router. D-Link support was very helpful and we're up and running again.

"AnneKS" wrote:

Here are the ping results for the mail server we've been using.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Anne Jonesping mail.watcoresources.com

Pinging mail.watcoresources.com [64.119.175.105] with 32 bytes of data:

Reply from 64.119.175.105: bytes=32 time=41ms TTL=107
Reply from 64.119.175.105: bytes=32 time=41ms TTL=107
Reply from 64.119.175.105: bytes=32 time=41ms TTL=107
Reply from 64.119.175.105: bytes=32 time=40ms TTL=107

Ping statistics for 64.119.175.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 41ms, Average = 40ms

C:\Documents and Settings\Anne Jones


"Gordon" wrote:

AnneKS wrote:
but asked me to send ping and tracert reports. I sent those but didn't
get
anywhere.

And what were the results of the Ping command?

On Tue, 18 Jan 2005 15:07:02 -0800, AnneKS wrote:

One other thing - I can use webmail directly on the internet just fine - send
and receive. There's just something between it and Outlook.

Webmail is irrelevant - it uses a different port (80), a different protocol
(HTTP), and probably accesses a different server altogether.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights

On Wed, 19 Jan 2005 08:49:20 -0000, Gordon wrote:

AnneKS wrote:
but asked me to send ping and tracert reports. I sent those but didn't
get
anywhere.

And what were the results of the Ping command?

Note that ping only tells you that an ICMP packet can get to the
destination computer and that it sent a reply that got back to you. It
does not say anything about whether you can connect on port 25 or whether
there's an SMTP server running at the destination...

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights

I am having a similar "can receive, but not send" problem with Outlook 2000.
I have been using an AOL Broadband connection as my ISP, but access a webmail
account (a 3rd party domain name/server) through Outlook 2000. This has been
working just fine for over a year...when all of sudden, about 10 days ago, I
stopped being able to SEND messages. Whenever I attempt to SEND a message
from Outlook I get the following error message:

"This message could not be sent because one of the recipients was rejected
by the server. Server Response: 553 your IP (xxx.xxx.xx.xxx) is on our block
list. (Account: 'mail.scottishsportsfutures.org.uk', SMTP server:
'mail.scottishsportsfutures.org.uk', error number: 0x800ccc79"

My 3rd party (web-hosting) server ASSURE me this has nothing to with them.
I believe them because I am able to send emails through my webmail account
and they can send emails to me when they enter my account details onto THEIR
computers. They are about 98% sure it has something to do with AOL putting
my domain name on some kind of spam-preventing block list. They told me to
call AOL and have it unblocked...but AOL also "ASSURE" me that they do not
put IP addresses or domain names on block lists.

The craziest part is -- that I have had ZERO problems using Outlook and AOL
over the past year...and all of a sudden, one day it just stopped sending
messages & starts giving me that same error message. I haven't done anything
to change my account properties/settings. My firewall allows full access to
Outlook.

I'm completely stumped and so very, VERY frustrated!

Can you offer any suggestions? ...pretty please????

"Jeff Stephenson [MSFT]" wrote:

On Tue, 18 Jan 2005 08:41:02 -0800, AnneKS wrote:

Again, I can recieve but not send. The error that I get is 0x80042109.

This is most likely because SBC is blocking port 25 to all but their own
servers, a common (and lamentable) practice of ISPs nowadays.

My boss gets a different one - 0x800CCC0F.

That is likely due to an anti-virus program on your boss's computer that's
scanning outgoing mail - lately, at least, this error seems to be tied very
tightly to that. Disable outgoing mail scanning, which may require
uninstalling the anti-virus program, then reinstalling it with the option
disabled.

I've been working on mine for now. I opened up the firewall settings and
allowed Outlook as an exception. I switched my outgoing server (SMTP) server
to what SBC suggests - smtp.sbcglobal.yahoo.com (SMTP authentication is
required.) I then tested the account settings and got the error message
"Send test email message: unable to send test Message. Please verify the
E-mail Address field." For "fun" I then tried to send a message - I get a
new error message: "0x800CCC78: Unable to send the message. Please verify
the email address in your account properties. The server responded: ??????"
The email address is mine and is correct!

Could you turn on diagnostic logging (see
http://support.microsoft.com/default...;en-us;Q300479) and post
the OPMLog.log file after trying to send?

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights

On Wed, 19 Jan 2005 15:55:02 -0800, Sandra wrote:

"This message could not be sent because one of the recipients was rejected
by the server. Server Response: 553 your IP (xxx.xxx.xx.xxx) is on our block
list. (Account: 'mail.scottishsportsfutures.org.uk', SMTP server:
'mail.scottishsportsfutures.org.uk', error number: 0x800ccc79"

My 3rd party (web-hosting) server ASSURE me this has nothing to with them.
I believe them because I am able to send emails through my webmail account
and they can send emails to me when they enter my account details onto THEIR
computers. They are about 98% sure it has something to do with AOL putting
my domain name on some kind of spam-preventing block list. They told me to
call AOL and have it unblocked...but AOL also "ASSURE" me that they do not
put IP addresses or domain names on block lists.

The craziest part is -- that I have had ZERO problems using Outlook and AOL
over the past year...and all of a sudden, one day it just stopped sending
messages & starts giving me that same error message. I haven't done anything
to change my account properties/settings. My firewall allows full access to
Outlook.

Sending through your webmail account means nothing - it's a whole different
protocol and server. The only thing you can do at your end is to try
setting up authentication to your outgoing server (on the "outgoing server"
tab for your account).

If that doesn't work, you're going to have to get the help of your ISP in
investigating. If you have a static IP address, it may be that it ended up
on a "black hole" list of IP addresses thought to send or allow spam - many
ISPs use these. If you don't have a static IP, there may be something else
at work...

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights

Hi Sandra -

I had the same problem with Outlook 2002 and SBC Yahoo DSL. All of a sudden
it just stopped being able to send. The problem for me ended up being the
router of all things. We had to change our MTU setting. It was at 1492, now
it's at 1472 and everthing is back to normal. What kind of router are you
using?

Good luck!

"Sandra" wrote:

I am having a similar "can receive, but not send" problem with Outlook 2000.
I have been using an AOL Broadband connection as my ISP, but access a webmail
account (a 3rd party domain name/server) through Outlook 2000. This has been
working just fine for over a year...when all of sudden, about 10 days ago, I
stopped being able to SEND messages. Whenever I attempt to SEND a message
from Outlook I get the following error message:

"This message could not be sent because one of the recipients was rejected
by the server. Server Response: 553 your IP (xxx.xxx.xx.xxx) is on our block
list. (Account: 'mail.scottishsportsfutures.org.uk', SMTP server:
'mail.scottishsportsfutures.org.uk', error number: 0x800ccc79"

My 3rd party (web-hosting) server ASSURE me this has nothing to with them.
I believe them because I am able to send emails through my webmail account
and they can send emails to me when they enter my account details onto THEIR
computers. They are about 98% sure it has something to do with AOL putting
my domain name on some kind of spam-preventing block list. They told me to
call AOL and have it unblocked...but AOL also "ASSURE" me that they do not
put IP addresses or domain names on block lists.

The craziest part is -- that I have had ZERO problems using Outlook and AOL
over the past year...and all of a sudden, one day it just stopped sending
messages & starts giving me that same error message. I haven't done anything
to change my account properties/settings. My firewall allows full access to
Outlook.

I'm completely stumped and so very, VERY frustrated!

Can you offer any suggestions? ...pretty please????

"Jeff Stephenson [MSFT]" wrote:

On Tue, 18 Jan 2005 08:41:02 -0800, AnneKS wrote:

Again, I can recieve but not send. The error that I get is 0x80042109.

This is most likely because SBC is blocking port 25 to all but their own
servers, a common (and lamentable) practice of ISPs nowadays.

My boss gets a different one - 0x800CCC0F.

That is likely due to an anti-virus program on your boss's computer that's
scanning outgoing mail - lately, at least, this error seems to be tied very
tightly to that. Disable outgoing mail scanning, which may require
uninstalling the anti-virus program, then reinstalling it with the option
disabled.

I've been working on mine for now. I opened up the firewall settings and
allowed Outlook as an exception. I switched my outgoing server (SMTP) server
to what SBC suggests - smtp.sbcglobal.yahoo.com (SMTP authentication is
required.) I then tested the account settings and got the error message
"Send test email message: unable to send test Message. Please verify the
E-mail Address field." For "fun" I then tried to send a message - I get a
new error message: "0x800CCC78: Unable to send the message. Please verify
the email address in your account properties. The server responded: ??????"
The email address is mine and is correct!

Could you turn on diagnostic logging (see
http://support.microsoft.com/default...;en-us;Q300479) and post
the OPMLog.log file after trying to send?

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights