asked on

Out going emails suddenly being delayed from my Exchange 2003 SBS server.

Just his week my emails are suddenly being mysteriously delayed and then not delivered. I don't know what is going on. This server has been sending emails reliable for many years. It is an Exchange 2003 server running on SBS2003. I checked to see if my server is blacklisted, and it does not appear to be. It has cause some undo stress for my business not having emails delivered in a timely manner.

Any Ideas? email server is home.888phantom.com IP address is static 75.160.160.33.

The only change that was recently made is an increase in DSL line speed from 3 mb to 5 mb.

SOLUTION

Sjizzel

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

BelushiLomax

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rjessop

ASKER

OK,

I run through the internet & email setup wizard to double check my settings, and all are as they should be - in this wizard I choose "use DNS to deliver". I've opened up exchange manager and look at the Que under my server and there is a list of all the recent messages (last two days) that haven't already been returned undeliverable. This Que shows I'm using smtpout.secureserver.net as a smart host, which is the godaddy the server I've been using for about 3 years. I don't remember why I switched to using their server for outgoing relay, instead of just DNS. My guess is something has changed with Godaddy, or my account with them, however, I just spoke to them and they are clueless - don't have much knowledge about SBS/Exchange setup. Any insite on that setup, or what I need to check?

Should I be using an outgoing relay, instead of letting my Server use DNS?

rjessop

ASKER

ok, problem solved. Apparently upgrading/downgrading your Centurylink (Formerly Qwest) DSL service causes them to reset your profile to default, which blocks port 25.

Thanks for your assistance.