"Jason R. Mastaler" <[EMAIL PROTECTED]> writes: > Tim Legant <[EMAIL PROTECTED]> writes on tmda-users: > > > The workaround is to deliver to a program > > This might make a nice feature addition though, to eliminate the > dependency on an external LDA even further. Perhaps the deliver action > could accept a comma seperated list of actions. e.g, > > to [EMAIL PROTECTED] [EMAIL PROTECTED], ~/Maildir/ > > Same for Defaults.DELIVERY. > > DELIVERY = "[EMAIL PROTECTED], ~/Maildir/"
The one thing that's been a sticking point for me has been how to handle different actions. Your examples are a single action (delivery) with several destinations. What if I want to bounce or confirm a message mailed to, e.g. a private address, *and* place it in a special mailbox? Of course, I can just bounce or confirm it and it will be in pending/ where I can look it up, but if I get a lot of spam, I will have to sort through a bunch of garbage to find mail to that address, whereas having it in a mailbox that I can browse in my MUA seems more convenient. Also, I think commas are legitimate in email addresses (weird, yes, but legal), so we might have to introduce quoting on comma-seperated actions. Not awful, I think, because I believe we can leave single actions unquoted, thus retaining backward compatibility. Tim _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
