551 not our customer when forwarding mail outlook

[Carmel]

Same thing here. Started this morning. Using Bellsouth.net as my
outgoing mail server. Use Outlook at home and auto download my emails
from Bellsouth.net and yahoo.com. But today, i can't forward or send
any email messages, only recieve. Getting the sam message you are.

You might try one of these links:

https://webauth.att.net/auth/webmai...S/v/wmgoto/4B811A410002932D000033BC2223065062

http://localization.att.com/loc/con...=http://www.att.com/esupport/index.jsp?cv=102

Perhaps you might find something useful there. In any case, the problem
is not Outlook, a rarity I admit, but rather with the downstream ISP.

--

Carmel |::::=======
|::::=======
|===========
|===========
|

 

[Hank Bailey]

Using Bellsouth.net and having the same issue about last 48 hours.

 

[Thomas]

It's driving me nuts...551 not our customer. I've tried everything I can think of to fix it.

 

[Hank Bailey]

Just got this message on an ATT chat;

I apologize but we are undergoing a system maintenance. Would you please try
to check your client email program later today and see if it will work then.
This maintenance is intended to improve the service we offer you and we
regret any inconvenience. For the mean time, we suggest that you access your
email account online or we can temporarily change your outgoing mail server
and see if this resolve the issue.

 

[Gary]

My original problem..

"Same problem here. Started yesterday, 4/19/10. Newly created e-mail go out but not fwd or reply. Is it an Outlook or ISP issue? Happens with both Outlook XP on an XP machime and Outlook 07 on a Vista machine. I use BellSouth, i.e. AT&T DSL.

... has now gotten worse not better. No outgoing mail what so ever. No fwd, no reply, not even new msgs. Comes back immediately with 551 not our customer. Unless of course I send a msg to another bellsouth.net address. Dead give-a-away as to where the problem lies

 

[N. Miller]

I get returned mail with the error "551 not our customer" when trying to
forward mail. I can send new mail to the same contacts with no problem.

The commonality in this thread seems to be former Bellsouth customers. I
wonder if this forum thread will help?

<http://www.dslreports.com/forum/r23833442-Services-Unable-to-send-email-via-mailbellsouthnet>

FWIW, I am a former SBC customer who did migrate to the "SBC Yahoo! DSL
Service", now called, "at&t Yahoo! HSI", back in December, 2002, when it was
first rolled out. At the present, AT&T seems content to not apply much
effort to running their email service, or to bird dogging Yahoo! about
problems with their email service. I suspect that they believe email service
to be a net cost, no profit service. Probably time to either switch
providers (if you think a competitive provider in your area is better with
email; but most ISPs are not), or find an alternative email service provider
(which has the advantage of not tying you to one ISP).

 

[ddpinto2693]

I am having this problem on 3 different email accounts, only one of them is
bellsouth.net. I saw a previous note that this was not an Outlook problem. I
do not believe that. One email provider suggestedt his was a conflict
between a recent OS security patch and Outlook 2007.

 

[ddpinto2693]

Update to my recent post. AFter pondering this, I now realize the
mail.bellsouth.net ismy outgoing mail server for all 3 accounts. Later in
this thread, I did see someone who contacted ATT/Bellsouth and got a 'we are
doing some maintenance. check it later to see if it resolves itself'
response. That sure looks like a 'we screwed up and we are fixing it' answer.

DDP

 

[bobbiestaten]

It is a Bell South error. When they changed to Att some customers still had
bell south and some had att pop addresses. Their latest update last night
crunched things. Change your email settings to: Pop server in =
Pop.att.yahoo.com out= SMTP.att.yahoo.com Also uncheck lon on using
secure server if it was checked. On advanced tab change in and out port
numbers in= 995 out=465 Hope this helps. Call them at 8883212375 if this
doesn't fix it

 

[Carmel]

It is a Bell South error. When they changed to Att some customers
still had bell south and some had att pop addresses. Their latest
update last night crunched things. Change your email settings to:
Pop server in = Pop.att.yahoo.com out= SMTP.att.yahoo.com Also
uncheck lon on using secure server if it was checked. On advanced
tab change in and out port numbers in= 995 out=465 Hope this
helps. Call them at 8883212375 if this doesn't fix it

Actually, both port 25 & 587 work equally as well.

$ telnet smtp.att.yahoo.com 25
Trying 66.196.96.87...
Connected to smtp.sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
220 smtp102.sbc.mail.re3.yahoo.com ESMTP
^]
telnet> quit
Connection closed.

$ telnet smtp.att.yahoo.com 587
Trying 76.13.12.104...
Connected to smtp.sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
220 smtp103.sbc.mail.ac4.yahoo.com ESMTP
^]
telnet> quit

Both are preferable over 465 which was never a standard and is
virtually unsupported. It is only kept on life support for users of
depreciated versions of Outlook. There is one caveat; port 25 may be
blocked by your ISP. If so, use 587 instead.

In addition, I was able to connect via port 110 for POP service;
however, port 995 failed. I am not sure why yet.

$ telnet pop.att.yahoo.com 110
Trying 68.142.229.14...
Connected to pop-sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
+OK hello from popgate 2.45 on pop115.sbc.mail.re2.yahoo.com
capa
+OK CAPA list follows
EXPIRE NEVER
IMPLEMENTATION popgate 2.45
PIPELINING
RESP-CODES
TOP
UIDL
USER
..
quit
Connection closed by foreign host.

$ telnet pop.att.yahoo.com 995
Trying 68.142.229.14...
Connected to pop-sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
capa
Connection closed by foreign host.

--
Carmel |::::=======
|::::=======
|===========
|===========
|

 

[rmbru2k]

ATT TECH SUPPORT UPDATE FEB. 21, 2010

I am a Bellsouth client. I contacted tech support. They said that the issue
is new within the past 24 hours. They are aware of the issue and are working
on it. It is my understanding and theirs that clients can recieve incoming
mail, but cannot send to numerous email provider accounts, "551 not our
customer."

Tech Spt said to please be patient as they are addressing the issues, but to
give them 72 hours to fix the problem. Tech Spt said that if you do not see
the problem is resolved after 72 hours to call and inform them of such. The
number to ATT tech support is (888) 321-2375, option tech support or DSL.

They are not requesting payments to fix the problem. If somebody requires a
payment, DO NOT PAY. Inform them that it is an ATT issue and clients are not
being required to pay. You are paying customers and this is an issue on their
end.

My advice: Be patient. Don't lose your mind. Don't be disrespectful. It is
an inconvenience to many including myself. This stuff happens. They are
simply keeping up to date with the technological changes to provide the best
services to their clients and customers. Don't make any changes to your
accounts; just hang in there and use an alternate communication method until
the problem is fixed.

 

[Robin]

Where do I do this??
I went to tools>options>mail set up>e-mail accounts...... Then what?

 

[ladydi]

ATT TECH SUPPORT UPDATE FEB. 21, 2010

I am a Bellsouth client. I contacted tech support. They said that th
issue
is new within the past 24 hours. They are aware of the issue and ar
working
on it. It is my understanding and theirs that clients can reciev
incoming
mail, but cannot send to numerous email provider accounts, "551 no
our
customer."

Tech Spt said to please be patient as they are addressing the issues
but to
give them 72 hours to fix the problem. Tech Spt said that if you do no
see
the problem is resolved after 72 hours to call and inform them of such
The
number to ATT tech support is (888) 321-2375, option tech support o
DSL.

They are not requesting payments to fix the problem. If somebod
requires a
payment, DO NOT PAY. Inform them that it is an ATT issue and client
are not
being required to pay. You are paying customers and this is an issue o
their
end.

My advice: Be patient. Don't lose your mind. Don't be disrespectful. I
is
an inconvenience to many including myself. This stuff happens. The
are
simply keeping up to date with the technological changes to provide th
best
services to their clients and customers. Don't make any changes t
your
accounts; just hang in there and use an alternate communication metho
until
the problem is fixed.


problem.

I called their DSL support and a very patient AT&T lady (India) walke
me thru the re-registration and reformatting the account...it's now
yahoo.POP3...so now all is back to normal. Had nothing to do wit
Outlook. Whew. Of course, NOW I have hundreds of old read emails tha
are showing as unread. Argh. Technology

 

[Frank H]

Just connected with BellSouth/ATT phone line person who advised that problem
is on their end and that they have no indication of when it will be fixed.
Attendant referred to the problem as maintenance (maybe gone seriously
wrong!). Frank H

 

[Jim Patrick]

I can not send email. The 551 error message appears.

 

[Ben Spotts]

I found the answer and how to fix it! AT&T will finally get aroudn to
telling us - someday maybe.

http://www.att.com/esupport/article.jsp?wtSlotClick=1-002HEW-0-1&sid=KB401738
will get you started. Need to change your acount settings.




Go to

 

[jupitertom]

I have had the "551 not our customer" issue as well since the evening o
Feb 19 (using Outlook 2007). I was finally able to reach Bellsout
(AT&T) customer service. They told me it is definitely an interna
Bellsouth issue (blamed it on a server issue). They said do NOT chang
any settings - be patient and use the internet version of email (Yahoo)
The lady I spoke to seemed extremely knowledgeable and said no firm dat
is yet available for the correction.

I much prefer Outlook but will be patient for a day or so - no reaso
why this should take this long if they put people on it.

I would like to know if anyone changed the in and out servers lik
someone posted earlier. I asked the lady I sopks to if that would hal
and she said do not do this as it could only worsen things on my end
Anyone else try the change and results if you did? Thanks, To

 

[AFKuhr]

DID NOT WORK

It is a Bell South error. When they changed to Att some customers
still had bell south and some had att pop addresses. Their latest
update last night crunched things. Change your email settings to:
Pop server in = Pop.att.yahoo.com out= SMTP.att.yahoo.com Also
uncheck lon on using secure server if it was checked. On advanced
tab change in and out port numbers in= 995 out=465 Hope this
helps. Call them at 8883212375 if this doesn't fix it

Actually, both port 25 & 587 work equally as well.

$ telnet smtp.att.yahoo.com 25
Trying 66.196.96.87...
Connected to smtp.sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
220 smtp102.sbc.mail.re3.yahoo.com ESMTP
^]
telnet> quit
Connection closed.

$ telnet smtp.att.yahoo.com 587
Trying 76.13.12.104...
Connected to smtp.sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
220 smtp103.sbc.mail.ac4.yahoo.com ESMTP
^]
telnet> quit

Both are preferable over 465 which was never a standard and is
virtually unsupported. It is only kept on life support for users of
depreciated versions of Outlook. There is one caveat; port 25 may be
blocked by your ISP. If so, use 587 instead.

In addition, I was able to connect via port 110 for POP service;
however, port 995 failed. I am not sure why yet.

$ telnet pop.att.yahoo.com 110
Trying 68.142.229.14...
Connected to pop-sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
+OK hello from popgate 2.45 on pop115.sbc.mail.re2.yahoo.com
capa
+OK CAPA list follows
EXPIRE NEVER
IMPLEMENTATION popgate 2.45
PIPELINING
RESP-CODES
TOP
UIDL
USER
..
quit
Connection closed by foreign host.

$ telnet pop.att.yahoo.com 995
Trying 68.142.229.14...
Connected to pop-sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
capa
Connection closed by foreign host.

--
Carmel |::::=======
|::::=======
|===========
|===========
|

.

 

[AFKuhr]

CALL CENTER IS OVERWHELMED, WAIT TIME IS AN HOUR, AND THERE IS A STANDARD
MESSAGE THAT SAYS THEY ARE WORKING ON THE REGION WIDE OUTTAGE THAT AFFECTS
EMAIL, INTERNET & WEBMAIL - GOOD OL' BELLSOUTH!!!

It is a Bell South error. When they changed to Att some customers
still had bell south and some had att pop addresses. Their latest
update last night crunched things. Change your email settings to:
Pop server in = Pop.att.yahoo.com out= SMTP.att.yahoo.com Also
uncheck lon on using secure server if it was checked. On advanced
tab change in and out port numbers in= 995 out=465 Hope this
helps. Call them at 8883212375 if this doesn't fix it

Actually, both port 25 & 587 work equally as well.

$ telnet smtp.att.yahoo.com 25
Trying 66.196.96.87...
Connected to smtp.sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
220 smtp102.sbc.mail.re3.yahoo.com ESMTP
^]
telnet> quit
Connection closed.

$ telnet smtp.att.yahoo.com 587
Trying 76.13.12.104...
Connected to smtp.sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
220 smtp103.sbc.mail.ac4.yahoo.com ESMTP
^]
telnet> quit

Both are preferable over 465 which was never a standard and is
virtually unsupported. It is only kept on life support for users of
depreciated versions of Outlook. There is one caveat; port 25 may be
blocked by your ISP. If so, use 587 instead.

In addition, I was able to connect via port 110 for POP service;
however, port 995 failed. I am not sure why yet.

$ telnet pop.att.yahoo.com 110
Trying 68.142.229.14...
Connected to pop-sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
+OK hello from popgate 2.45 on pop115.sbc.mail.re2.yahoo.com
capa
+OK CAPA list follows
EXPIRE NEVER
IMPLEMENTATION popgate 2.45
PIPELINING
RESP-CODES
TOP
UIDL
USER
..
quit
Connection closed by foreign host.

$ telnet pop.att.yahoo.com 995
Trying 68.142.229.14...
Connected to pop-sbc.mail.fy4.b.yahoo.com.
Escape character is '^]'.
capa
Connection closed by foreign host.

--
Carmel |::::=======
|::::=======
|===========
|===========
|

.

 

[scotth67]

As of 4:45 CST, the problem seems to be fixed. I can send to anyone; receiving never was a problem. Sure would have been nice to have some sort of notice about it. A blanket email would have done the trick. In any case, I think they have it resolved.