AT&T/BellSouth.net sending e-mail problems
Nohbody
as I've done for ages now, as previously recent as Friday
evening. Only this time, I received the error message "Server
mail.bellsouth.net rejected your username and password (Weak
authentication mechanism require TLS/SSL encryption)."
I'm not, generally, an idiot, so I went into the settings for
Agent (the one I'm typing this in, v5.0), and enabled SSL for
sending e-mail (receiving doesn't seem to mind being via a
non-secure connection).
Problem is the server isn't responding at all and timing out, so
I try the TLS option, but get the same login rejection error as I
did without any encryption at all.
I've temporarily disabled the firewall on my router, and the
modem's firewall has been disabled since the start (seemed pretty
"tits on a bull" useless), so I'm pretty sure it's not being
intercepted by a firewall rule.
Am I missing something, or do I have to use a phone beat on
AT&T's (non)help desk about a problem solely with their service?
Their online help thingy doesn't acknowledge that Forte Agent
even exists, so I can't use that, further continuing my opinion
of the online help thingy's suckitude, based on previous issues.
Dan Poore
--
About the only difference between the wingnuts on each end of
the [political] spectrum is *which* civil right(s) they think we
can do without. -- Rowan Hawthorn, in alt.callahans (2/28/05)
Bad Boy Charlie
wrote:
>This morning, I tried to send an e-mail via mail.bellsouth.net,
>as I've done for ages now, as previously recent as Friday
>evening. Only this time, I received the error message "Server
>mail.bellsouth.net rejected your username and password (Weak
>authentication mechanism require TLS/SSL encryption)."
>
>I'm not, generally, an idiot, so I went into the settings for
>Agent (the one I'm typing this in, v5.0), and enabled SSL for
>sending e-mail (receiving doesn't seem to mind being via a
>non-secure connection).
>
>Problem is the server isn't responding at all and timing out, so
>I try the TLS option, but get the same login rejection error as I
>did without any encryption at all.
>
>I've temporarily disabled the firewall on my router, and the
>modem's firewall has been disabled since the start (seemed pretty
>"tits on a bull" useless), so I'm pretty sure it's not being
>intercepted by a firewall rule.
>
>Am I missing something, or do I have to use a phone beat on
>AT&T's (non)help desk about a problem solely with their service?
>Their online help thingy doesn't acknowledge that Forte Agent
>even exists, so I can't use that, further continuing my opinion
>of the online help thingy's suckitude, based on previous issues.
>
>Dan Poore
Yes perhaps. Ever since BellSouth / AT&T did the 'Yahoo merger' they
have gone to SSL for incoming and outgoing email servers. You'll need to
set incoming (pop3) SSL mail to use port 95 and outgoing (smtp) SSL mail
to use port 465. I stopped using my BellSouth mail accounts many months
ago since even before this SSL thing they were often times a cyber black
hole and email would just vanish. By comparison yahoo or Gmail are
reliable and can also be setup in an email client if you don't care for
the web interface. Good luck with BellSouth!!!! Oh the memories....
Tecknomage
wrote:
> This morning, I tried to send an e-mail via mail.bellsouth.net,
> as I've done for ages now, as previously recent as Friday
> evening. Only this time, I received the error message "Server
> mail.bellsouth.net rejected your username and password (Weak
> authentication mechanism require TLS/SSL encryption)."
>
> I'm not, generally, an idiot, so I went into the settings for
> Agent (the one I'm typing this in, v5.0), and enabled SSL for
> sending e-mail (receiving doesn't seem to mind being via a
> non-secure connection).
>
> Problem is the server isn't responding at all and timing out, so
> I try the TLS option, but get the same login rejection error as I
> did without any encryption at all.
>
> I've temporarily disabled the firewall on my router, and the
> modem's firewall has been disabled since the start (seemed pretty
> "tits on a bull" useless), so I'm pretty sure it's not being
> intercepted by a firewall rule.
>
> Am I missing something, or do I have to use a phone beat on
> AT&T's (non)help desk about a problem solely with their service?
> Their online help thingy doesn't acknowledge that Forte Agent
> even exists, so I can't use that, further continuing my opinion
> of the online help thingy's suckitude, based on previous issues.
>
> Dan Poore
I see your email provider is BellSouth. Check with them on how to use
SMTP TLS/SSL. Use MAY require a special Port setting. Also check
your logon setting requirements. I *suspect* that if you use SSL you
cannot use the same logon as your POP3 *if it's NOT SSL* (POP & SMTP
must be both SSL to use the same logon).
My DSL ISP = AT%T/BellSouth but I use a different email provider. My
email provider uses a specific Port for TLS/SSL (which I do not use by
the way), and IF I remember correctly, there is something else I have
to setup on my account to use SSL.
--
======== Tecknomage ========
Computer Systems Specialist
IT Technician
San Diego, CA
Nohbody
monkeys bang out the following:
[snip of stuff]
For a VERY belated follow-up, the problem was just a temporary
issue with the BellSuck mail server. It cleared up about a day or
so later, and has been letting me send stuff without problems.
(Well, as far as the mail server is concerned, anyway. The
internet connection being a temperamental [female dog] is another
issue. :P )