RE: More sorbs blacklisting
What I think is needed at least for the short term is a reverse MX system.
So if I send an email from stev.org there is a RMX record saying that server
xyz is meant to be able to relay. This will at least stop spammers sending
as something like firstname.lastname@example.org yahoo.com though random relays. This
would also mean email is slightly harder to spoof and the from line will
actually mean something useful to be able to filter off. Then servers /
domain that are actually being used as spamming where they keep changing
there RMX record to use different relay can actually also be blocked. Using
some sort of DNS BL.
> -----Original Message-----
> From: John Kelly [mailto:email@example.com]
> Sent: 26 June 2006 17:09
> To: firstname.lastname@example.org
> Subject: Re: More sorbs blacklisting
> On Mon, 26 Jun 2006 10:13:19 -0600, Michael Loftis
> <email@example.com> wrote:
> >>> On 20.06. 02:15, John Kelly wrote:
> >>>> I'll gladly sacrifice 20% of "legit" mail to stop 99.5% of all SPAM.
> >It's nowhere near 99.5%. Especially when you consider all of the
> >I do based on *.adsl.* or *.dsl.* or (dynamicsomething).comcast.net etc.
> >catches a LOT of ratware running from machines with valid rDNS.
> I do the same. Reverse DNS does not catch all spam; however, reverse
> DNS is the key piece of the spam puzzle.
> >> 100% of mail originating from servers having proper DNS will succeed.
> >Yup this is correct. It's not like 20% of your outgoing mail will not
> >there, it either will or it won't.
> Yep, just fixup your DNS, and I will accept 100% of your mail. Unless
> of course, you are a spammer. I wonder why they whine, heh.