Now that I have switched to virtual domains, how can I continue to have postfix deliver the mail directly to dovecot via lmtp? It seems that postfix is try to save the mail to disk itself rather than handing it off to dovecot.
Below are the lines I was using before to deliver mail to dovecot, but it doesn’t seem to work now that I am using virtual domains. mailbox_transport = lmtp:unix:private/dovecot-lmtp alias_maps = hash:/etc/aliases proxy:pgsql:/etc/postfix/pgsql-aliases.cf local_recipient_maps = proxy:pgsql:/etc/postfix/pgsql-boxes.cf $alias_maps Any tips? What am I missing? Thanks! Austin Witmer > On Jun 18, 2022, at 10:14 PM, Viktor Dukhovni <postfix-us...@dukhovni.org> > wrote: > > On Sat, Jun 18, 2022 at 09:27:52PM -0600, Austin Witmer wrote: > >> Using >> https://wiki.alpinelinux.org/wiki/Setting_up_postfix_with_virtual_domains >> <https://wiki.alpinelinux.org/wiki/Setting_up_postfix_with_virtual_domains> >> as a bit of a tutorial, I got one of my domains switched over to being >> a virtual domain and was able to send and receive email for a user on >> the domain I transferred. >> >> Do I have to have the users setup now both in my postgresql database >> and also in the /etc/postfix/virtual_mailbox_maps file? That would >> seem redundant. > > The "virtual_mailbox_maps" table can query postgresql (typically as > > main.cf: > pgsql = proxy:pgsql:${config_directory}/ > virtual_mailbox_maps = ${pgsql}vmbox.cf > > vmbox.cf: > # See http://www.postfix.org/pgsql_table.5.html > # If delivery is via virtual(8), then the RHS must be a > # suitable path (typically maildir directory) > # If delivery is via LMTP or dovecot LDA, then RHS can > # be any non-empty token. > ... > >> Is there a way to use virtual domains and have all the user info >> stored in my postgresql database? > > Of course. > > -- > Viktor.
