"Jason R. Mastaler" wrote:
> Good suggestion, I've made note of it. I don't think many users of
> the current 'pipe' actually care about the body anyway. It might also
> help users who like to 'pipe' to subprograms that cause SIGPIPE, which
> in turn triggers an exception/deferred delivery in TMDA, which in turn
> leads to a post to this list. :-)
...
> We've discussed this before I believe, but I can't find the thread.
> It's not possible currently, but I think it would make sense for the
> future. The body is processed for a few other general things such as
> determining the size of the message to decide whether or not to attach
> it to the confirmation request. So, it would be a combination of
> working through these cases, and then some code reorganization.
Glad my suggestions were well-received. I came up with another last
night, which actually arises from my own usage. It occurs to me that it
would be useful to have an additional state for mail in the pending
queue. For the sake of argument, let's call it "marked," although it
might work much like selection.
In my particular case I get a truly massive amount of spam email --
really far too much to go through regularly with tmda-pending over the
whole batch. As a data point, there are currently almost 15 000
messages in my pending queue, and I've only started using TMDA since
Friday (the expiration rate is set at the default, two weeks). It
amounts to about 3000 a day -- and while I have `tmda-pending -b -T -Y
25h' piped to mail in a daily cron job, even then I can only muster up a
quick scan down the page. Going through the whole queue periodically
with tmda-pending is just out of the question -- it's way too big.
Out of all that mail that's indefinitely held or waiting to be
confirmed, it would be useful to be able to mark some of it to stand out
from the rest of the crowd. This additional state, MARK, acts just the
same as HOLD but can be manipulated independently -- that is,
tmda-pending gets new options for "mark" and "unmark," there's a new
action called "mark" for filters, and tmda-pending has a new command
line switch for operating on only marked messages (and, perhaps, another
for selecting unmarked messages).
The idea here is that while most spam will be held or waiting for a
confirmation that will never come, special filter rules which look
something like
headers-file "/home/max/.tmda/rules/mark" mark
can allow me to set some mail aside from the rest of the queue (of
course it would be in the same physical location), allowing me to, for
example, specially select email that looks like it's a TMDA
confirmation. Then `tmda-pending -i -m' (for example) would allow me to
go through only the marked mail, making a more directed analysis of mail
that had some promise (by whatever criteria I chose).
The advantage here is that this seems pretty straightforward and is
completely backward compatible (users who have no need of the marking
facility need not even know it's there; marking could even be off by
default to the point that it doesn't show up in the tmda-pending
interactive prompt).
What say you, people of Rome?
--
Erik Max Francis && [EMAIL PROTECTED] && http://www.alcyone.com/max/
__ San Jose, CA, USA && 37 20 N 121 53 W && &tSftDotIotE
/ \
\__/ I never could have predicted / That I'd feel this way
-- India Arie
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
