dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
2326
ekf
join:2003-07-10
Little Rock, AR

ekf

Member

ATT blocking email clients 5.5.4 invalid argument

I have DSL since 2003 and both sbcglobal.net and att.net POP/SMTP email addresses.
In ATT's notice re: webmail change, no mention of blocking email clients. I can receive, but cannot send. SMTP server returns 5.5.4 Invalid Argument.

In Chat, ATT rep told me ATT had blocked email client use. Then he offered to remotely view my screen. So why would looking at my screen help ME if ATT is blocking email clients?

It would not.

Last year, I tried to save family member's sbcglobal.net address, which had been connected to their Uverse account, which got turned off for a week while they were ill. 10 years of email gone, because ATT "can't find" the software to access the sbcglobal.net accounts. No warning. We didn't want sbcglobal.net email attached to the Uverse account, and certainly were not informed that the email account would be deleted if Uverse was disconnected, even voluntarily. ATT paid a Uverse technician for 6 hours while we sat on the phone trying to get it back.

from att email 05.08.2013:
"There is no impact to your email IDs, saved messages, webmail folders, passwords, email client settings, or service, based on this upgrade."

I praise my intuition for setting up a private (as such) POP/SMTP email account to replace my att accounts two weeks ago, but had not begun using it yet.

They desperately try to control customers which only drives them away faster.

Hayward0
K A R - 1 2 0 C
Premium Member
join:2000-07-13
Key West, FL

Hayward0

Premium Member

I have never used BSo/ATT mail EVER. And still works fine. What they do block is the standard SMTP port 80? so you need to set the client to use an alternate port for sending.

NormanS
I gave her time to steal my mind away
MVM
join:2001-02-14
San Jose, CA
TP-Link TD-8616
Asus RT-AC66U B1
Netgear FR114P

NormanS

MVM

said by Hayward0:

What they do block is the standard SMTP port 80?

No. Port is not the normal SMTP port; it is the standard HTTP port.

SMTP is port 25, which is blocked.
NormanS

NormanS to ekf

MVM

to ekf
said by ekf:

I have DSL since 2003 and both sbcglobal.net and att.net POP/SMTP email addresses.
In ATT's notice re: webmail change, no mention of blocking email clients. I can receive, but cannot send. SMTP server returns 5.5.4 Invalid Argument.

How did you configure the client? Since the SBC days, "username" has to be the full email address.

In Chat, ATT rep told me ATT had blocked email client use. Then he offered to remotely view my screen. So why would looking at my screen help ME if ATT is blocking email clients?

They block port 25; I have no trouble using SMTP with port 465 for my old 'pacbell.net' days (SBC era).

Last year, I tried to save family member's sbcglobal.net address, which had been connected to their Uverse account, which got turned off for a week while they were ill. 10 years of email gone, because ATT "can't find" the software to access the sbcglobal.net accounts. No warning. We didn't want sbcglobal.net email attached to the Uverse account, and certainly were not informed that the email account would be deleted if Uverse was disconnected, even voluntarily. ATT paid a Uverse technician for 6 hours while we sat on the phone trying to get it back.

Was the U-verse account "turned off" for non-payment? AT&T allows customers to convert email to free Yahoo! Mail accounts as long as the bill is paid up to date when closing ISP accounts.

from att email 05.08.2013:
"There is no impact to your email IDs, saved messages, webmail folders, passwords, email client settings, or service, based on this upgrade."

Nor is there. Thunderbird, the client I use, still works just as well since they changed webmail as before. And this is with eleven 'pacbell.net' accounts two years after quitting AT&T.

I praise my intuition for setting up a private (as such) POP/SMTP email account to replace my att accounts two weeks ago, but had not begun using it yet.

It is generally recommended to not rely on ISP email.

They desperately try to control customers which only drives them away faster.

Despite that I more, or less agree, and even dumped AT&T when they implemented "Cap-and-Overage", the functionality of their email has not changed since they (SBC) partnered with Yahoo! in 2002.
ekf
join:2003-07-10
Little Rock, AR

ekf

Member

said by ekf:

In Chat, ATT rep told me ATT had blocked email client use.
from att email 05.08.2013:
"There is no impact to your email IDs, saved messages, webmail folders, passwords, email client settings, or service, based on this upgrade."

Sat Sep 07 13:30:52 2013
MAIN 524288:0.48.42 ReadRForkTOC(Out.temp): 0
MAIN 524288:0.0.1 WriteTOC(Out.temp.toc): 0
14216192 1:0.0.14 smtp.sbcglobal.yahoo.com 465
14216192 262144:0.0.30 DNS Lookup of "smtp.sbcglobal.yahoo.com"
14216192 262144:0.0.31 98.138.31.74 (1)
14216192 262144:0.0.31 98.139.221.42 (2)
14216192 262144:0.0.31 67.195.15.66 (3)
14216192 262144:0.0.32 Connecting to 98.139.221.42:465
14216192 262144:0.0.36 Connected to 98.139.221.42:465
14216192 8:0.2.25 HELO
14216192 8:0.2.25 501 5.5.4 Invalid argument
14216192 8:0.2.25 SMTP
14216192 8:0.2.25 "I said: HELO
And then the SMTP server said: 501 5.5.4 Invalid argument' "'
MAIN 524288:0.2.41 WriteTOC(Out.temp.toc): 0
MAIN 524288:0.2.42 WriteTOC(Out.toc): 0

Sat Sep 07 13:33:30 2013
MAIN 524288:2.37.48 WriteTOC(Out.toc): 0

Sat Sep 07 13:33:35 2013
MAIN 524288:0.4.56 WriteTOC(Out.toc): 0

Sat Sep 07 13:33:47 2013
MAIN 8:0.12.46 Your message has misspellings.
MAIN 8:0.0.0 You can send it anyway, or cancel and correct the misspellings.
MAIN 8:0.1.19 Dismissed with 1.
MAIN 524288:0.1.23 WriteTOC(Out.toc): 0

Sat Sep 07 13:33:52 2013
MAIN 524288:0.5.7 ReadRForkTOC(Out.temp): 0
MAIN 524288:0.0.2 WriteTOC(Out.temp.toc): 0
15318016 1:0.0.9 outbound.att.net 465
15318016 262144:0.0.18 DNS Lookup of "outbound.att.net"
15318016 262144:0.0.18 98.138.84.52 (1)
15318016 262144:0.0.19 Connecting to 98.138.84.52:465
15318016 262144:0.0.22 Connected to 98.138.84.52:465
15318016 8:0.1.30 HELO
15318016 8:0.1.30 501 5.5.4 Invalid argument
15318016 8:0.1.30 SMTP
15318016 8:0.1.30 "I said: HELO
And then the SMTP server said: 501 5.5.4 Invalid argument' "'
MAIN 524288:0.1.41 WriteTOC(Out.temp.toc): 0
MAIN 524288:0.1.41 WriteTOC(Out.toc): 0

Sat Sep 07 13:35:09 2013
MAIN 524288:1.16.30 WriteTOC(Out.toc): 0

Sat Sep 07 13:35:13 2013
MAIN 524288:0.4.24 WriteTOC(Out.toc): 0

Sat Sep 07 13:35:49 2013
MAIN 8:0.36.3 Your message has misspellings.
MAIN 8:0.0.0 You can send it anyway, or cancel and correct the misspellings.
MAIN 8:0.1.30 Dismissed with 1.
MAIN 524288:0.1.33 WriteTOC(Out.toc): 0

Sat Sep 07 13:35:54 2013
MAIN 524288:0.4.17 ReadRForkTOC(Out.temp): 0
MAIN 524288:0.0.2 WriteTOC(Out.temp.toc): 0
14554624 1:0.0.7 smtp.att.yahoo.com 465
14554624 262144:0.0.17 DNS Lookup of "smtp.att.yahoo.com"
14554624 262144:0.0.17 98.139.221.42 (1)
14554624 262144:0.0.18 98.138.31.74 (2)
14554624 262144:0.0.18 67.195.15.66 (3)
14554624 262144:0.0.19 Connecting to 98.139.221.42:465
14554624 262144:0.0.22 Connected to 98.139.221.42:465
14554624 8:0.1.43 HELO
14554624 8:0.1.43 501 5.5.4 Invalid argument
14554624 8:0.1.43 SMTP
14554624 8:0.1.43 "I said: HELO
And then the SMTP server said: 501 5.5.4 Invalid argument' "'
MAIN 524288:0.1.51 WriteTOC(Out.temp.toc): 0
MAIN 524288:0.1.51 WriteTOC(Out.toc): 0

NormanS
I gave her time to steal my mind away
MVM
join:2001-02-14
San Jose, CA
TP-Link TD-8616
Asus RT-AC66U B1
Netgear FR114P

1 edit

NormanS

MVM

Not happening here:
C:\util\dig>telnet smtp.att.yahoo.com 25
Connecting To smtp.att.yahoo.com...
220 smtp.att.yahoo.com ESMTP ready
helo reki.aosake.net
250 smtp.att.yahoo.com
quit
221 2.0.0 Bye
 
Connection to host lost.
 

And I am not connecting from an ATTIS IP address:
C:\util\dig>nslookup reki.aosake.net
Server:  ordns.he.net
Address:  2001:470:20::2
 
Non-authoritative answer:
Name:    reki.aosake.net
Address:  173.228.7.217
 

I used port 25 for simplicity; Mozilla Thunderbird is configured to use port 465:

AT&T Yahoo! in Thunderbird


PS: A Windows Live Mail transaction log:
[13:38:22.43] 1b74   Mail:      SMTP [rx] 220 smtp.mail.yahoo.com ESMTP ready
[13:38:22.49] 1b74   Mail:      SMTP [tx] EHLO Miyuki
[13:38:22.61] 1b74   Mail:      SMTP [rx] 250-smtp.mail.yahoo.com
[13:38:22.61] 1b74   Mail:      SMTP [rx] 250-PIPELINING
[13:38:22.61] 1b74   Mail:      SMTP [rx] 250-SIZE 41697280
[13:38:22.61] 1b74   Mail:      SMTP [rx] 250-8 BITMIME
[13:38:22.61] 1b74   Mail:      SMTP [rx] 250 AUTH PLAIN LOGIN XYMCOOKIE
[13:38:22.61] 1b74   Mail:  Zone_MailChk ERROR: (sicily.cpp:695), failed with 0x8000FFFF  
[13:38:22.61] 1b74   Mail:      SMTP [tx] AUTH LOGIN
[13:38:22.74] 1b74   Mail:      SMTP [rx] 334 VXNlcm5hbWU6
[13:38:22.74] 1b74   Mail:      SMTP [tx] dC5zYWthZ2FtaUBhdHQubmV0
[13:38:22.87] 1b74   Mail:      SMTP [rx] 334 UGFzc3dvcmQ6
[13:38:22.87] 1b74   Mail:      SMTP [tx] YUNZN3FsSzhXT3VLTk5EUDJQ
[13:38:23.24] 1b74   Mail:      SMTP [rx] 235 2.0.0 OK
[13:38:23.25] 1b74   Mail:      SMTP [tx] MAIL FROM: <**********@att.net>
[13:38:23.36] 1b74   Mail:      SMTP [rx] 250 OK , completed
[13:38:23.36] 1b74   Mail:      SMTP [tx] RCPT TO: <**********@netscape.net>
[13:38:23.48] 1b74   Mail:      SMTP [rx] 250 OK , completed
[13:38:23.48] 1b74   Mail:      SMTP [tx] DATA
[13:38:23.61] 1b74   Mail:      SMTP [rx] 354 Start Mail. End with CRLF.CRLF
[13:38:23.62] 1b74   Mail:      SMTP [tx] .
[13:38:24.06] 1b74   Mail:      SMTP [rx] 250 OK , completed
[13:38:24.06] 1b74   Mail:      SMTP [tx] QUIT
 

I removed a bunch of WLM "[db]" entries. I don't know what the "Zone_MailChk ERROR:" means, but it was not a show stopper.