On Wed, 14 Jan 2004, Mitch \(WebCob\) wrote: > > > 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?
It took me a while, but 'man dot-courier' got them to me. I'd like to suggest a link in maildrop/maildropfilter's manpages to dot-courier's, something along the lines of "for a list of exit codes and what they mean to courier, please see dot-courier" -- Ensign Walnut approaches Dr. Crusher with caution... Jon Nelson <[EMAIL PROTECTED]> C and Python Code Gardener ------------------------------------------------------- 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
