Hacking it in order to change lazyaw semantics and cause it to consider
IP+recpient is easy, you just have one line to move. But that change cannot be
integrated into the sources since the change on lazyaw breaks existing
configurations.
I appreciate your time in explaining what can be done on the source code, but in the environment I'm working with it's not acceptable to use patched code (hard to maintain). We need to use the code from upstream.
I just want to clarify why this is needed (maybe then it would be interesting for the project owners to incorporate this).
We see lots of emails coming from large web hosting or mass-mail companies. Those come from the same IP addresses (or pools of IPs), but with different senders. Example: we caught 1 IP which sent email to us from 55 different domains over the span of 24h. If we would white list per IP only, a lot of junk would just pass, but at the same time grey listing per ip+sender+recipient causes delays in deliveries of valid emails (like if 1 sender emails 10-20 different recipients).
I hope someone would consider implementing such option on the upstream code, instead of me dealing with patched/custom versions.
Thank you.
(irc: netmask on freenode)