On Thu, June 28, 2012 13:41, Noel Jones wrote: > cyrus_destination_recipient_limit=1 means deliver a maximum of one > recipient to each "cyrus" transport defined in master.cf, which > pipes to the cyrus "deliver" program; there may be multiple > processes running in parallel. > > Apparently some versions of cyrus "deliver" program are unable to > properly handle more than one recipient at a time. I don't know > which versions this limitation may apply to. > > It appears to me that lmtp, rather than pipe, is the preferred > transport for modern cyrus installations, so this is likely an > ancient example still hanging around in master.cf. Treat this entry > as a sample rather than as "this is how you do it".
That is how I was treating it, up to the point that it was suggested cyrus deliver was necessary to handle delivery to virtual_mailboxes. > > The choice of lmtp vs. pipe as a delivery transport has no direct > effect on the choice of a local domain vs. a virtual mailbox domain. > > >> Further, under the virtual_mailbox_domains scenario, should both the >> mailbox_transport and the virtual_transport be set to cyrus? If so, >> what is the relationship between local_destination_recipient_limit = >> 300 and cyrus_destination_recipient_limit=1? > > No, use one or the other depending on the domain address class. To clarify this for me. Given that I am constrained to use cyrus-imap for final delivery to the users' mailbox, if lmtp is the desired value for mailbox_transport when using cyrus then does this extend to virtual_transport as well? In other words, if using cryus-imapd should virtual_transport = lmtp as well? If not then why not? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3
