On 2010-08-17 Tom Kinghorn wrote:
> What I would like to achieve is that any IP which connects to any mail
> server which has one of our clients IP's
> gets rbl scanned.
>
> /external_ip [spammer] {Client host [193.138.93.1] listed at
> dnsbl.njabl.org; }
> |
> |
> V
> clients_mail_server ( eg 41.25.3.5) <unknown-MTA>
> |
> |
> V
> our_smarthost_for_clients <postfix using amavisd-new>/
>
> I would therefore like to scan the mail as the mail originated from an
> IP which is not our IP So the mail would be blocked as the originating
> IP is listed at njabl.org
AFAICS your approach is likely to generate backscatter and perhaps even
violations of your clients's contracts. Don't do that.
RBL filtering in your scenario should be done either at your clients'
mail servers or not at all.
Regards
Ansgar Wiechers
--
"All vulnerabilities deserve a public fear period prior to patches
becoming available."
--Jason Coombs on Bugtraq
