Data Vortex <[EMAIL PROTECTED]> writes:
> Coming from a user's perspective, I'd like the wording to be as
> flexible and as clear as possible, and I think this approach offers
> more ways to evolve as the tmda filter language matures.
>
> I started using tmda when I had 1500 lines of procmail recipies
> handling all my incoming messages. I was hesitant to transfer much
> of that ability to tmda filters becuase of the difficulty presented
> with working in a first match always wins environment. Procmail
> evolved this way - starting as a first recipie wins, but adding flow
> control in the form of the c, e, a recipie flags, and nesting.
And procmail is an abomination IMHO. The last thing I want to see is
for TMDA to become as convoluted as procmail.
TMDA isn't a complete replacement for procmail. Users with advanced
filtering needs are probably better off sticking with procmail or
maildrop. TMDA makes it easy to connect with such tools.
I'm in favour of extending TMDA's filtering abilities to the point
where it will start to become a support burden due to excessive
complexity.
> I think it would have value for me for tmda filter files to offer
> this level of configurability. Arranging the logic as above could
> allow for extensions of this thinking in the future:
>
> to [EMAIL PROTECTED] {
> size < 5K
> | pager-program
> deliver=~/Mailbox
> else
> deliver=~/Mailbox-notpaged
> }
Gack.
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers
