Milter-greylist

I have no idea why its broken, but I can no longer send email to the
list from my work address. This I had to webform. Anyway, here is a
post of what I had sent three times now regarding the botnet plugin.


Re: [milter-greylist] BotNet plugin
From: eclark <eclark@...>
To: milter-greylist@yahoogroups.com
Date: Yesterday 11:46:14 am


This is a fantastic idea. One small problem. What if you use a third
party for 
your mail exchange, and a first party for your mail transmission? Kind of 
like this:

$TTL 86400
$ORIGIN org.
a   IN   SOA  ns5.a.b. hostmaster.a.com. (
                200329316 86000 7200 3600000 600 )
                IN      NS      ns5.a.b.
                IN   NS  ns6.a.b.

                IN      A       1.2.3.4
                IN      MX      10 a.b.inbound10.mxlogic.net.
                IN      MX      20 a.b.inbound20.mxlogic.net.
                IN      MX      30 a.b.inbound30.mxlogic.net.

In this case, mxlogic is the mailexchanger for the domain. However, mail 
originating from the domain itself will come from 1.2.3.4. Under this 
proposal, we would see 1.2.3.4 being greylisted (or at worst,
blacklisted for 
nonmatching exchangers!!) despite originating at a real world smtp
server. 
With companies like mxlogic and postini acting as offsite exchangers,
this 
complicates a solution like below. Any suggestions on how to get
around that?