From: VanguardLH on
Dennis wrote:

> "The specified server was found, but there was no response from the server.
> Please verify that the port and SSL info is correct........"
> The other message is:
> "Outlook could not connect to the outgoing mail server (SMTP). The problem
> could be the server neam or port, or your server may not support SSK. Verify
> ....."

So did you configure the e-mail account defined within Outlook to use SSL?
Does the mail server support or demand the use of SSL to connect to it? You
need Outlook to match the settings used by the mail server. If the mail
server doesn't support SSL then you can't use it in Outlook. If the mail
server supports SSL and *if* you choose to use it then you need to use the
correct port. When SSL is supported, a different port is used to listen for
those SSL-enabled connections. If the mail server demands that SSL must be
used to connect to it (e.g., Gmail) then you must enabled SSL in the e-mail
account that you define within Outlook.

If SSL is being used, the time on the client and server must be with a
minute, or so, of each other. The handshaking involved before an SSL
connection is established has a timestamp within it. That handshaking will
expire if it takes too long. If the clock is off on either the client or
server (actually if the time is too different between client and server)
then it makes appear that the handshaking has expired and the session is
aborted. Check the clock on your host has the correct time and the timezone
is correct.
From: Dennis on
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?
Thanks again for your suggestions.
Dennis


"VanguardLH" wrote:

> Dennis wrote:
>
> > As I stated before, but perhaps not clearly enough, I've removed Norton Anti
> > Virus software from my computer. I haven't re-installed.
>
> Sorry, I missed that you UNinstalled the Norton product(s) (and presumably
> anything else that interrogates your e-mail traffic). To ensure that all of
> Norton's stuff is off your computer, Symantec has a cleanup utility to
> ensure all remnants of their software get uninstalled. Rather than dig
> around Symantec's web site, I just did a Google search and found:
>
> http://www.softpedia.com/get/Tweak/Uninstallers/Norton-Removal-Tool.shtml
>
> If you don't want to get the copy from Softpedia, their download page has a
> link to Symantec's FTP server to get the removal program.
>
> Since you never mentioned seeing an error message, I'll have to assume there
> never has been an error message during an send operation.
>
> At this point, you might have to enable the troubleshooting logs in Outlook
> to see what gets listed in the mail session between it and the mail server.
>
> Defining a new mail profile might work, too.
> .
>
From: VanguardLH on
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.
From: Dennis on
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.
> .
>