Aaron Stone wrote: > On Mon, 2007-04-23 at 00:00 +0200, Peter Rabbitson wrote: > >> I didn't know Sieve is _that_ powerful. Thanks for pointing this out. >> But imho a possibility to say with a single forward rule "user bob gets >> all mail that user alice gets" would still be very useful. Of course I >> have no clue how hard would that be to implement, so you can safely >> ignore my ramblings. > > Alice can forward her mail to Bob, but Alice would be the owner of that > script and in control of it. If you wanted to do it at an administrative > level, you'd have to use a forward. > > We have an idea out for running a Sieve script at the time that a > message is first received for delivery, which could duplicate some of > the alias/forward stuff but would also add a lot of other features, such > as header tests and maybe spam controls down the road. This Sieve script > would be run _before_ DBMail has resolved to which user account the > message will be delivered, so it would be an effective way to catch > messages that are eventually going to be delivered to Alice. > > The solution might be an administrative Sieve script that runs for each > user prior to their own Sieve scripts. We'd need at least one new column > in the database to handle this. Is if this is a reasonable use case that > should be handled by DBMail? >
Yes, this sounds like an excellent idea. Furthermore the Sieve hooks should be available pre- and post- routing, to solve the exact scenario I am describing. Instead of the administrator digging around to see what addresses are assigned to bob, he says with a single match in postrouting "everything that would end up in bob's inbox, goes there _and_ in alice's inbox as well, and to the supervisor's 'bob_on_vacation' box so he can see how much more work Alice did". _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
