On Fri, 7 Nov 2003, Andrzej Filip wrote: > Rob Siemborski wrote: > > On Thu, 6 Nov 2003, Andrzej Filip wrote: > > > >>>- What would the map name be? cyrus? Would it ever change? Can people > >>>envision different types of maps that this daemon would have to support? > >> > >>"cyrus" seems to be good default name. > >>Let us start with "mailbox presence" checking. > > > > I agree. > > > >>Next version may also: > >>* check if mailbox will accpet message of given size based on "SIZE=" > >>parameter of "MAIL FROM:" > >>* take into account who successfully authenticated SMTP session > >>[it can make some folders accessible] > >>* apply some sieve reject rules based on envelope sender and sending host > > > > This last one might be very hard, especially if rules are based half off > > an envelope bit and half off a header bit. I wouldn't want to think of > > trying to run a sieve interpreter with limited information. > > Would not it be posiible to interpet only heading sieve rules which reject > message based on info available at "RCPT TO:" point ? > First "non reject" or "need information not available yet" sieve rule would > stop "envelope based" sieve rules interpretation. > [ Reject what you know for sure you will reject later - ASAP reject ] > > It would be nice to allow sieve reject messages before message body is > received. IMHO it is worth to investigate achievable gain/cost. >
This would be nice, but as much as sendmail 'abuses' these maps I wonder if busier sites would be able to use such maps. -- Igor
