Cannot Sent pop mail

[Marc Seidler]

I have a client with a strange problem.
Outlook 2003, WinXP Sp2
The system was sending and receiving mail fine last week.
It now only receives mail. I get an error during the send/receive that the
server cannot be reached.
I double checked the account settings, removed and recreated the account.
I created the account in OE and it works fine. I then imported the OE
account into Outlook and still I cannot send.
In ran Detect and Repair and still no send.
I ran winfix to rebuild the TCP stack. I scanned with Adaware and Spybot
and the system is clean. I uninstalled Norton 2004 and installed Norton
Corp (removes some of the worm scanners, etc)
They have perfect Internet. This is on a Lan through a router and 6 other
users have no problem with Outlook reaching the SMTP server. This system is
using outgoing.Verizon.net as the outgoing server.

 

[Vanguard]

I have a client with a strange problem.
Outlook 2003, WinXP Sp2
The system was sending and receiving mail fine last week.
It now only receives mail. I get an error during the send/receive that
the server cannot be reached.
I double checked the account settings, removed and recreated the account.
I created the account in OE and it works fine. I then imported the OE
account into Outlook and still I cannot send.
In ran Detect and Repair and still no send.
I ran winfix to rebuild the TCP stack. I scanned with Adaware and Spybot
and the system is clean. I uninstalled Norton 2004 and installed Norton
Corp (removes some of the worm scanners, etc)
They have perfect Internet. This is on a Lan through a router and 6 other
users have no problem with Outlook reaching the SMTP server. This system
is using outgoing.Verizon.net as the outgoing server.

Enable transport logging and look at the lines containing "SMTP" (Microsoft
is an idiot when it comes to recording entries in a logfile in that they
show the function calls instead of a decent logfile, so you'll have to find
those lines with "POP" and "SMTP" as the string value showing what command
was sent and what data was returned). Enable only 1 account in Outlook in
scheduled settings for the account group (i.e., if there are multiple
accounts, just use one), exit Outlook, kill any old copy of the logfile
(%temp%\opmlog.log, as I recall), load Outlook, compose an e-mail, and click
Send/Receive. Then exit Outlook and review the logfile.

You never mentioned what else you did to resolve the problem. Did you
disable the firewall? Did you disable e-mail scanning in the anti-virus
program? Did you disable the anti-virus program entirely? Did you start
Outlook in safe mode ("outlook.exe /safe")? Did you reboot Windows to start
it in Safe Mode to help reduce whatever you are loading on Windows startup?
Can you traceroute from the problematic host to the SMTP server? Does the
SMTP server respond to a ping (not all do)?

 

[Chipper]

Don't know if this is of any relevance here but I had a similar issue some
weeks back.

I found out that my email server (earthlink.net) now requires users to log
on to the outgoing server also.

In Outlook get into the eMail Account Settings (POP3) and select "More
Settings".

Select the "Outgoing Server" tab and select "My outgoing server (SMTP)
requires authentication"......

Then select "Log on using...." and enter the user settings and select
"Remember Password".

Do not select the option to "Use the same settings as the incoming server".

Do not select "Log on to incoming server ....." at the bottom of the
options.

Click OK... Next..... Finish..... and exit Outlook.

Restart Outlook.

Should be okay now.

Also check with verizon.net if they changed the outgoing server name.
Earthlink and some onthers have changed the "smtp." part to "smtpauth". All
this something to do with attempting to stop spam or whatever.

HTH.

Chipper

 

[Marc Seidler]

I had uninstalled Norton 2004 and tried it and then installed Norton Corp.
AV and it still did not work.
There is and was only 1 account.
Yes outgoing authentication is needed and was set that way with the correct
user name and pw. Remember that it works fine in Outlook Express on this
machine. The issue is in Outlook 2003.
I did not try and ping the server as since Outlook Express works then it
should not be a tcp issue in windows but again an Outlook issue. It is
possible that Norton during an upgrade of 2004 something got messed up.
According to Symantec this is a known possible issue and that getting the
updates a 2nd time will resolve it. This did not help at all and
uninstalling the product also did not help. In there a 2nd TCP setting in
the reg specific to Outlook regarding port selection/proxy etc?