On Wed, 30 Apr 2008, Jesse Norell wrote:
Also here, you can add a second hash containing local users.
Except that's not what I want - I want to fall back on the default
behaviour of checking users from /etc/passwd if the
local_recipient_maps
fails. Is there a way to do that?
That is what you want. You want a local_recipient_maps entry that
checks both your dbmail database (which you apparently have working) and
also checks the password file. The default value is:
$ postconf -d local_recipient_maps
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
So just add in your dbmail value to the default behavior, and you should
be set:
local_recipient_maps = proxy:unix:passwd.byname $alias_maps \
mysql:/etc/postfix/sql-recipients.cf
OK, that seems to work. However, now I'm not getting any deliveries to
dbmail. dbmail user mail bounces after being accepted by postfix for
delivery (so the user retrieval list works for checking purposes). If
there is a user by the same name localy, that will receive the mail
instead of the virtual dbmail user, but a dbmail-only account doesn't seem
to. Instead the mail bounces back as undeliverable with the message that
the user doesn't exist.
I thought specifying <mytestdomain> in /etc/postfix/transport and pointing
that to dbmail's lmtp would suffice. Do I need to change something else as
well, like local_transport?
I tried talking directly to dbmail lmtp on port 24 and that correctly
accepts mail for existing users and rejects for non-existant users. So the
problem must be in the postfix configuration...
Gordan
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
