...and so on. In this case, actually, regexp matching isn't needed, but you get the idea.
Hmmmm... Good idea!
Along the same lines I just did the following, and it worked perfectly (so far):
~/.forward:
---------------------------------------------------------------------
"| /path/to/maildrop -d ${USER}"
---------------------------------------------------------------------~/.mailfilter: --------------------------------------------------------------------- import SENDER import RECIPIENT import EXTENSION
if( $EXTENSION =~ /^tmda-/ )
{
EXTENSION = substr( $EXTENSION, 5, 1000 )
to "| /path/to/tmda-filter"
}
if( $EXTENSION =~ /^tmda$/ )
{
EXTENSION = ""
to "| /path/to/tmda-filter"
}
---------------------------------------------------------------------This lets all mail through except mail to [EMAIL PROTECTED] which is TMDA-protected. Please note that if you use this yourself, the number after $EXTENSION in the 'substr' field must be changed to be equal to the length of the extension plus one for the dash. This is left as an exercise to the reader.
That kind of feels like jumping through hoops for something that used to be so elegant. Oh well, that's the price of progress. Or lack-thereof.
I think I'm still going to write my maildrop wrapper, and call it "maildrop-ext". It will let me define .mailfilter-tmda which will be executed my maildrop for both [EMAIL PROTECTED] and [EMAIL PROTECTED] The config above is pretty much doing the same thing, my way will make it more elegant to maintain. In my opinion. I'm sure some people prefer one mamoth filter file to many smaller filter files, but I'm not one of them.
When I finish the wrapper, would anyone like to use it? I can post it here.
-- Jim Ramsay "Me fail English? That's unpossible!"
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
