> You can use a virtual user table, but you will have to split your > "deliver_local" table. As Uwe suggested, I would use lmtp for that: > > action "inbox" lmtp "/var/run/dovecot/lmtp" rcpt-to virtual <vusers> > > In that case, vusers is defined here: > > table vusers file:/etc/smtpd/vusers > > And its content: > > postmaster [email protected] > abuse [email protected] > root [email protected] > contact [email protected] > [email protected] vmail > [email protected] vmail > [email protected] [email protected] > > And so on…
Thank you both Uwe and Archange for the pointer to lmtp, I was not familiar with that! I enabled lmtp according to what I read online by adding lmtp to the protocols Regarding the example contents of the vusers table you suggested Archange, the first 4 lines would only ever be active for local mail, correct? Would this eg. send the daily output and insecurity output to [email protected]? Regarding the 5th and 6th line of your example table, wouldn't that just deliver to the Maildir of the user vmail? Would there ever be a case where I would want this? Just asking to confirm in case I do not understand. :) Lastly, if I map [email protected] to [email protected], would it end up in the Maildir of [email protected] in the folder "special"? Or do I need to do any extra configuration on the side of dovecot to make this happen? > > ############################################################## > > allow_username_mismatch = true; > > > > domain { > > firstdomain.tld { > > path = "/etc/mail/dkim/firstdomain.tld.key"; > > selector = "blah"; > > } > > } > > ############################################################## > > > > Will it work automatically by simply entering eg. > > 'seconddomain.tld > > {...}' with its respective keyfile and selector? > > Yes. And if you use sensible file names like me, you can even do > this: > > path = "/etc/mail/dkim/$domain.$selector.key"; > > Regards, > Archange I am glad to hear that this will work! Since I assume that the users will now have to authenticate with their full [email protected], can I remove 'allow_username_mismatch = true;' from the config? Iirc it was necessary before because users would just authenticate with their username. Thank you for your patience with my many questions! Best, Unicorn
