issue with bellsouth/at&t
 

Following all instructions given by att for continued use of email (which up
until today had worked flawlessly for years), I now am unable to send email
using Outlook Express. Never before had at&t require authentication, but it
appears they do so now, though I'm not sure when this went into effect.

I simply use the DSL service to send and receive email, but I don't use the
account that was assigned, as I have had an account on a friend's server for
probably 10 years or more.

Now, when I try to send, I get an error message indicating messages are
rejected by the server, with the problem apparently centering around
"requiring a valid sender domain."

I didn't see this in a thread here yet, but this is baffling.

issue with bellsouth/at&t
 

Would you care to share the error message with us? Please post the error
message in its entirety. You can left click on it to highlight and then
right click to copy and then paste it into this thread.

And check your account settings especially the authentication setting.

How To Set Up Outlook Express to Use Your BellSouth E-mail Account:
1:
http://help.bellsouth.net/bellsouth/...3-e36f443f1be5

2:
http://support.att.net/bellsouth/asp...2D0fe13eaa534c
--
Bruce Hagen
MS-MVP Outlook Express
Imperial Beach, CA


"bartidog" wrote in message
...
Following all instructions given by att for continued use of email (which
up
until today had worked flawlessly for years), I now am unable to send
email
using Outlook Express. Never before had at&t require authentication, but
it
appears they do so now, though I'm not sure when this went into effect.

I simply use the DSL service to send and receive email, but I don't use
the
account that was assigned, as I have had an account on a friend's server
for
probably 10 years or more.

Now, when I try to send, I get an error message indicating messages are
rejected by the server, with the problem apparently centering around
"requiring a valid sender domain."

I didn't see this in a thread here yet, but this is baffling.

issue with bellsouth/at&t
 

"bartidog" wrote in message
...

Following all instructions given by att for continued use of email
(which up until today had worked flawlessly for years), I now am
unable to send email using Outlook Express. Never before had
at&t require authentication, but it appears they do so now, though
I'm not sure when this went into effect.

I simply use the DSL service to send and receive email, but I don't
use the account that was assigned, as I have had an account on a
friend's server for probably 10 years or more.

At the risk of stating the obvious, but if you use "a friend's server"
to send email, then the "instructions given by att for continued use of
email" do _not_ apply (except maybe having port 25 unblocked, but that's
always been the case).

That said, I am more familiar with att's sbc-land than bellsouth. But
given http://www.dslreports.com/faq/bellso...mail_Info#9129
the rules and loops appear to be similar. And chances are better on the
dslreports.com dedicated forum that you'll find bellsouth-specific
advice.

issue with bellsouth/at&t
 

Thanks for the kind replies. I hope I won't offend anyone by top-posting here.

Without going into too much detail, mail will now send mail through
bellsouth, with my "usual" return address (with a different domain name) with
no apparent problems.

This is the first time I've ever had to fill in under the
accounts/properties/servers that "My server requires authentication", but
hey, as long as it works.

Perhaps it was just a hiccup that's just managed to go away. I'm hoping so.

"N. Miller" wrote:

On Wed, 23 Apr 2008 22:35:00 -0700, bartidog wrote:

Following all instructions given by att for continued use of email (which up
until today had worked flawlessly for years), I now am unable to send email
using Outlook Express. Never before had at&t require authentication, but it
appears they do so now, though I'm not sure when this went into effect.

AT&T has always required authentication on certain of their SMTP message
submission servers; mostly legacy SBC servers and associated Yahoo! servers
(SBC being the company which bought AT&T). I have been a customer since it
was SBC, so I really only know the legacy SBC stuff.

AT&T Worldnet may also have required authentication for their SMTP message
submission servers.

One of my old, legacy SBC SMTP message submission servers
('mail.pacbell.net') just changed to require authentication. This may be
indicative of a move to unify all AT&T SMTP service under a single set of
rules.

Bellsouth is no longer an independent company; they were bought by AT&T (the
new SBC-run AT&T, the old AT&T management retired after SBC bought them).
The old Bellsouth SMTP message submission servers are no longer in Bellsouth
IP space, they were move to AT&T Worldnet Services IP addresses a long time
ago. My guess is, AT&T is eventually going to require *all* of their
subscribers to use authenticated SMTP for email message submission.

I simply use the DSL service to send and receive email, but I don't use the
account that was assigned, as I have had an account on a friend's server for
probably 10 years or more.

Now, when I try to send, I get an error message indicating messages are
rejected by the server, with the problem apparently centering around
"requiring a valid sender domain."

Now you are discussing a non-AT&T service. AT&T has nothing to do with the
requirements of your friend's SMTP message submission server; your friend
runs that server, not either AT&T Worldnet Services (for the 'att.net' and
'bellsouth.net' domains), or AT&T Internet Services (for the nine legacy SBC
domains). In fact, AT&T Worldnet Services (and Bellsouth, before them) have
always blocked port 25 access to SMTP message submission servers outside of
their respective IP networks. Even AT&T Internet Services blocks outbound
port 25 (but, unlike ATTW (for 'att.net' and 'bellsouth.net'), ATTIS will
unblock port 25 access on request).

I didn't see this in a thread here yet, but this is baffling.

Well, that makes two of us. Baffled, that is. Are you trying to connect to
'mail.bellsouth.net', or some other server? Please let us know because the
key to answering your question depends upon where you are trying to connect.

--
Norman
~Shine, bright morning light,
~now in the air the spring is coming.
~Sweet, blowing wind,
~singing down the hills and valleys.

issue with bellsouth/at&t
 

"bartidog" wrote in message
...
Thanks for the kind replies. I hope I won't offend anyone by top-posting
here.

Without going into too much detail, mail will now send mail through
bellsouth, with my "usual" return address (with a different domain name)
with
no apparent problems.

This is the first time I've ever had to fill in under the
accounts/properties/servers that "My server requires authentication", but
hey, as long as it works.

Perhaps it was just a hiccup that's just managed to go away. I'm hoping
so.
I can only speak about sbcglobal... That ISP told us of the upcoming change
to require authentication well over two years ago.
However, the old non authenticated method continued to work until just
recently. They have now enforced the rules. And, you need to use
different ports as well.
Jim
snip

issue with bellsouth/at&t
 

Jim wrote:
"bartidog" wrote in message
...
Thanks for the kind replies. I hope I won't offend anyone by top-posting
here.

Without going into too much detail, mail will now send mail through
bellsouth, with my "usual" return address (with a different domain name)
with
no apparent problems.

This is the first time I've ever had to fill in under the
accounts/properties/servers that "My server requires authentication", but
hey, as long as it works.

Perhaps it was just a hiccup that's just managed to go away. I'm hoping
so.
I can only speak about sbcglobal... That ISP told us of the upcoming
change
to require authentication well over two years ago.
However, the old non authenticated method continued to work until just
recently. They have now enforced the rules. And, you need to use
different ports as well.

AT&T is the new coporate name for SBC/Global which acquired the most recent
AT&T corporation, BellSouth, PacBell, Southwestern Bell, and a host of other
Baby Bells recently; cf. http://www.att.com/gen/investor-relations?pid=5711
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/