Monday, February 21, 2022, 9:08:41 PM, Jaroslaw Rafa wrote: > Dnia 21.02.2022 o godz. 13:10:45 Phil Biggs pisze: >> >> - emails sent to (external) validuser@ addresses are validated >> as present in virtual_mailbox_maps >> - validuser@ addresses are translated to (internal) dovecotuser@ >> via virtual_alias_maps >> - only dovecotuser@ addresses are accepted by dovecot >> - emails originally addressed to dovecotuser@ addresses are rejected
> Just asking: how do you deliver mail to Dovecot so that it needs to know and > accept any email addresses? Dovecot doesn't receive nor send mail (from what > I know), it only provides access to mailboxes. If Postfix knows to what > mailbox it should deliver the mail addressed to particular user (and that's > what should be provided by virtual_mailbox_maps), then it's only Dovecot's > thing to provide coordination between user's login and the correct mailbox. > So for me virtual_alias_maps seems completely unneccessary in your case. What > funtion exactly does it provide here? Dovecot only accepts email for addresses for which it has a matching user account. As you say, it is just used a message store. However, I wasn't able to find a way to have a dovecot user receive mail addressed to any address other than one that matched the login "user" name. I also couldn't face the prospect of manually changing the login user in the MUA for every account. The internal dovecot user accounts are more "human-readable" (e.g., ml-postfix-users@...) but the external email addresses used by those accounts are almost all of the format mbyymmdd@... (long story). virtual_mailbox_maps only validates an external address as deliverable. virtual_alias_maps rewrites the external address to the corresponding internal address that matches the dovecot user account/mailbox. -- Cheers, Phil
