I want to confirm something I came across while playing with a test
Postfix/Dovecot configuration.  First, I am using Postfix 2.9.1
installed on a fully updated Debian stable (the backports version is
2.9.1-2~bpo60+1).

I need to reject recipient-extension addresses not specifically allowed
by a .forward-extension file in the user's home directory during the
SMTP conversation, but allow any recipient-extension for which the user
has defined a .forward-extension file.  As far as I can tell, that is
not possible (note, my experience with Postfix is *very* limited, thus
this email) using any of the default alias maps, because the addresses
fall back to the recipient.

I have tried only using the "$alias_maps" by assigning
"local_recipient_maps = $alias_maps", then placing the user name in the
/etc/aliases file as "dave: dave".  I have tried using the
virtual_alias_maps and placing only the following lines in
/etc/postfix/virtual.

#v+
d...@caterva.org        dave
dave-t...@caterva.org   dave-test
#v-

In both cases when sending email to dave-anothert...@caterva.org Postfix
determined that dave-test existed because Postfix defaulted to the user
dave because the user existed.  Note that I have been able to get
Postfix to do everything else I wanted: Local, virtual, and internet
delivery all work well.

So, my two questions.

1) Am I correct that blocking recipient addresses which consist of an
existing user with an extension not defined by that user (in a
.forward-extension file) is not possible using Postfix using just the
configuration options available in main.cf?

2) Has anyone done something similar to what I want with a milter/plugin
which my search-fu and documentation reading has not uncovered?

If more information is needed please let me know and I will happily
provide.

Regards,
-- 
dave [ please don't CC me ]

Attachment: pgpExGYX2M4Np.pgp
Description: PGP signature

Reply via email to