Paul J Stevens wrote: > Peter Rabbitson wrote: >> I am using latest dbmail 2.2.15. I just realized that *any* sieve >> rule present for an account (even if the rule is disabled), implicitly >> disabels any support for addr+folder@ type of address expansion routing. > > I assume you mean that having an active sieve-script will disable > subaddress delivery. That is correct. The default-mailbox, derived from > the subaddress does not propagate into the sieve layer.
I am not sure what you mean here (especially since you are attaching a patch further down). Basically my question is - what is the precedence here? Can Sieve *and* subaddressing coexist? Or it is solely one or the other? >> The way things are now, if a user wants to take advantage of sieve, >> they will have to populate the sieve rulebook with *all* + extensions >> used so far, so the mail delivery will continue as before. This is... >> suboptimal :) > > I've just pushed a fix for this. > > > Try the patch attached plz. My test-setup got screwed up, and I am not brave enough to test this on prod. I will get around to this in a couple of weeks. Thanks! _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
