
how-to block ads
|
|
Uniqs: 4516 |
Share Topic  |
 |
|
|
|
 CHIEFSFANThe Muffin Man join:2000-11-01 Saint Ann, MO | Email sent to SBCglobal addresses Didn't know if i should post this here or somewhere else, but when our company, which uses ATT DSL sends email through our exchange server to sbcglobal addresses, the recipient sometimes doesnt get the email. Looking at System manager, it says "message transferred to flpi113.prodigy.net, so im assuming its not a problem on our end. Any one else had this problem, or know of a way to fix it? | |  NormanSPremium,MVM join:2001-02-14 San Jose, CA kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| Email sent to 'flpi113.prodigy.net' should be delivered to the user's mailbox. In the case of an 'at&t Yahoo! HSI' user, this will be a Yahoo! Mail Delivery Agent. If the user has SpamGuard enabled, the email could be delivered to the "Bulk" folder. If the user has SpamGuard configured to immediately delete the contents of the "Bulk" folder, he will never see the email. The only fix for this is in the hands of the user. -- Norman ~Oh Lord, why have you come ~To Konnyu, with the Lion and the Drum | | |
|  EGeezerSummertimePremium join:2002-08-04 Midwest kudos:7 Reviews:
·Callcentric
1 edit | reply to CHIEFSFAN Are you using ATT's email service? In our area, ATT has changed their authentication for SMTP and POP. One of my customers has a SBS exchange server (SBS2003) and I simply couldn't get the server configured to work with the settings they require. If you have exchange settings that do, please let me know. At the present time I have all my client PCs using Outlook with a separately configured account for ATT email.
If your recipient hasn't changed their settings, they may not be able to receive some emails. ATT has been futzing with this "improvement" for some time.
See »www.guardlitho.com/mailservers.html or the ATT help site.
Mail Server (POP, SMTP) Settings Email Address, Incoming (POP), Outgoing(SMTP) MemberID@sbcglobal.net, pop.att.yahoo.com, smtp.att.yahoo.com
Outgoing mail server: Outgoing server (SMTP) requires authentication Incoming mail port #: 995, secure connection (SSL) checked Outgoing mail port #: 465, secure connection (SSL) checked
-- If dogs travel in space at the speed of light, do they reach their destination in dog-light years? | |  NormanSPremium,MVM join:2001-02-14 San Jose, CA kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| said by EGeezer:Are you using ATT's email service? In our area, ATT has changed their authentication for SMTP and POP. One of my customers has a SBS exchange server (SBS2003) and I simply couldn't get the server configured to work with the settings they require. If you have exchange settings that do, please let me know. At the present time I have all my client PCs using Outlook with a separately configured account for ATT email. Those servers you list are not run by AT&T, they are run by Yahoo!. They wouldn't work as a 'smarthost', anyway, which is probably what your client needs, if he is running an SBC Exchange server. Those Yahoo! servers will throw "553 From: address not verified" if the sender email address is not associated with the login email address; and only ten, max, email addresses can be verified per account.
If your client needs a proper 'smarthost', I would suggest using, 'smtp.ameritech.net'. It is one of several aliases to the AT&T Internet Services operated SMTP AUTH mail server. Access is available through port 25, or, if necessary to get around a port 25 block, you can also use port 587. No secure protocol is required. Log in requires the full email address, and the password. -- Norman ~Oh Lord, why have you come ~To Konnyu, with the Lion and the Drum | |  EGeezerSummertimePremium join:2002-08-04 Midwest kudos:7 Reviews:
·Callcentric
| Thanks for the update!
The problem we had was that we have a DSL service from Ameritech with ten user accounts with emails of "user@ameritech.net". Over the years they became SBC. SBC/Yahoo then ATT - at least on the billing. When we log in using the master account we are redirected to »att.my.yahoo.com/ and all account information (sub accounts, billing etc) is there.
When we use SMTP.ameritech.net, We get nag messages from ATT telling us they are going to cut off port 25 SMTP and require POP authorization. They referred us to the POP and SMTP settings I posted.
When I called tech support they confirmed the change over but could not give us a date when the cut-over would be permanent and 110/25 would go away.
The customer is a law office and can't afford to have email service disrupted by a sudden termination, so my question is;
If we switch back to using the Ameritech SMTP/POP servers, will we again start receiving nag emails or be cut off at some unspecified point?
I'd really love to be able to again use the POP connector in SBS 2003 Exchange. -- If dogs travel in space at the speed of light, do they reach their destination in dog-light years? | |  wayjacPremium,MVM join:2001-12-22 Indy kudos:1 | Take a look at this: SBS 2003 Exchange SmartHost with Authentication | |  NormanSPremium,MVM join:2001-02-14 San Jose, CA kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| reply to EGeezer said by EGeezer:When we use SMTP.ameritech.net, We get nag messages from ATT telling us they are going to cut off port 25 SMTP and require POP authorization. They referred us to the POP and SMTP settings I posted. I don't know why you get nag notices. I use the 'mail.pacbell.net' alias to the same server, and I get no notices. I know of one other user reporting nag notices when using the 'smtpauth.flash.net' alias. I never got those notices when using the 'smtpauth.sbcglobal.net' alias, either. All point to the same IP address.
The only nag notice I have ever seen posted indicated that it came from Yahoo!. But the ATTIS SMTP AUTH servers are not run by Yahoo!.
I don't know if the old, legacy accounts which were never migrated are going to be forced to migrate. I detest Yahoo!, now, and wish that AT&T would sever the ties; I've heard a rumor that might even happen.
Does your client use their 'ameritech.net' email domain? It might be time to look at regular email hosting, and using their own domain.
Yahoo! sucks, and I want AT&T to pitch them. -- Norman ~Oh Lord, why have you come ~To Konnyu, with the Lion and the Drum | |  NormanSPremium,MVM join:2001-02-14 San Jose, CA kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| reply to wayjac Regarding the problem described in that link: AFAIK, AT&T will assign a custom rDNS name to at least one of the IP addresses in the static package. The user should pick a name that will stay the same, such as, 'mx1.example.com', and request that be assigned to the IP address used for the outbound SMTP relay. That should fix the problem described in your link. -- Norman ~Oh Lord, why have you come ~To Konnyu, with the Lion and the Drum | |  EGeezerSummertimePremium join:2002-08-04 Midwest kudos:7 Reviews:
·Callcentric
| reply to NormanS Thanks Norman and all - Coincidentally the customer just forwarded me this email dated 29 MAY, another nag. I'm guessing a recent Windows Update has reset the user's Outlook settings since the user was one I set up with the new config months ago. Here's the email -
From: Yahoo! [mailto:mailbot@yahoo.com]
Sent: Wednesday, May 28, 2008 3:03 PM
To: customer name
Subject: Message From Yahoo!
<https://a248.e.akamai.net/sec.yimg.com/a/ym/ymc/yplus/spacer.gif>
<https://a248.e.akamai.net/sec.yimg.com/a/ym/ymc/yplus/spacer.gif>
AT&T Yahoo! <http://us.i1.yimg.com/us.yimg.com/i/us/plus/b6/att/atty.gif>
<https://a248.e.akamai.net/sec.yimg.com/a/ym/ymc/yplus/spacer.gif>
Dear AT&T Yahoo! Customer:
We noticed that you are accessing email using non-secure settings in your
email software.
We would like to ensure that your AT&T Yahoo! Member ID, password, and email
messages are transmitted securely between your mail software (such as
Outlook or Outlook Express) and the AT&T Yahoo! Mail servers. In order to
meet this need, please enable SSL <http://helpme.att.net/glossary.php#147>
via the instructions that are available on the Help
<http://helpme.att.net/article.php?item=10918> site.
Since multiple email notifications have already been sent out about this, we
request that you please make the necessary changes immediately. Remember,
you need to make these changes if you want to continue to send/receive email
using a mail client.
Thank you for your cooperation,
AT&T Yahoo! Customer Support
<https://a248.e.akamai.net/sec.yimg.com/a/ym/ymc/yplus/spacer.gif>
<https://a248.e.akamai.net/sec.yimg.com/a/ym/ymc/yplus/spacer.gif>
Please do not reply to this message. This is a service email related to your
use of AT&T Yahoo!. To learn more about Yahoo!'s or AT&T's use of personal
information, including the use of web beacons
<http://privacy.yahoo.com/privacy/us/beacons/details.html> in HTML-based
email, please read our Privacy <http://att.yahoo.com/privacy> Policy.
Yahoo! is located at 701 First Avenue, Sunnyvale, CA 94089. AT&T Internet
Services is located at PO Box 2203 San Ramon, CA 94583.
I agree ATT Yahoo sucks for business. I'm not too hot about allowing SMTP relay on the SBS, so will probably stick with the separate account in Outlook. When/if the customer switches ISPs we may have a different setup.
My recent experiences with Road Runner hasn't been too hot either - see my review update linked in my profile.
-- If dogs travel in space at the speed of light, do they reach their destination in dog-light years? | |
|