Roland <[EMAIL PROTECTED]> writes:
> --On Dienstag, 13. Januar 2004 09:55 -0800 "Mitch \\(WebCob\\)"
> <[EMAIL PROTECTED]> wrote:
>
>> I'm trying to call TMDA, and I get an error that SENDER is not set during
>> one of it's processes... it IS set during the others... the difference in
>> the messages (from the logs) is that in this case from is showing as <>
>>
>> Someone on the TMDA list says it is maildrop unsetting the RMPTY env vars...
>>
>> I tried changing my code to reset it, but it isn't working (syntax error)
>>
>> to "| SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter"
>
> This wont ever work, and there is also absolutely no point
> to pipe mails with empty sender into tmda.
This works fine if you use "env" as follows:
to "| /usr/bin/env SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter"
TMDA works fine with a SENDER environment variable set to the empty
string (""). It just fails when the SENDER variable has been completely
removed from the environment, as the following command
(counter-intuitively) does within maildrop:
SENDER=""
Using the above command (with /usr/bin/env) guarantees that TMDA works
from within maildrop. I know, because that's what I had to do on my
host to get it working.
> use |env to see what variables are available, and import
> those you need in maildrop.
>
> Roland
--
Courier User
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
