ChangeIP.com Forums

I'm using windows 2000 adv server and exchange 2000 and I'm unable to send messages to users@sbcglobal.net. It returns with this error message:




Is there a way around this, because sbc claims they aren't block any email domain?

Is this happening when relaying thru our servers, or from your own server directly? SBC is very picky on who they accept mail from - you must relay thru a trusted server basically. If you use the relay on our system you can get the mails there reliably.

Sam

You didn't post the SMTP error code, which I'm guessing was 550, with a custom response. If you have an SMTP server (MTA) on a dynamic IP address, and even if you have a proper MX record with your DDNS provider, they will still reject you on the basis of the dynamic IP address. They have a static table compiled of all the ISP's dynamic IP blocks, and they refuse relay and (for some domains) deny final delivery based on the dynamic IP status of the sending MTA.

I'm currently troubleshooting with SBC support because I cannot do SMTP relay through their relay servers, PERIOD. I have PPPoE dynamic service with them now, and have registered my MX record in my dynamic dns. They don't offer standard SMTP relays to any of their customers now. They've changed from true static IPs to \"sticky static\" IPs (PPPoE with a never changing address) for all new static IP customers. For current static customers, they maintain \"legacy\" (i.e. normal TCP port 25 SMTP) relay servers, but they won't add any new customers to them, and they won't let me use one, since I downgraded from static to dynamic IP service to save over $50/month. I'd been an SBC DSL static IP customer for 5 years, and I was true static, not the \"sticky static\".

After getting PPPoE setup on my SMC 7008ABR, getting DDNS configured properly, and the MX, PTR, and SPF records setup for my domain, I was able to receive all mail destined for my domain without a problem. Attempting to send, I hit the now infamous port 25 filter. I called SBC, got it removed, and then happily was able to send outbound SMTP mail directly from my Exchange server to final destination SMTP hosts, just like I always had when I was static. Then, after about 15 successful outbound deliveries (all to non \"big isp\" domains), I got this back from Earthlink while trying to send a message to my dad:

Mail could not be delivered to 209.86.93.233 (for earthlink.net). The destination server reported 550 Dynamic IPs/open relays blocked. Contact <openrelay@abuse.earthlink.net>..

I've never been an open relay, and just last night checked 19 RBL orgs and all 19 showed a negative listing of my domain. So, Earthlink is denying me due to the dynamic IP address alone.

When sending a test message to an SBC level 2 support tech in Dallas, I got this from his local \"SBC corporate\" server, i.e. different SBC subnet from the consumer side:

>Mail could not be delivered to 144.160.112.9 (for sbc.com). The destination server reported 550 5.0.0 SBCIS Dynamic IP - Access denied.

This is so stupid I laughed. They're denying delivery of an email from their own customer, based on the dynamic IP \"status\" of his MTA host, even though that dynamic IP is part of THEIR network.

As I see it, I basically have a few options at this point:

1. Configure a Linux mail hub in front of my Exch server with an MTA that can do the auth required by the SBC/Yahoo relay servers (if possible at all) so I can relay through them just like a POP client does, and thus not get blocked on the receiving end by the likes of Earthlink, AOL, et al.

2. Hold my breath until I finally convince SBC to let me relay off one of the \"legacy\" relay servers, since Exch can't provide the auth they require on the \"new\" SMTP relay servers.

3. Forward all my outboud mail to a SMTP server with a static IP. I have a couple of local friends that might do this for me either on their home servers, or work servers.

I'd really like to use the SBC/Yahoo servers for relaying, since they provide my service, and they're trusted by all the other \"big ISPs\". I've done extensive Googling for a *nix open source MTA/MUA (and script setup) that can auth with SBC/Yahoo relay servers in the way POP/IMAP clients do, and thus then relay all my outbound mail through them. I haven't been able to find such a beast, and am gladly open to suggestions. I've got a Debian box with Exim that I intend to use as a smart host/hub in front of the Exch server, but I haven't been able to get Exim to perform this \"auth with PPPoE NAME and PASS\" before attempting the standard ESMTP commands to start the message transfer.

I'm not much of a scripter, and I don't know if I can pull off mod'ing Exim, Postfix, Qmail, or Sendmail to do this. Any takers? Many people attempting the same thing I am would love to see a solution like this available. If there isn't a solution out there to do this, then I'll bite the bullet and build it myself, although it might take quite some time to get it working.

We offer SMTP relaying to get around all these problems. We run our servers off large tier-1 data centers and are not blacklisted by anyone. You can relay mail to us from Exchange or any other MTA/MUA that you wish. We allow SMTP AUTH and POP before SMTP authentication. Simply add some storage to your account, create a pop3 mailbox (can be a dummy mailbox used just for auth only) and your good to go. The quota limits are based on the amount of storage that you purchase, ie 10mb mailbox can send 10mb per day, or 1000 emails per day. 25mb mailbox can send 25mb per day, or 2500 mails per day.

SBC is just messed up and doesn't know how to do it right : )

Thx,
Sam

How can a multi-billion dollar company not get it right

They are so quick to get your money and so slow to fix a problem, their job is to make $$$$ not provide you quality service.

Are there any alternatives to SBC Yahoo DSL ? All SBC customers should sign a petition demanding SBC charge less if they are only offering poor service