"Mike Usmar" <[EMAIL PROTECTED]> writes: > Currently having a few problems getting SpamAssassin working correctly with > TMDA. Now I've searched through most of the mailing list archives, and found > nothing in reference to having TMDA calling spamassassin after all > white/black lists have been checked. Only references to spamassassin is > where you run messages through SA first, then through TMDA. > > What I am trying to do, is run messages through TMDA like normal, and if > they do not match any whitelists or blacklists, then run message through SA, > and tag the subject with [SPAM], and then in our web interface to the > Pending queue, the user can see which is definitely spam (tagged subject by > SA), and which is just pending (and can order the pending items by subject, > and put definite spam at the top... etc.) > > This is my current TMDA filter file: > > from-cdb /etcmail/tmda/actrix_whitelist.cdb ok > from-cdb /etcmail/tmda/actrix_blacklist.cdb bounce > from-file -autocdb ~/.tmda/whitelist ok > from-file -autocdb ~/.tmda/blacklist bounce > pipe "/usr/local/bin/spamassassin" confirm
The 'pipe' rule pipes the mail to the specified program but doesn't read the message back; in other words, it doesn't treat the program as a filter. It uses the return code from the program to determine if the rule matched. Thus, any changes SpamAssassin makes to the message are not preserved. The behavior you were hoping for is interesting, though. I'm noting it as a possible additional feature sometime in version 1.x. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
