* David T-G <davidtg-muttusers@xxxxxxxxxxxxxxx> [2003-09-07 13:54]: > David, et al -- > > ...and then David Rock said... > % > % * David T-G <davidtg-muttusers@xxxxxxxxxxxxxxx> [2003-09-06 09:25]: > % > > % > to have that list of known addresses in the MTA's file -- and I don't > % > want to have to mess about at the MTA level anyway. > % > % Well, you are already messing with the MTA to add the addresses, whether > > No, that's what I don't want to do. My only config is in my .qmail files > and my .muttrc file. I didn't really pick up on your using qmail. I don't, so I don't have any experience with the config files, but the little reading I've done gives me a little better understanding of the problem. Let me see if I have this right: username on the box is davidtg series of .qmail files related to this id: ~davidtg/.qmail-davidtg-muttusers ~davidtg/.qmail-davidtg-foo ~davidtg/.qmail-davidtg-bar etc... When you said "on the fly", I didn't realize qmail has USER defined files for transport directives. If this is how it works, then the problem is actually simpler than I thought. Just create a script to walk the directory for .qmail-extension and build the alternates dynamically from that. Brute force (and easiest to write) for the example above would end up looking like this: set alternates="(david-tg-muttusers|davidtg-foo|davidtg-bar)@domain" slightly more fancy (but more work) set alternates="david-tg-(muttusers|foo|bar)@domain" so the .muttrc would look something like this: set alternates=`altscript.sh` I would expect that you could even re-source .muttrc if you added a new address. Although that is probably a bit too "on the fly" even for you ;-) > HAND to you, too :-) Thanks. -- David Rock david@xxxxxxxxxxxxxx
Attachment:
pgpZnezCJjEcx.pgp
Description: PGP signature