What about a new incoming action "ok-mark" (or ok-log, ok-test, or whatever)? It would behave as normal "ok", that is mail would be delivered. But additional to that, it would set the X-TMDA-Action header in that mail, regardless of the global ACTION_HEADER_INCOMING setting.I'll leave it to Jason to say yes or no, though I have a vague feeling he'll say no. ;-) This seems somewhat misplaced, to me. For one, why would X-TMDA-Action: be needed on only some e-mails? The testing scenario is identical to ACTION_HEADER_INCOMING=1 and ok for everything.
In the testing scenerio, one could use ok-mark for all lines in the incoming filter, where some testing is wanted.
ok-mark would pass mail through tmda-flagged and could be moved by the MTA into a special folder. [This folder contains most likely annoying spam or even more dangerous attachments. Look through that folder every once in a while but be more carefull than with normal folders.]Why not just tell TMDA to deliver to said folders? This sounds more like a spamassassin application in some ways, though.....
With existing scenario and ACTION_HEADER_INCOMING=1 set globally, it could be thatIf something hits ok, it gets delivered to whatever DELIVERY is set for. You can over-ride that definition on an individual rule with deliver=path/to/Maildir/. If that's not set, then under qmail, it resumes processing of the .qmail file following TMDA. So, if I understand the question properly.... no.
from-file ~/.tmda/lists/whitelist ok
would also be sent to the bad folder. Is that so?
Now, if you're thinking of dumping everything that has X-TMDA-Action:, then yes, all your mail delivered by TMDA would be caught by that unless you're also checking the content of that header.
In my case i have some repeating spam coming in to email '[EMAIL PROTECTED]' [rend is not used in my domain]Hmm.... My first suggestion would be simply to bounce mail to unknown users -- why bother processing something addressed to a user who doesn't exist? However, since some of my old setups for my domain didn't let me do that either, I think it's a valid, if rare, question.
with:
to '[EMAIL PROTECTED]' ok-mark
I could see my bad email-folder filled with that spam and delete it occasionally, but by hand.
with: to '[EMAIL PROTECTED]" drop I can (after some time) not even see it anymore.
to '[EMAIL PROTECTED]' deliver=~/Maildir/.Spam/
would drop mail of that sort to a subfolder Spam. Once you're satisfied that no mail for you is ever mistakenly addressed to [EMAIL PROTECTED] (why would it be, again?), you can switch to
to '[EMAIL PROTECTED]' drop
Though, technically, leaving it pending (hold) and checking with tmda-pending is very similar to a spam folder. If you're ultra-worried about real mail getting trapped in pending, just set a cron job to do the following every few days:
tmda-pending -C -b -s | mail -s 'Pending TMDA mail for $USER' $USER
-- Micha�l A. Bishop
"From silly devotions and sour-faced saints, spare us, O Lord." -St. Teresa of Avila
"A truly good book teaches me better than to just read it. I must soon lay it down and commence living on its hint. What I began by reading, I must finish by acting." -Henry David Thoreau
smime.p7s
Description: S/MIME Cryptographic Signature_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
