Please do not top post.
> While that does make sense I can seem to get exim to let me put a pipe
> command in that section. I not understanding what im doing wrong.
>
>
> I wanted it to run right at
>
> drop dnslists = relays.ordb.org : bl.spamcop.net
> message = your mail server $sender_host_address is in a black list \
> at $dnslist_domain ($dnslist_text)
Simple!
drop message = your mail server $sender_host_address is in a \
blacklist at $dnslist_domain ($dnslist_text)
dnslists = relays.ordb.org : bl.spamcop.net
condition = ${run{somecommand $sender_host_address}{yes}{yes}
Remember, order counts!!! It will check dnslists then the condition but
only if dnslists was true!
I do this myself to blacklist people who attempt to relay via my server.
> But its like pipe isn't allowed in that section.
Exactly. It's not because it does not make sense.
> -----Original Message-----
> From: Wakko Warner [mailto:wakko@animx.eu.org]
> Sent: Thursday, September 30, 2004 6:14 AM
> To: David Murphy
> Cc: exim-users@???
> Subject: Re: [exim] SBL and iptables
>
> > I have been trying to work out a way so if a sbl/rbl match is found
> rather
> > than just denying the connection . I can have that same acl pipe to
> iptables
> > and add a iptable deny rule.
> >
> > Every method ive tried from a pipe to a execute has failed someone
> please
> > help me.
>
> Probably because exim is not running as root? I've thought about this
> myself, but my firewall is not on the local machine.
>
> How about trying sudo? I did this at work to automatically update the
> mcafee virus definition files when I get an email from mcafee saying that
> they released an updated version.
>
> --
> Lab tests show that use of micro$oft causes cancer in lab animals
>
>
--
Lab tests show that use of micro$oft causes cancer in lab animals
