Roland <[EMAIL PROTECTED]> writes: > --On Mittwoch, 14. Januar 2004 10:08 -0500 Courier User <[EMAIL PROTECTED]> > wrote: > >>> But the point is still there: TDMA is supposed to return challenges >>> to unknown senders which is just not possible with bounces. >>> And tdma especially trolls for bounces with exactly those challenges. >>> >>> The line in .mailfilter should be something like: >>> >>> cc "| test \"$SENDER\" && tdma-filter" >> >> TMDA functions properly if the SENDER variable is "" (empty string) >> as opposed to being completely unset. The "cc" command above works >> fine. > > What do you expect to achieve by sending a challenge for a received > bounce ? > > Doing such stupid things actually is typical for those sending back > challenges to everything received (preferably on a unfiltered catchall), > and they really deserve the 100% false positive rate... > > Roland
That's not the reason for making sure that SENDER is set to an empty string. I never said anything about sending a challenge to an empty sender, nor do I recall reading that anyone else said that. The reason for this is that TMDA throws an exception and aborts its processing if the SENDER variable is unset. If SENDER is an empty string, then TMDA functions fine. This allows a TMDA rule such as this: from <> drop This rule never gets executed when TMDA aborts with an exception during the missing SENDER variable case. Think before you start throwing the word "stupid" around. -- 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
