Re: email not sending from Outlook 2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

It's Norton AV 2009, staying on top of updates. Now I'm remembering I may
have had a similar problem a few years back with McAfee on another system.
I'll ask my email provider if port 587 is OK. I'll let you know what
happens after I install Norton AV.
Thanks, Dennis

"VanguardLH" wrote:

Dennis wrote:

Well, I ran that Symantec cleanup utility, and the result was the same,
unable to send emails. I also made sure that SSL was unchecked, and it was,
always has been. HOWEVER, for the outgoing server (SMTP), I changed the
number to 2525 from 25, and, for now, it's working again. Very strange. If
you can illuminate me as to what happened there, how the number might have
changed on its own, I'm all ears.

So, I'll be re-installing Norton Anti Virus (nothing else), and we'll see
what happens. Any warnings I should pay attenion to when re-installing
Norton AV?

Looks like Norton change the port so your e-mail client would connect to
their local proxy. I have never heard of an e-mail provider using port
2525. So Norton changed your e-mail account settings but didn't change them
back when you uninstall it. Reinstalling Norton will probably have it alter
your account settings again so e-mail traffic goes to their local proxy.
However, most AV programs no longer interfere in this manner and instead use
a transparent proxy to intercept your e-mail traffic. That means your
account settings in your e-mail client are not altered, especially since the
AV programs only understand a few common e-mail apps to know how to change
their account settings. Is this a really old version of Norton, like on or
before 2003? That was the last time I used Norton stuff and, as I recall,
they had already switched to using a transparent proxy.

By the way, while port 25 might work, many ISPs and e-mail providers are
changing to port 587. Port 25 was meant only to communicate between MTAs
(mail transfer agents, like SMTP mail hosts), not for MUAs (mail user
agents, like your e-mail client). Back in 1999 an RFC was ratified to
change MUAs to use port 587. ISPs and e-mail providers have been slowly
migrating to that recommended port number. Also, many ISPs will block
traffic over port 25 since trojan mailbots on infected hosts use that port.
So check if your e-mail provider also listens on port 587. If they haven't
yet switched, they will eventually. As always, you have to match on
whatever settings your e-mail provider tells you to use.
.

.

Relevant Pages

  • Re: Telnet, Ping and Port 1025
    ... >>I do have Norton AV and Firewall installed, ... > outgoing packets for any particular port. ... > telnet server running and the port open to accept telnet ...
    (microsoft.public.security.virus)
  • Re: NIS 2003 Help With
    ... Norton shows the IP Address to be mine ... NPF 02 we do not even show a port scan from Norton's ... > NIS 2003 rule allows the server to receive incoming ... > Try running the Norton web site test again. ...
    (comp.security.firewalls)
  • Re: Telnet, Ping and Port 1025
    ... >was Norton's own on-line security check that revealed the Telnet, Ping ... Norton doesn't seem, by default, to lock down all ports. ... outgoing packets for any particular port. ...
    (microsoft.public.security.virus)
  • Re: email not sending from Outlook 2003
    ... So, I'll be re-installing Norton Anti Virus, and we'll see ... Looks like Norton change the port so your e-mail client would connect to ... So Norton changed your e-mail account settings but didn't change them ... So check if your e-mail provider also listens on port 587. ...
    (microsoft.public.outlook.general)
  • Re: Help
    ... When power came back everything was fine, but my outlook express ... Called Linksys and they said everything is fine, call Norton. ... "The connection to the server has failed. ... port is still open. ...
    (microsoft.public.windows.inetexplorer.ie6.outlookexpress)