My script doesn't blacklist a site for having *no* website. It only
creates the blacklist entry if it finds a website that matches a very
specific list of templates I've seen sending high volumes of spam.
Unfortunately, the "default" pages for most distributions are on that
list. Simply erasing the default page, or making it blank, or
redirecting it somewhere else is enough to fix it.
Also note that my script doesn't look at email addresses, only at rDNS
names ("from" addresses are so trivial to forge that they're not worth
even parsing out). So, for example, if you setup
[email protected] on a shared server with a default page, my
script will probably never check your website because your mail will
actually come from server113.westcoast.bigdatacenter.com. My script
will find that server name in the headers and look for a site there.
The intent is to block entire servers that are sending spam, not just
individual domains. My thinking is: if someone is running a mail server
that hosts a website, they either don't care about the server (e.g. a
spammer who intends to dump the server in a week) or they don't know
what they're doing (e.g. never turned off the Apache daemon, even though
they don't need it) or they just aren't paying attention (e.g. an
absentee sysadmin who's also not applying updates). In any case, I
probably don't want email from that server.
In Niamh's case, the email address is [email protected] but the mail
server is mail.redbus.holtain.net. If you browse http://holtain.net,
you'll see the Fedora Core Test Page. That's what triggered the
blacklist entry; it wasn't anything to do with fullbore.co.uk.
I know this system leads to false positives, but since this server only
hosts a couple of domains and very few mailboxes, the benefits outweigh
the risks. I would never run this script on one of my customer's servers.
-- Sam Clippinger
On 5/11/11 12:04 PM, Greg Cirino wrote:
> We have quite a few clients that are "domain email only". I also have a
> couple of private domain email addresses without an associated website.
>
> They have no need for a website, but they want to use domain email for
> clients (instead of the free services)
>
> I believe this is more common than one might think.
>
> Best Regards
> Greg Cirino
> 603-425-2221
> Cirelle Enterprises, Inc
> Hosting, Development, Email, MLS
> www.cirelle.com
> www.mlsbot.com
>
>
> | Hello Christoph,
> |
> | Wednesday, May 11, 2011, 4:07:28 PM, you wrote:
> |
> | CK> I can envisage this being a fairly common scenario when people want
> | personal
> | CK> email but no website so the website would be the default.
> |
> | Or even set up a masiil server before a website. It seems a guaranteed
> | way to get a lot of false positives.
> |
> | Further the message is totally misleading-
> |
> | "Refused. Your domain name is blacklisted.
> |
> | You (or someone else) have sent us so much spam that we've added your
> | domain name to our blacklist. Sorry about that, but we've had enough and
> | we don't know what else to do. "
> |
> | When in fact the blacklist has been applied for not having a website,
> | even when no spam has been received at all.
> | --
> | Best regards,
> | Niamh mailto:[email protected]
> | _______________________________________________
> | spamdyke-users mailing list
> | [email protected]
> | http://www.spamdyke.org/mailman/listinfo/spamdyke-users
> |
>
>
> _______________________________________________
> spamdyke-users mailing list
> [email protected]
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>
_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
