Re: E-Mail From Static IP Getting Caught By Some Spam Filters in TekSavvy http://www.dslreports.com/forum/r21075536 en Wed, 11 Nov 2009 07:05:35 EDT Wed, 11 Nov 2009 07:05:35 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21076378 shepd : If the admin makes it hard work for you to help them fix their broken computers (which is basically what blacklisting IPs that shouldn't be blacklisted is), give up.

Tell the admin that you'll be telling their ISPs customers to contact him if they want email from your domain. Then just go ahead and do that.

Note: This won't work for places like yahoo, etc. In those cases, if the admins won't fix things, for a mailing list I'd just put a note up explaining you won't be fixing their broken servers since you tried and it didn't work. The more places that simply stop bothering to fix other admins broken email servers, the fewer broken email servers there will be (due to incentive to keep their customers).]]> http://www.dslreports.com/forum/remark,21076378 Mon, 08 Sep 2008 13:23:10 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21076359 sbrook : depends on the blacklist ... some you can only get off with an extreme amount of time and others you can't get off at all.]]> http://www.dslreports.com/forum/remark,21076359 Mon, 08 Sep 2008 13:21:10 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21076211 bjlockie :
said by JayMan See Profile :

Blacklists don't care what kind of IP it is. If they get reports they blacklist it, even if it's a business IP. Teksavvy's own mail servers have been blacklisted before.
I wasn't talking about blacklists, I was referring to blocks of residential IPs.

Re: blacklists are alot easier for an ISP to get off.]]> http://www.dslreports.com/forum/remark,21076211 Mon, 08 Sep 2008 12:56:23 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21076004 sbrook : There are three ways to end up on blocklists ...

1) Your IP is reported as a source of spam (various ways that may happen ... somebody maliciously reports you ... somebody has previously had the IP currently assigned to you and was reported as a spammer ... or you have spammed ... or you've accidentally been included such as the mail list described)

2) Your IP is in a block of IPs known to be a source of spam (some blocklists take the approach that if one or more IPs in a block are a source of spam and requests to the netblock owner to clean up the spam go unresolved, then they'll widen the net to the entire netblock)

3) Your static IP is in a block of IPs which has been marked as dynamically assigned. For example, say an ISP has the netblock 192.168.192.1 through ..255.255 and they reserved 255.1 through 255.255 themselves for static IPs, but didn't report that to IANA (the number authority). Users of the static IPs may face the problem that it appears that their IPs are dynamically assigned. (A sure potential source of spam and viruses)

4) Your static IP has no reverse DNS entry so it cannot be confirmed as the name of the mail server. Lots of recipient SMTP servers will reject mail if it cannot confirm the originating connection IP with the name of the server it's declared to be from.

The bottom line is that the cost to you to deal with this problem is probably far more than the cost of having a reliable SMTP mail submission server on a host somewhere. Many webhosting plans can service your needs for only a few dollars a month.

The alternative that many small companies do is to have a backup email service from some of the freemail servers "just in case" if there are only a few mails that bounce this way.]]> http://www.dslreports.com/forum/remark,21076004 Mon, 08 Sep 2008 12:16:39 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21075894 JayMan : Blacklists don't care what kind of IP it is. If they get reports they blacklist it, even if it's a business IP. Teksavvy's own mail servers have been blacklisted before.]]> http://www.dslreports.com/forum/remark,21075894 Mon, 08 Sep 2008 11:55:11 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21075536 bjlockie : Nobody has mentioned it but I doubt a business plan with static IP would be on a blocked net block.

If you require to run a business on a residential service then you could relay all mail through the TekSavvy mail server. smart_host for Postfix.]]> http://www.dslreports.com/forum/remark,21075536 Mon, 08 Sep 2008 10:43:27 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21074622 JayMan : yahoo.com is a bitch. It took me 2 months but I have finally got my server whitelisted on yahoo. Some asshole who is subscribed to some of my lists rather then unsubscribe just started tagging all the emails as spam. It was a bitch to get that fixed.

SPF, DKIM, Domainekeys, forward and reverse DNS. With all the spam on the internet these days unless you got all of those running you might as well not even run a email server.]]> http://www.dslreports.com/forum/remark,21074622 Mon, 08 Sep 2008 04:53:54 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21074474 jfmezei : >Into something like this:
>
>iamthisguy.dsl.teksavvy.com

No. If you are sending mail primarily from user@chocolate.com, then you want the reverse translation for your ip to be something.chocolate.com

You need to send an email to dnsadmin at tech savvy period com to request that the reverse translation for your fixed IP be set to whatever you specify.

The reverse translation should be associated with you, not your ISP, and should not look like a dynamically allocated IP at all (aka: contain the words DSL, dialup, cable, and some numbers that make up an IP address)]]> http://www.dslreports.com/forum/remark,21074474 Mon, 08 Sep 2008 02:24:35 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21074303 PXA : Well, I did a check and all the blacklists came back OK which is a good thing. I also did use the SPF generator tool you linked to a while back to create the SPF records for my domains. I think you're on to something with the reverse translation and that's very likely what is tripping up the Rogers server. So just to be clear, what you are suggesting is that I change my reverse translation from something like this:

xx-xx-xxx-xxx.dsl.teksavvy.com

Into something like this:

iamthisguy.dsl.teksavvy.com
--
Parallax Abstraction,
Ottawa, Ontario, Canada
blog.digital-lifeline.ca]]> http://www.dslreports.com/forum/remark,21074303 Mon, 08 Sep 2008 00:56:21 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21073856 Vinch : As mentionned earlier, make sure you have a good reverse lookup that matches what your server sends out during HELO or EHLO which should also resolve to your static IP. ]]> http://www.dslreports.com/forum/remark,21073856 Sun, 07 Sep 2008 22:56:59 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21073805 jfmezei : To get your own mail server to work reliably:

-make sure you have reverse transalation on the IP that isn't "generic" such as those used by default by ISPs. Teksavvy has no problem giving you a proper reverse transation of your choice. (a big advantage for Teksavvy vs other ISPs).

-I know that SPF records are now pretty much required to send to Hotmail, so perhaps they are needed for Yahoo as well. (Bell outsources email to Hotmail, Rogers to Yahoo).

-You need to ensure that your IP is not on any RBLs. This is tough to check.

»www.mxtoolbox.com/blacklists.aspx is one of many services that check your IP against many RBLs. If you are a positive on one of the RBLs, then you can go to that RBL and deal with them to get yoru IP off. (or find out why yo were put on).

There are also various tests you can trigger to check that your server doesn't alllow open relays.

In terms of SPF, you can goto »www.openspf.org/ or do a dig of various domains to see how they set theirs up. You can "link" to the teksavvy one to include the teksavvy SMTP servers in case you need to send email via their servers.]]> http://www.dslreports.com/forum/remark,21073805 Sun, 07 Sep 2008 22:45:27 EDT Re: E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21073541 Guspaz : It's unfortunate that you're not having trouble public blocklists; they're easier to deal with.

Your best bet is to get in touch with Rogers yourself. I find that telephone works best for such things.

You should look for useful phone numbers in their business pages. Alternatively, there are various direct phone numbers listed in their domain's WHOIS information; specifically, there are phone numbers for a "Nick Allum" as their technical contact, and "Deborah Charlie" as their administrative contact.]]> http://www.dslreports.com/forum/remark,21073541 Sun, 07 Sep 2008 21:56:14 EDT E-Mail From Static IP Getting Caught By Some Spam Filters http://www.dslreports.com/forum/remark,21073253 PXA : Truthfully, I'm not sure if there's a solution to this while I continue to host my own e-mail but I thought I'd ask. I have two domains (my personal one and the one for my new company) and host my own e-mail on a server in my office. I do this through TSI DSL with a static IP. The problem I am having is that certain ISPs (primarily Rogers) think everything that comes from my server is spam and automatically filter it. This happened when I used to be on Primus as well.

Rogers has no way of requesting that your domain be put on a whitelist. I know my server is secure and that it is absolutely not being used to relay spam. My theory is that Rogers is able to tell that the IP block I am on is used for residential customers and therefore just assumes all e-mail originating from such IPs is spam. I do have SPF set up in my domains but I don't think Rogers processes this.

Does anyone know if there's a way I can ensure that this doesn't happen? My company communicates with a lot of people on the Rogers servers and this is frustrating. We also don't want to have to pay for separate e-mail service when this could work just as well. Thanks all!
--
Parallax Abstraction,
Ottawa, Ontario, Canada
blog.digital-lifeline.ca]]> http://www.dslreports.com/forum/remark,21073253 Sun, 07 Sep 2008 21:08:34 EDT