Hi,
We are planning to add maildrop to get some filter functionality, i.e.
reformail. The server is on production, and mail delivering is
configured now with virtual as virtual_transport and courier as MDA (if
helps), and maildrops is already installed from distro repositories.
We plan to use already defined MX backup while we do those modifications
and tests.
So I think that I need to:
* replicate all virtual_* config to maildrop_*:
main.cf contains next defined variables:
virtual_alias_maps, virtual_gid_maps, virtual_mailbox_base,
virtual_mailbox_domains, virtual_mailbox_maps, virtual_minimum_uid,
virtual_transport, virtual_uid_maps, virtual_create_maildirsize,
virtual_mailbox_limit, virtual_maildir_extended,
virtual_mailbox_limit_maps, virtual_mailbox_limit_override,
virtual_maildir_limit_message, virtual_overquota_bounce
Most of them are proxy:mysql files. If anyone asks for a possible
variable for problems i may post it.
* change virtual_transport to maildrop:
virtual_transport = virtual -> virtual_transport = maildrop, isn't?
* ensure maildrop interface works as expected:
virtual is not modified:
virtual unix - n n - - virtual
and maildrop has this:
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient}
and should add: maildrop_destination_recipient_limit=1
Could be any problems on delivery interface? Would main.cf variables
work as intended?
I expect that there is no problems and (as readme says) performance
scould be improved (or almost load not incresed).
Thanks.
--
Joan.
