On Wed, May 25, 2016 at 10:56:36PM +0200, Dirk wrote: > > What kind of mappings happen in that regexp table? Sure you can > > the mail delivered to some maildir or other, but how are users able > > to read the mail? Presumably dovecot still needs to know about > > the mailboxes created by virtual(8) so it can grant access to them > > to suitably authenticated users via IMAP. > > /.*\.d...@x.domain1.com/ x.domains1.com/dirk/ > > This is kind of my own "spamgourmet.com" implementation where I can give > email Addresses on the fly to any "webpage". > Everything is dilvered to one maildir. > > > > But now I would like to use sieve with dovecot. > > > > For both domains? Or just one of them? > > Ideally both. > > >> Therefore I would have to enable > >> #virtual_transport = lmtp:unix:private/dovecot-lmtp > > > > Fine, now the LMTP recipient needs to be a recipient name known to > > dovecot, but that's not much different from the requirement that > > dovecot be able to associated users with mailboxes for IMAP. > > > > So you've not explained your problem in sufficient detail. > > As to my knowlege dovecot can not handle "dynamically" created emails > addresses.
Give it addresses it knows. > > Well dovecot does not know about that mailbox. Deliver to a mailbox > > that dovecot does know about. You'd typically use virtual_alias_maps > > for that. > > Not possible - there is no mapping until the mail arrives. The email > address is dynamic. Nonsense, essentially the same regexp table can be used in virtual_alias_maps instead of virtual_mailbox_maps: /\.d...@x.domain1.com/ d...@x.domain1.com -- Viktor.