I said concurrency, meaning only the last line is unnecessary. You MUST
use maildrop_destination_recipient_limit, or you will have problems,
mostly with messages going to multiple recipients.
Postfix 2.1.5:
'postconf -d maildrop_destination_recipient_limit'
postconf: warning: maildrop_destination_recipient_limit: unknown
parameter
Hmmm ...
'postconf -d | grep recipient_limit'
Blah,
blah,
local_destination_recipient_limit = 1
Tony, correct me if I'm wrong, but aren't you a regular on the Postfix
mailing list? So I'm surprised that you are not aware that any
transport you define in master.cf gets its own
*_destination_recipient_limit as well as several other similar config
parameters.
That is, your post is mistaken and will only serve to confuse maildrop
new-comers: if you route mail from Postfix to Maildrop as a transport,
you *MUST* define this:
maildrop_destination_recipient_limit = 1
When used as a generic delivery transport, Postfix does not treat it as
"local" and will in fact deliver messages for more than one recipient
incorrectly without this parameter. If you use Maildrop as a
replacement mailbox_command, only then is
local_destination_recipient_limit probably in order.
Do you know something that I don't?