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?
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?
No, you can use the import command to take it from the environment.
While reviewing the code to confirm the above, I discovered that the environment variables BOUNCE and BOUNCE2, if set in the smtpaccess file, will be passed as additional arguments to the filter. I don't remember what was the original reason for that.
In general, can I count on these arguments always being passed to maildrop during rcptfilter and smptfilter calls, in the local filtering case?
Yes.
If so, should the documentation be upgraded to state that this is the case?
Probably.
pgp00000.pgp
Description: PGP signature
