Outlook business e-mail can't send

MSgherzi

Member
Reaction score
0
Location
Tehachapi, California
I had a customer about a week or so ago who had several problems. I managed to solve all of his problems except for the fact that his Outlook 2007 would not send any outgoing e-mails. It was linked to his business e-mail account. He mentioned that a co-worker had something similar. He also mentioned that he recalled being able to send it from another network connection. I checked his firewall, opened up the necessary ports (software and hardware firewalls: i.e windows firewall and his 2WIRE router/modem), turned off his anti-virus, ran Outlook with the highest privileges (he was running Vista...64-bit? can't remember if it was x86 or not), and I even tried changing security settings and port numbers within Outlook itself. No dice.

I told him I'd try to find a solution for him. So far, nothing. They don't have an IT person at his business but their lady who set this whole thing up claims the ports are right and the settings are right.

Anything that I missed?
 
Maybe a problem with the ISP he's on? Sometimes they block any smtp traffic other than their own. Just a thought since it supposedly worked on another network.
 
I would start by checking the authentification settings in the mail account set up. Alot of ISP's require authentification if you are sending mail via an internet connection other than their own.
 
If you've got the ports right (I'd call the email host to double check the settings) and you've got the authentication set right also, then I'd take the computer off site to another network and another ISP and see if it works. If so, you've got an ISP problem, most likely they are blocking the outgoing port traffic for some reason.

I know it seems amateurish but I've found sometimes it's best to make 110% sure all settings are correct and after that, take the machine off site and test the settings there too. If there is some weird networking/ISP problem on their location it might take 10x as long to figure out there as it would to just take the machine back to your shop for an hour.
 
If you've got the ports right (I'd call the email host to double check the settings) and you've got the authentication set right also, then I'd take the computer off site to another network and another ISP and see if it works. If so, you've got an ISP problem, most likely they are blocking the outgoing port traffic for some reason.

I know it seems amateurish but I've found sometimes it's best to make 110% sure all settings are correct and after that, take the machine off site and test the settings there too. If there is some weird networking/ISP problem on their location it might take 10x as long to figure out there as it would to just take the machine back to your shop for an hour.


You know, you're probably right. It worked before, but it's possible that AT&T is blocking it. I don't know if he would have wanted me to take the whole thing somewhere else just to try, though. I could, however, just copy his e-mail settings into Thunderbird and try it somewhere else.

Thanks for the suggestions.

Nice sig BTW!
 
You know, you're probably right. It worked before, but it's possible that AT&T is blocking it. I don't know if he would have wanted me to take the whole thing somewhere else just to try, though. I could, however, just copy his e-mail settings into Thunderbird and try it somewhere else.

Thanks for the suggestions.

Nice sig BTW!

I've seen a problem where ISP blocks mail of of other servers when configured to send through the ISP. Like MSgherzi@MSgherzi.com over att.com. You may have mail.msgherzi.com for ingoing/outgoing or whatever the server requires. ISPs sometimes block port 25 in that case due to spammers. Sometimes changing port number and allowing it through firewall is all that's needed.
 
Whenever I am blocked from doing something I load a program called hotspot shield. Not sure if I trust it beyond creating a VPN (you can research it and make it your call) that is why I always uninstall when I'm done. It does create a real VPN that ISPs can't see/block. Useful for many situations when there is a suspected port block or traffic shaping taking place.
 
Just some other thoughts,are passwords correct (case sensitive)? recently installed program,like some kinds spam filtering system or software.Windows firewall turn on by mistake.

Was server ever rebooted recently,maybe a driver update.Service pack install corrupted.Check your I.E. settings.Maybe install and reinstall of Anti virus.
 
Just some other thoughts,are passwords correct (case sensitive)? recently installed program,like some kinds spam filtering system or software.Windows firewall turn on by mistake.

Was server ever rebooted recently,maybe a driver update.Service pack install corrupted.Check your I.E. settings.Maybe install and reinstall of Anti virus.

Windows Firewall turned on by mistake? Lolly lolly lolly lolly..oops, I turned on windows firewall on accident..
 
Windows Firewall turned on by mistake? Lolly lolly lolly lolly..oops, I turned on windows firewall on accident..

Funny you say that.I have seen IT Pro's during diagnoses turn it Off/On and forget they did that.But the idea of that statement was to check some things the tech or previous tech did. It was only a means to, double check odd but sometimes weird solutions

Computing Solutions is there any offering of solutions/possible issues from you ?
 
Funny you say that.I have seen IT Pro's during diagnoses turn it Off/On and forget they did that.But the idea of that statement was to check some things the tech or previous tech did. It was only a means to, double check odd but sometimes weird solutions

Computing Solutions is there any offering of solutions/possible issues from you ?

I already said probably the ISP is blocking port 25 for spam to whatever@whatever.com..use port 26 for outgoing server and it'll probably work. Of course, it could be more advanced than that, but that's likely the problem.

True..I got you. Someone could have turned off Windows Firewall, but then it wouldn't be blocking anything. Chances are the router won't block port 26.
 
Last edited:
I already said probably the ISP is blocking port 25 for spam to whatever@whatever.com..use port 26 for outgoing server and it'll probably work. Of course, it could be more advanced than that, but that's likely the problem.

True..I got you. Someone could have turned off Windows Firewall, but then it wouldn't be blocking anything. Chances are the router won't block port 26.

A good possibility.And agree with you,that it could be a possible culprit.Lets hope this is what is causing this persons issue.ISP's don't always tell there customers.And creates issues like this.
 
Windows Firewall was first introduced as part of Windows XP Service Pack 2. Every type of network connection, whether it is wired, wireless, VPN, or even FireWire, has the firewall enabled by default. If it weren't on, I'd be very curious as to why it wasn't for most people.
 
I see what you're getting at, fellas. AT&T might block other ISP or business related e-mail besides the most common ones.

I suppose I could have tried using Tor, but it would have probably timed out. I might hit this guy back up and maybe just copy his settings and try sending it from my location. And if I remember correctly, I'm pretty sure that I tried using a different port number as well without much success.

I have to admit, though, that the Windows Firewall post was funny. But I get what you're saying. Vista's firewall is more advanced than XP's, though, because it also monitors outbound as well as inbound. Because of that, there's more configuration that needs to be taken into consideration with outgoing issues like this.
 
Many ISPs have taken to blocking the default SMTP port 25 and now require a different SMTP port, most often 587.

Verizon is a big ISP here in central Florida and they made the change a while back. The down side was they didn't announce the change! All I knew was that a bunch of customers called me saying that they could receive, but no longer send emails in Outlook, OE, WinMail (etc). I was really p****ed when I found the root cause!
 
Oh...it's AT&T. Yes, I can confirm that they block most smtp traffic to other servers. Additionally, if you use their SMTP servers to send with a non-att e-mail, you have to log into their webmail client and add that other e-mail as a trusted e-mail source, then confirm it with a code or a link. It's completely absurd.
 
Oh...it's AT&T. Yes, I can confirm that they block most smtp traffic to other servers. Additionally, if you use their SMTP servers to send with a non-att e-mail, you have to log into their webmail client and add that other e-mail as a trusted e-mail source, then confirm it with a code or a link. It's completely absurd.

Could you elaborate further on that exact procedure?

Also, do you think if I called ATT that they would tell me if they were blocking it? I wouldn't even know which number to call since they have so many.
 
Sure, though you will likely want to find another way to make this work because you won't be able to send through AT&T's SMPT servers if you're on a different ISP.

First, you have to have the username and password that is the main account on the DSL service. You log into that account at http://att.yahoo.com/mail

From there, just follow these directions:

http://help.yahoo.com/sbc/tutorials/mmail/mm_accessother2.html

See also "Sending Mail Using another e-mail address" on the same page.


Edit: Att tech support was absolutely no help in getting around this "feature". They'd probably say that they're not blocking it, you just have to jump through their hoops.
 
Back
Top