My original goal was making tmda work from maildroprc... got it working
now - if this env hack is going to cause problems can someone let me know?
Sam had mentioned (when I was cc'ing :
cc "|env >log"
that the pipe would overflow and cause problems... if so, how do I resolve?
In the meantime here is my solution:
And success!
In the users home dir:
/usr/local/tmda/bin/tmda-keygen
mkdir /home/mitch/.tmda
echo 596041dcfe0a344ecbfc2478fc4b8ecde169ea9c >/home/mitch/.tmda/crypt_key
chown -R u595 /home/mitch/.tmda
chmod -R u=rwX,g=,o= /home/mitch/.tmda
touch /home/mitch/.courier-default
chown -R u595 /home/mitch/.courier-default
This is from my maildroprc:
LOCKTMDA=$HOME/.tmda.lock
flock $LOCKTMDA {
# to "| env SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter"
# IF EXITCODE is 99, then tmda processed an action
# IF EXITCODE is 0, then tmda has approved the message for further
action
cc "| env SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter"
if ($EXITCODE != "0")
{
#tmda has done it's job - get rid of the evidense!
to "|cat >/dev/null"
}
}
#IF the message hasn't been dumped at this point, continue processing
Hope that example helps someone!
m/
-------------------------------------------------------
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
