need organizational hint

[Ken Murchison]

Phil Howard wrote:
> 
> On Thu, Apr 10, 2003 at 10:11:40PM -0400, Ken Murchison wrote:
> 
> |
> |
> | Phil Howard wrote:
> | >
> | > On Thu, Apr 10, 2003 at 04:52:07PM +0200, Christian Schulte wrote:
> | >
> | > | Adam Tauno Williams wrote:
> | > |
> | > | >>3.  Each user can specify their own rules for blacklisting and/or
> | > | >>    whitelisting senders and sending server, either explicit, or
> | > | >>    by their own choice of DNS based blacklists / whitelists.
> | > | >>
> | > | >>
> | > | >
> | > | >In Cyrus this is accomplished via Sieve.  If your not going to use Sieve then it
> | > | >is purely an MTA/MUA issue, and not a Cyrus one.  But if I were you I'd use
> | > | >Sieve it is very nice and seem very efficient.
> | > | >
> | > | >
> | > | In 2.2 sieve scripts get compiled on the fly into bytecode...you will
> | > | not find such a solution for e.g. procmail!
> | >
> | > And how does this get run?  Is it its own MTA?  An SMTP front end?
> | > An LMTP front end?  Patches to Postfix?
> |
> |
> | The Sieve bytecode gets executed at the time of delivery by Cyrus lmtpd.
> 
> How will it do rejections that are to be done based on the IP address
> of the MTA that makes the SMTP connection to my MTA?  Is that address

It can't.  You can only do Sieve rejections based on headers contents,
SMTP/LMTP envelope contents and message size.  You should read RFC 3028
to understand the capabilities of Sieve.

If you want to do blacklisting by IP, then this is an MTA function.

-- 
Kenneth Murchison     Oceana Matrix Ltd.
Software Engineer     21 Princeton Place
716-662-8973 x26      Orchard Park, NY 14127
--PGP Public Key--    http://www.oceana.com/~ken/ksm.pgp