Giampaolo Tomassoni wrote:
So, if people could take a look at it, test it, see if it does what it
advertises, and see if it's as accurate as my experience indicates, I
would appreciate getting feedback. If it pans out, I'll see about
putting it in a tar ball, and submitting it to the wiki's list of plugins.
if ( ($hostname =~ /(\S?0*($a|$b|$c|$d|$e|$f|$g|$h|$i)){2,4}/) ||
($hostname =~ /$e/) ) {
# hostname contains two or more octets of its own IP addr
# in hex or decimal form ... or the entire thing in decimal
# probably a spambot since this is an untrusted relay
Mail::SpamAssassin::Plugin::dbg("RelayChecker: ipinhostname");
$ipinhostname = 1;
}
Wow, how rude this is! Almost all customers of my ISP (Telecom Italia) would be
banned from the e-mail world...
Telecom Italia is used to put RDNSes with something like this:
host1-84-static.48-88-b.business.telecomitalia.it.
They would not be banned from the e-mail world.
Instead, they would:
a) be heavily encouraged to get a custom RDNS record, OR
b) be heavily encouraged to send outgoing email through their ISP*, OR
c) be heavily encouraged to use a hosted email service that has a custom
RDNS record instead of a client-looking RDNS record, OR
d) accept that their email is going to be quarantined (not banned).
(* which they should do -- I'm not their email server, so unless they
can make themselves look like a server, instead of a client, they have
no business connecting directly to my email server; they should connect
to their own email server, which should have a custom RDNS record, and
then have that machine connect to my email server)
If they can't do (a) because their ISP doesn't offer that, then they'd
be encouraged to switch to an ISP that does offer custom RNDS records
... or do (b) or (c).
I'm personally comfortable with insisting that the people who want to
connect to my email servers conform to those options. It's certainly a
nicer set of options than having (d) be: accept that their email wont be
accepted at all (which is what I've done in the past).
