On Sun, Sep 28, 2003 at 04:10:36PM -0400, Sam Varshavchik wrote: > Courier User writes: > > > > >If there's a .courier or a .courier-default file in the recipient's > >HOME directory, will that somehow override the localmailfilter > >processing? > > No. localmailfilter occurs when the message is received from the sending > mail server, before it is even accepted for local delivery. $HOME/.courier > is not even in the picture yet.
OK. Well, I got it working ... it was a problem with the specific user ID I was using to test it. This brings up another question. In the localmailfilter(7) man page, it states that for local delivery filtering, maildrop will be invoked as follows: HOME=$HOME FILTER -D uid/gid -M filter (where FILTER is, in this case, the full pathname for maildrop) However, as part of some debugging, I noticed that the following arguments are actually being passed to maildrop, at least in the rcptfilter case: -D uid/gid -M rcptfilter domain.com ip-addr [EMAIL PROTECTED] I presume that the final three arguments are the values of the following environment variables, respectively: TCPREMOTEHOST TCPREMOTEIP SENDER Is that correct? Also, can it be assumed that if BLOCK2 is also set, that it, too, will be appended as an argument to maildrop in this case? In general, can I count on these arguments always being passed to maildrop during rcptfilter and smptfilter calls, in the local filtering case? If so, should the documentation be upgraded to state that this is the case? Thanks. -- Courier User [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
