[SA-exim] Side-effect involving mailing lists

[Marc MERLIN]

On Sun, Nov 16, 2003 at 02:43:21PM -0800, Rick Moen wrote:
> > That's why the config file has this:
> > # Please, don't teergrube people you relay for you or your own MXes :-)
> > SAteergrubecond: ${if and { {!eq
> > {$sender_host_address}{204.80.101.251}} {!eq {$
> > sender_host_address}{198.186.202.175}} {!eq
> > {$sender_host_address}{194.2.204.37} } {!eq
> > {$sender_host_address}{216.239.45.4}} {!eq
> > {$sender_host_address}{216.109 .84.130}} } {1}{0}}
> 
> OK, I'll look up the IPs of the problem MLM hosts, and append
> conditionals for them.  Question:  Might this be worth breaking out
> into a /etc/exim4/sa-exim-whitelist-ips file, if only because otherwise
> the syntax is a bit error-prone?
 
The teergrube condition could be based on anything, people are welcome to
type any valid exim parseable statement there (some use mysql, some check
for other things like header data, etc, etc...)

Looking in /etc/exim4/sa-exim-whitelist-ips is fine. If people want to
contribute interesting conditions, I don't mind adding them as samples
in the config file.
 
> Alteratively, they could be in multiple lines like:
> 
>    SAteergrube_not: nnn.nnn.nnn.nnn 

I don't really see the point. This can all be done with the statement above

> > Other times, I whitelist the list in SA's config, so teergrubing doesn't
> > kick in.
> 
> Just to confirm, you're talking about the aforementioned SAteergrubecond
> line, right?

No, you can whitelist them in SA's local.cf too

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/   |   Finger marc_f at merlins.org for PGP key