Lloyd Zusman <ljz <at> asfast.com> writes:
>
> "Monique Y. Mudama" <spam <at> bounceswoosh.org> writes:
>
> > On 2004-10-14, Lloyd Zusman penned:
> >> For reasons that are too byzantine and convoluted to explain here,
> >> under special circumstances, I want certain messages that have not
> >> been processed through TMDA to be put into the TMDA pending queue for
> >> a given user, as if they were saved via the 'hold' directive.
> >>
> >> [ ... ]
> >>
> >> Any ideas?
> >
> > Have maildrop add a header to the message, pass the message on to tmda, and
> > have tmda put all messages with that header on 'hold'.
>
> Thanks. Yes, I thought of something like that, but it seems too
> complicated to manage. [ ... ]
In re-reading this, I realize that I need to be more clear about why
this would be complicated:
I need this capability to be manageable from a global maildrop filter
file, and it has to work for a group of users. In this filter file, I
can indeed easily use "reformail" or its moral equivalent to add the
special header to the appropriate incoming messages for this group of
users. However, each individual TMDA user would need to put the appropriate
rule into his/her own TMDA rules file in order to cause these messages
to be put into the pending queue.
I know that I can set up users with a default TMDA filtering rule that
performs this function. However, each user could override this by
modifying his/her TMDA filter files. Also, I would have to manually
add such a rule to existing TMDA rule files, thereby intruding on the
private data of the users on my system. I am loath to do that.
And finally, even if I did all of this, it requires extra system
administration capabilities to keep these two cooperating processes (the
global addition of the header and the management of each user's TMDA files)
in sync.
All that is certainly do-able, but the "tmda-hold" utility that I posted
in my previous message can do this in a single step, thereby obviating this
complicated procedure. All that would be needed would be to put the
following rule into my global maildrop configuration file:
if ( ... certain conditions ... )
{
to "|/path/to/tmda-hold"
}
In writing tmda-hold, it occurred to me that a more general capability
might be useful: to specify an action on the command line of tmda-filter
which will unconditionally be performed on the message that it is
processing.
For example:
tmda-filter --action=hold
put the stdin-based message into the pending queue
tmda-filter --action=ok
deliver the message normally (for example, in case the
message would be handled otherwise by the user's TMDA
rules)
tmda-filter '--action=deliver=~/mbox.spam'
send the message to the spam mailbox
... etc. ...
A little while ago, I made this proposal in the tmda-devel mailing list.
I'm willing to write this enhancement and post patches to tmda-filter and
tmda-rfilter if you folks deem this to be a useful.
Any thoughts?
Thanks in advance.
--
Lloyd Zusman
[EMAIL PROTECTED]
God bless you.
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
