"Bob W" wrote in message
...
Checking the "Authentication" box fixed it.
I wonder why it wasn't [was?] working before since I have done
nothing
with my accounts?
E-mail providers change their requirements. Some are slow to
implement anti-spam measures. Many now want to ensure you have
permission to use their resources rather than a spammer trying to hide
on another domain while using someone else's mail server.
For info on off-domain port 25 (SMTP) traffic blocked to thwart spam
from spamming or infected customers, read:
http://www.commercestreet.com/Blocking_Port_25.htm
http://help.yahoo.com/help/us/mail/pop/pop-38.html
http://www.postcastserver.com/help/P..._Blocking.aspx
http://www.aota.net/Troubleshooting/port25.php4
http://www.spamhaus.org/faq/answers....0Spam%20Issues...
http://www.findarticles.com/p/articl.../ai_ziff129473
http://www.google.com/search?q=%2Bbl...2BSMTP+%2Bspam
One, some, or all of the following could have changed or are being
implemented:
- Your ISP (the network to which you connect) requires you use their
mail servers. They do not permit you crossing their network to use an
off-domain mail server over which they have no control and cannot log
e-mail traffic that uses their network. Usually this means they block
e-mail traffic using port 25 that targets an off-domain network;
however, it is also possible with protocol analyzers to detect traffic
is for e-mail and block that traffic. This is probably why Gmail opted
to force SSL connects because they use ports other than the standard
of 110 for POP3 and 25 for SMTP since everyone using Gmail is trying
to cross their ISP's network to get at an off-domain mail server.
- The targeted mail server does not allow off-domain connections (or
requires non-standard setup of SSL, different port numbers, and/or SPA
to make off-domain connections). You are crossing your ISP's network
to reach the targeted mail servers, but to those mail servers you are
not on their network when trying to connect to those mail servers
(i.e., you are off-domain to them). You will need to check what
settings AOL requires for off-domain connections which could be
different than for on-domain connections. My ISP (Comcast) is like
that: while on their network, you connect to their mail servers using
110 for POP3 and 25 for SMTP but when coming from off their domain
then you need to use SSL, 995 for POP3, 465 for SMTP, and also use SPA
to connect to their mail servers.
- Some e-mail providers require that you send before you receive. Many
e-mail clients receive first and then send. As a result, the
expectation is that the mail server will reuse the login for the
receive session also for the send session but the send session has to
be within a short time after the login for the receive session (not
from when the receive session ends). If there are lots of mails or
delays, too much time elapses and those login credentials for the
receive session are lost so you cannot send. The cure is to enter your
login credentials for the send session (SMTP) or to change the order
of sessions within your e-mail client (send and then receive). Maybe I
missed it but I don't see an option in OE (so it probably isn't there
in WLM) to change the order of the sessions (i.e., to receive first
and then send, or to send first and then receive). Instead and when
defining e-mail accounts in any e-mail client, I always configure the
SMTP server settings to require authentication and then specify the
same login credentials as for the POP3 server (rather than say to
reuse them). This means I have to twice enter my login credentials:
once for the POP3 configuration and again for the SMTP configuration.
Just because you don't change anything doesn't mean your e-mail
provider cannot.