Comcast rejects my mail because I smarthost and spam filter

[JN]

I am kind of stuck between a rock and a hard place here. We get a ton of
SPAM so filter our email by having our MX records listed servers at an
Anti-SPAM service company. They filter the mail, then send us all the good
mail. Works GREAT!

Also, Verizon and a bunch of other companies last year were rejecting our
email because it was coming from our static IPs which are not registered as
belonging to an ISP. Just a customer of one. We got around this by using
our Anti-SPAM service companies smart hosting feature and all was good.

Now those complete losers at Comcast our rejecting our emails because we are
not sending it directly to them. But if I turn off the smarthost settings,
tons of other customers and vendors will reject our emails. Is there anyway
to configure Exchange to send all email through the smart host, except for
Comcast.net?

[Lanwench [MVP - Exchange]]

Who's your ISP?

There's only so much you can do about this. You can set up multiple SMTP
connectors for various destination domains with different smarthost or "send
directly:" settings. You can set up an SPF record. You can work with your
ISP to get them to set up PTRs for you - and switch to another ISP who isn't
blacklisted. But ultimately, if your recipients' mail servers are rejecting
mail you send, all you can do is take it up with the recipient admins - and
if they won't budge, well, you can't send mail to them.

[Michael Dragone]

Just to add to Lanwench's good advice - have you contacted your antispam
service provider? I'm sure if Comcast is rejecting mail that you smarthost
through them then they're rejecting mail that *other* customers are
smarthosting through them. They may be working on this problem already.

Exchange Hosted Services had a run-in with Comcast a few weeks back (delayed
messages, etc.) which the two of them eventually resolved. If you want to
keep doing what you're doing (smarthosting mail to the antispam provider),
then you'll have to see if they can work things out with Comcast.

"Lanwench [MVP - Exchange]"
<lanw...@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:uQWpYCWD...@TK2MSFTNGP04.phx.gbl...

[John Oliver, Jr. [MVP]]

To add what has been stated so far, make sure you have a valid SPF record in
place. Comcast was doing the same thing with a customer of mine and once I
created an SPF Record for their domain, mail started flowing again to
Comcast. No issues since.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner

"Michael Dragone" <news...@mikerochip.com> wrote in message
news:ulCb1KXD...@TK2MSFTNGP04.phx.gbl...