> > I agree completely. Sam? > > maildropfilter already fully documents how the exit command works: > > EXIT - TERMINATE FILTERING UNCONDITIONALLY > exit > > The exit statement immediately terminates filtering. > maildropâs return > code is set to the value of the EXITCODE variable. > Normally, maildrop > terminates immediately after successfully delivering the > message to a > mailbox. The exit statement causes maildrop to terminate > without deliv- > ering the message anywhere. > > What exactly is so confusing, here? >
To you - nothing - to me (now) nothing... maybe it doesn't belong there, but belongs in a FAQ. How do I dump a message? Set the exit code to 0 and call exit. Or maybe an example... I've seen a lot of people I'd normally consider reasonably smart waste a lot of time trying to send to /dev/null - (including myself). What about a reference of exit codes and what they mean? 0 - message to be considered delivered (even if it was not actually sent anywhere!) 1 - defer.. (guessing) 99 - temp fail? For those of us who started before courier, although in many ways better I think, some of the changes can be confusing... this would be one of em Thanks! m/ PS - any thoughts on the delivery to char devices / sockets I was asking about? Just speaking conceptually - not asking you to code it ------------------------------------------------------- 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
