I'm not sure if this will do all of what you want, but here's what I do:<snip>
Thanks!
I actually saw that in the postfix users list, but haven't tried it yet, because I don't think it will work for exactly what I want to do... in short, I need it to go deeper:
I need a way to re-define the environment variable "EXTENSION" based on multiple recipient extensions just like qmail did, and I think your solution will just work for .forward and .forward-default, which is not quite what I want to do. I want to have .forward-tmda and .forward-tmda-default working, and I don't think postfix can ever do that on its own.
So I'm toying with a wrapper around maildrop which will do the following:
For example, consider the address "[EMAIL PROTECTED]" (in reality the script will be generic and handle any number of extensions)
- First check if the file "~user/.mailfilter-ext1-ext2-ext3" exists. If so, set EXTENSION to "" and execute maildrop with that filter.
- If not, check if the file "~user/.mailfilter-ext1-ext2" exists. If so, set EXTENSION to "ext3" and execute maildrop with that filter.
- If not, check if the file "~user/.mailfilter-ext1" exists. If so, set EXTENSION to "ext2-ext3" and execute maildrop with that filter.
- If not, set EXTENSION to "ext1-ext2-ext3" and execute maildrop with the default ~user/.mailfilter or /etc/maildroprc.
I wonder how that will work... It's quite a lot like the dot-qmail processing I love, but this way I don't have to symlink all these -default files to the original ones.
Do any python gurus know: If I don't touch sys.stdin and then do an os.execl(), will the program I've exec'd have access to the same stdin?
-- Jim Ramsay "Me fail English? That's unpossible!"
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
