Bull
@pacbell.net
moderated:
April 25th, @05:08PM
| Pacbell legacy server and email
Hi Guys, I can receive email but can't send. I am not as technical as you all and i've tried to correct the problem myself to no avail. Depending on what site i am on i get difference server suggestions and port # suggestions...very confusing. (Legacy Pacbell user).
Prior to the problems a few weeks ago, my email settings where
Windows XP, Outlook 2002, Linksys router/firewall, Avast.
pop server: postoffice.pacbell.net
smtp: mail.pacbell.net
NOT logging in using Secure Password (SPA)
Outgoing Server (SMTP) was not checked
Incoming server (pop3)port 110, ssl not checked
outgoing server (smtp) port 25, ssl not checked
I tried changing the pop3 and smtp servers settings, the ports to 995 and 465 and selecting the ssl settings as suggested, but then i run into more problems and the server doesn't recognize me as a user.
Would appreciate any guidance you can offer. Thank you!!
[Mod Note: Post split to make a new thread. skj] |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| Re: Outbound email problems - any other reports?
said by Bull :
Hi Guys, I can receive email but can't send. I am not as technical as you all and i've tried to correct the problem myself to no avail. Depending on what site i am on i get difference server suggestions and port # suggestions...very confusing. (Legacy Pacbell user).
Different side of the service; you can't even use 'smtp.att.yahoo.com'. This certainly warranted its own thread. Most people use the Yahoo! servers, and don't know the legacy servers at all.
Prior to the problems a few weeks ago, my email settings where
Windows XP, Outlook 2002, Linksys router/firewall, Avast.
pop server: postoffice.pacbell.net
smtp: mail.pacbell.net
NOT logging in using Secure Password (SPA)
Outgoing Server (SMTP) was not checked
Incoming server (pop3)port 110, ssl not checked
outgoing server (smtp) port 25, ssl not checked
I tried changing the pop3 and smtp servers settings, the ports to 995 and 465 and selecting the ssl settings as suggested, but then i run into more problems and the server doesn't recognize me as a user.
Am told that the DNS records for 'mail.pabell.net' were changed. They now point to SMTP AUTH servers. You will need to make some basic changes in your client. I am not familiar with the layout for Outlook 2002. Somewhere, on the "Servers" tab, you should find a check box labeled, "My server requires authentication". Check it. Note that this is NOT the same as the SPA login box; don't use SPA!
You may also need to modify your login name. If you are using just the username (i.e., "%User_ID%"), you will have to add your email domain to that (i.e., "%User_ID%@pacbell.net).
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Bull
@pacbell.net
| Thank you for your help Norman. I am at work and will make the changes when i get home. If i understand you correctly, i need to put the % sign before and after my user id?
"%User_ID%@pacbell.net. This is something I have not tried.
So I can keep my port settings at 110 and 25 and I don't have to do anything with the router?
I contacted ATT help online today and waited 30 minutes, started going through the troubleshooting and then the connection was disconnected...nice support!
thanks again!!! |
|
nwrickert
sand groper
Premium,MVM
join:2004-09-04
Geneva, IL
·AT&T Midwest
| Hmm, no, DO NOT put a percent sign in there. NormanS  was just using the notation for windows environment variables (though your pacbell userid might not be the same as your windows userid). |
|
Bull
@pacbell.net | Doh  , okay thanks. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to Bull
said by Bull :
If i understand you correctly, i need to put the % sign before and after my user id?
Although nwrickert is correct about how the '%' is normally used, I also do it to foil spam harvesting bots. I am pretty sure that most mail hosts don't like to see a '%' in a user name. The alternative is more difficult for some people to parse, using RFC 2606 Reserved Top-Level Domains, such as, 'example.org'.
Just your user name and the email domain; full email address. It has been thus for at least four years.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
odayd
join:2002-12-08
Los Banos, CA | which smtp auth server needs to be used? I have been working on this for a while..
The other thread appears to be more related to sbcglobal or yahoo accounts..
Thanks |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
edit:
April 26th, @08:24PM
| Prior to mid-2002, SBC DSL customers only used SBCIS operated servers; such as 'mail.pacbell.net' for the 'pacbell.net' domain, and 'mail.nvbell.net' for the 'nvbell.net' domain.
AT&T Internet Services (ATTIS), which used to be SBC Internet Services (SBCIS), still operates those legacy servers for access by customers who never migrated to SBC Yahoo! DSL Service (now called, at&t Yahoo! HSI).
All migrated customers, and all new customers since SBC signed the contract with Yahoo! are supposed to be using the new 'smtp.att.yahoo.com' SMTP message submission severs. Alas, the new Yahoo! policy restricting sender email address to the associated account ID, and ten additional "verified" email addresses, limits the usefulness of 'smtp.att.yahoo.com' as a "Smarthost" for those running their own mail servers.
For those AT&T legacy DSL customers who never migrated to at&t Yahoo! HSI (or its predecessor, SBC Yahoo! DSL Service), 'smtp.att.yahoo.com' (and its predecessors) are not available for use. Only the legacy servers, such as 'smtpauth.sbcglobal.ne', or any other in one of the nine legacy SBC domains.
The Yahoo! change in policy on their SMTP message submission server access is a huge negative, and I urge anybody who has not, yet, migrated to the co-branded Yahoo! service to not do so at this time.
Since 'mail.pacbell.net' is now an alias to 'smtpauth.sbcglobal.net', there is not much advantage to one over the other. There are now five aliases, that I am aware of, pointing to the same legacy server cluster:
• 'mail.pacbell.net'
• 'smtp.ameritech.net'
• 'smtpauth.flash.net'
• 'smtpauth.prodigy.net'
• 'smtpauth.sbcglobal.net'
If your DSL setup documentation calls for 'mail.pacbell.net', continue to use it, for consistency's sake. Just be sure to configure your client to log in with your full email address as the username, and your account password.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Frohike
join:2000-07-23
Waxahachie, TX | Just change your outgoing to smtpauth.sbcglobal.net and be sure to check "my outgoing server requires authentication" and be sure to include your full email address as the outgoing server. |
|
tbone
@pacbell.net | Frohike, your the man...this fixed it!! Thank you for your post!! |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| I'd be suspicious that the client setting for "My outgoing server requires authentication" is what fixed it. The server names are aliases:
And...
Although, maybe, your DNS cache still had the old IP address for 'mail.pacbell.net', and a 'ipconfig -flushdns' at a command prompt would have fixed things.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Bull
@pacbell.net | Thanks for clearing this up. i'll go home tonight and give the new domain name a try.
Thanks!! |
|
Bull
@pacbell.net
| Hello, i'm home now and i am getting the same error code  .
"send test e-mail: unable to send test message, please verify the email address". I also tried to flush dns and i get the following error "could not flush the dns resolver Cashe: function failed during execution"
i have my outbound set to smtpauth.sbcglobal.net
I've tried checking my outgoing server requires authentication and use same settings as my incoming mail server...and i've tried it without authentication.
Am i using the correct server domain? What domain should i use for the inbound? It is currently working with postoffice.pacbell.net.
thanks!!! |
|
Bull
@pacbell.net
| Hello all, I did a google search and figured out how to access the dns settings
1) Click Start
2) Click RUN
3) Type services.msc in the text box
4) Click OK or hit Enter
5) Scroll down to DNS Client and double click it
6) Select General tab and select Startup type: Automatic
7) Click Apply
7) Finally at Service Status Click Start (if it is stopped)
...Then i was able to flush the dns. Then i changed the outbound server as you suggested and also (checked) my outgoing server requires authentication. clicked Log-on using my user name and password.
Thanks a bunch for helping an average computer guy....my wife will be very happy  . Thanks! |
|
sciencewhiz
@pacbell.net | reply to Bull
Re: Pacbell legacy server and email
Since yesterday, I have not been able to connect to either mail.pacbell.net or smtpauth.sbcglobal.net
Anyone else have this problem? |
|
nwrickert
sand groper
Premium,MVM
join:2004-09-04
Geneva, IL
edit:
May 11th, @10:08AM
| No problem here this morning.
edit: that's with smtpauth.sbcglobal.net that there is no problem. I didn't try any others. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to sciencewhiz
said by sciencewhiz :
Since yesterday, I have not been able to connect to either mail.pacbell.net or smtpauth.sbcglobal.net
Anyone else have this problem?
Just now I was able to Telnet to 'mail.pacbell.net' on port 25. Check your firewall?
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
skj
Welcome to the far side of reality
Premium,Mod
join:2002-04-04
Atlanta, GA |  reply to Bull
(topic move) Pacbell legacy server and email
Moderator Action
The post that was here (and all 1 followups to it), has been moved to a new topic .. »Not receiving email |
|
