Nick:
> This isn't causing me any problem (that I can tell) so I ask out of
> curiosity, about postfix 3.4.7 on debian stable...
>
> My main.cf sets local delivery to go to dovecot,
>
> local_transport = lmtp:unix:private/dovecot-lmtp
>
> In obedience to LOCAL_RECIPIENT_README it also sets
> local_recipient_maps to "specify a database that lists all the known
> user names or addresses",
>
> local_recipient_maps = $real_recipients, $virtual_alias_maps
>
> where 'real_recipients' are the local unix accounts that can receive
> mail. These settings are working, postfix delivers mail into dovecot
> whether addressed to real account names or to virtual aliases.
>
> If the recipient is bogus, postfix rejects the mail like so,
>
> 550 5.1.1 <bogus-recipi...@acrasis.net>: Recipient address
> rejected: undeliverable address: host
> mail.acrasis.net[private/dovecot-lmtp] said: 550 5.1.1
> <bogus-recipi...@acrasis.net> User doesn't exist:
> bogus-recipi...@acrasis.net (in reply to RCPT TO command)
You have additional configuration beyond what you described above,
namely, something that invokes reject_unverified_recipient.
> This is dovecot, not postfix, giving the verdict on the validity of
> 'bogus-recipient', yes? If postfix has "a database that lists all the
> known user names or addresses", why does postfix consult dovecot?
Because you configured Postfix to invoke reject_unverified_recipient.
As always, an examination of "postconf -n" output can clarify
surprises.
Wietse
