[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Excluding users from the milter

From: Chuck Yerkes
Subject: Re: Excluding users from the milter
Date: Mon, 30 Jun 2003 14:04:35 -0400
User-agent: Mutt/1.4i

Quoting Cassandra Lynette Brockett (address@hidden):
> Just a simple question - do you need to exclude them from the milter running
> for them, or just exclude the milter from changing/modifying their messages?
> If the former - no such luck without hacking the milter.  If the later, then
> all you need to do is tell the milter to not modify the emails, and/or set

Ideally, (IMHO), the right answer would be this:
When sendmail starts up, it gathers the input filter names.
It would make sense, and be consistent with other sendmail "ways"
to have sendmail invoke a rule per milter.  So if I have:
O InputMailFilters=SpamAssassinFilter,

the rule "check_SpamAssassinFilter" would be invoked before sending
data to the milter.

Sendmail would look at the return value to decide (ok = "send
through milter" and error = "don't send through milter).

Bumps include mail to several people, some of whom get it, some
don't.  Sendmail splits mail already and could do that here.

An alternernative would be to have the milter use the access map
(access.db) to decide who gets miltered or not.

The access map is used as a single point to manage various
access points to mail.

Again, ideally, the map lookup routines would be in a library
from sendmail and not buried in the single binary.  This way
the library can deal with the access map being a db file,
an LDAP entry, a HESIOD map, or a NIS map.

  Sendmail folks have run into this as a problem over and over
and over. (I've been doing SNMP things where I have to hand
parse the file and that's just wrong - I should
be able to say something like:

   char **imf;


reply via email to

[Prev in Thread] Current Thread [Next in Thread]