Problem with Sending Emails

[eat more bacon]

This is really odd....

I haven't been able to send emails for the last 36 hours or so. All
settings seem fine, nothing was changed just prior to this happening. The
inability extends across several email accounts and several servers so
assumed it was an Outlook issue, perhaps a corrupt profile.

A couple hours ago, I was at a Starbucks, using AT&T WiFi. Just thought I'd
see what would happen if I tried to send an email... and it went through. No
issue sending them for the couple hours there. Now back at the home
office... and they won't send.

So, I'm guessing it isn't Outlook, but something related to my Internet
connections.. maybe an IP problem? Has anyone had a similar experience
and/or a suggested resolution?

Thanks

 

[Rogier]

Do you get an error message when sending email ???

If you are using a regular smtp server (not IMAP) to try a telnet session to
the ip address of the mailserver on port 25: So start cmd prompt and type:
telnet x.x.x.x 25. If you get a caanot connect message I would asume that you
a facing a firewall issue on your office network.

Rogier

 

[eat more bacon]

This is a home office. The only firewall on is Windows Firewall. There
are multiple mail servers involved here. I don't know their addresses, but
tried this tool on CMD: ping mail.domain.name. It returned an error (could
not locate).

 

[eat more bacon]

Forgot to answer the first part of your question. Yes, the error code is
0x80042109

 

[Rogier]

I asume that mail.domain.name is not the real server you are trying to send to:

Assume that I use inbox.com as a mail domain: and my.inbox.com as smtp server.

To diagnose try this:

CMD: nslookup my.inbox.com
the anser should like this

Server: dns.zl.iss.as9143.net
Address: 212.54.35.25

Non-authoritative answer:
Name: my.inbox.com
Address: 64.135.83.10

If this does not work you have a DNS issue, themn you could consider
changing the DNS name set in outlook to the ip address ( only a fix )

If it works then just perform the telnet:

CMD: telnet my.inbox.com 25

Then should should get an answer from the server:

220 WM30.inbox.com [InBox.Com SMTP Server] ver. 1.0.3160.15759 by MatriX
ATC:39

If this does not work then it must be a firewall !!!!!!

 

[Rogier]

Points to the proposed solution

Forgot to answer the first part of your question. Yes, the error code is
0x80042109

 

[eat more bacon]

What I get is a DNS time out for the first part with Address that is the IP
of my machine. Then in the non authoritative answer, I get the equivalent of
my.inbox.com and the address is (I believe) the IP of our actual server box.
The telnet CMD is met with a "telnet is not recognized as an internal or
external command, operable program or batch file.

The same thing happens with all 3 different mail servers (3 different
accounts like my.inbox.com, all on different server boxes).
=

I was reading a bit on the web about Comcast (my ISP) blocking port 25 in
some cases. Is that a possibility here? Although we're not using Comcast as
the SMTP server, maybe it still controls the process to some extent?




The telnet

I asume that mail.domain.name is not the real server you are trying to send to:

Assume that I use inbox.com as a mail domain: and my.inbox.com as smtp server.

To diagnose try this:

CMD: nslookup my.inbox.com
the anser should like this

Server: dns.zl.iss.as9143.net
Address: 212.54.35.25

Non-authoritative answer:
Name: my.inbox.com
Address: 64.135.83.10

If this does not work you have a DNS issue, themn you could consider
changing the DNS name set in outlook to the ip address ( only a fix )

If it works then just perform the telnet:

CMD: telnet my.inbox.com 25

Then should should get an answer from the server:

220 WM30.inbox.com [InBox.Com SMTP Server] ver. 1.0.3160.15759 by MatriX
ATC:39

If this does not work then it must be a firewall !!!!!!

This is a home office. The only firewall on is Windows Firewall. There
are multiple mail servers involved here. I don't know their addresses, but
tried this tool on CMD: ping mail.domain.name. It returned an error (could
not locate).

 

[Wowbagger]

I was reading a bit on the web about Comcast (my ISP) blocking port 25 in

some cases. Is that a possibility here? Although we're not using Comcast
as
the SMTP server, maybe it still controls the process to some extent?

I have heard that at times Comcast will block port 25 unless you call them
up and ask them to unblock it for you.

 

[Rogier]

Are you using Vista !!!

Put in the printed text of the nslookup command.

What mail domain are you trying, it's not normal to get a dns timeout; and
what do you mean with the ip of my machine !!! your PC or your router ???

R>

What I get is a DNS time out for the first part with Address that is the IP
of my machine. Then in the non authoritative answer, I get the equivalent of
my.inbox.com and the address is (I believe) the IP of our actual server box.
The telnet CMD is met with a "telnet is not recognized as an internal or
external command, operable program or batch file.

The same thing happens with all 3 different mail servers (3 different
accounts like my.inbox.com, all on different server boxes).
=

I was reading a bit on the web about Comcast (my ISP) blocking port 25 in
some cases. Is that a possibility here? Although we're not using Comcast as
the SMTP server, maybe it still controls the process to some extent?




The telnet

I asume that mail.domain.name is not the real server you are trying to send to:

Assume that I use inbox.com as a mail domain: and my.inbox.com as smtp server.

To diagnose try this:

CMD: nslookup my.inbox.com
the anser should like this

Server: dns.zl.iss.as9143.net
Address: 212.54.35.25

Non-authoritative answer:
Name: my.inbox.com
Address: 64.135.83.10

If this does not work you have a DNS issue, themn you could consider
changing the DNS name set in outlook to the ip address ( only a fix )

If it works then just perform the telnet:

CMD: telnet my.inbox.com 25

Then should should get an answer from the server:

220 WM30.inbox.com [InBox.Com SMTP Server] ver. 1.0.3160.15759 by MatriX
ATC:39

If this does not work then it must be a firewall !!!!!!

This is a home office. The only firewall on is Windows Firewall. There
are multiple mail servers involved here. I don't know their addresses, but
tried this tool on CMD: ping mail.domain.name. It returned an error (could
not locate).

:

Do you get an error message when sending email ???

If you are using a regular smtp server (not IMAP) to try a telnet session to
the ip address of the mailserver on port 25: So start cmd prompt and type:
telnet x.x.x.x 25. If you get a caanot connect message I would asume that you
a facing a firewall issue on your office network.

Rogier

:

This is really odd....

I haven't been able to send emails for the last 36 hours or so. All
settings seem fine, nothing was changed just prior to this happening. The
inability extends across several email accounts and several servers so
assumed it was an Outlook issue, perhaps a corrupt profile.

A couple hours ago, I was at a Starbucks, using AT&T WiFi. Just thought I'd
see what would happen if I tried to send an email... and it went through. No
issue sending them for the couple hours there. Now back at the home
office... and they won't send.

So, I'm guessing it isn't Outlook, but something related to my Internet
connections.. maybe an IP problem? Has anyone had a similar experience
and/or a suggested resolution?

Thanks

 

[Chris]

No you are not the only person having problems with this, there are several
others that have posted the same problem on this sight today. I ended up
calling my internet provider and they talked me through a process to change
my outgoing and incoming server address which solved the problem. No
explination why the old one suddenly quit working. (I could recieve email but
not send it.)

 

[Milly Staples [MVP - Outlook]]

Comcast blocks Port 25 and you must use an alternate port. Their web site
has the instructions for your mail client.

The only people who can use Port 25 on Comcast are the business accounts.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact.
How to ask a question: http://support.microsoft.com/KB/555375


After furious head scratching, Wowbagger asked:

|| I was reading a bit on the web about Comcast (my ISP) blocking port
|| 25 in some cases. Is that a possibility here? Although we're not
|| using Comcast as
|| the SMTP server, maybe it still controls the process to some extent?
|
| I have heard that at times Comcast will block port 25 unless you call
| them up and ask them to unblock it for you.

 

[N. Miller]

I was reading a bit on the web about Comcast (my ISP) blocking port 25 in
some cases. Is that a possibility here? Although we're not using Comcast as
the SMTP server, maybe it still controls the process to some extent?

It would not matter which SMTP message submission server you use. When
Comcast imposes a port 25 block, it applies to all outbound SMTP traffic,
regardless of whose server you are using. They install a blocking
configuration file on the modem; works very similar to putting a block in a
SOHO router.

If your ISP is Comcast, and they did put a port 25 block on your modem, you
need to find out if your email service provider is following the new
recommendation in RFC 5321 to use port 587 for message submission.

 

[eat more bacon]

I got on a chat with Comcast today and that is basically what happened here
as well. Had to change my outbound server to them and the port to 587.
Apparently they made this change a year ago, but for whatever reason it only
kicked in for me this week.