Yikes! Thanks for the heads up...
You can add my vote to get this patched...
Chris Masters wrote:
OK, oops. I'm relying to my own mail here.
It seems that the function get_user_mysql in mdmysql.c
only ever returns NULL if any problems are
encountered.
Would it not be better to return an exit code if there
is a:
1) database connection error - so that main.C can
return EX_TEMPFAIL
2) general database error - that main.C can return
EX_TEMPFAIL
3) connot find user error - so that main.C can return
EX_NOUSER
If there is any uncertainty about the database (ldap
or mysql) being up and correct tempfail rather than
bounce!
Anyone?
Do I feel a patch coming on?
--- Chris Masters <roti...@yahoo.com> wrote:
Hi All,
I use maildrop to deliver mails to virtual users
located in MySQL.(from Postfix).
If maildrop cannot connect to the database it
returns
"unknown user" instead of a 451 (tempfail) error
code:
Oct 14 14:35:48 lon-quar-01 postfix/pipe[2044]: [ID
197553 mail.info] A79E2D7388:
to=<roti...@wardrobes.co.uk>, relay=maildrop,
delay=55, status=bounced (user unknown. Command
output: Could not connect to database 192.168.0.30
Could not connect to database 192.168.0.31 Invalid
user specified. )
Has anyone got a fix?
Is this a known problem?
Thanks, Chris