From: Sven Michels (no email)
Date: Fri Feb 01 2002 - 05:19:02 EST
Hi list,
most of you heared from the problem with the recent
postfix releases and Berkley DB. I've a maschine with
postfix 1.1.2 and the same problem... so i figured out
what happened.
Problem was:
postfix/smtpd[29132]: fatal: error reading /etc/postfix/sender_access.db:
Invalid argument
that happens _sometimes_ and that was the mysterial ;)
after a day, we had some logs about the problem. It seems
that the problem only exist, if MAIL FROM was <>. I remember
that a new value was added recently to the main.cf:
smtpd_null_access_lookup_key
per default, smtpd_null_access_lookup_key is not set
(postconf -d smtpd_null_access_lookup_key). After setting
it to <> and reloaded postfix: problem was gone!
So we started smtpd with -v:
BEFORE:
Feb 1 09:57:16 firewall postfix/smtpd[19755]: generic_checks:
name=check_sender_access
Feb 1 09:57:16 firewall postfix/smtpd[19755]: check_access:
Feb 1 09:57:16 firewall postfix/smtpd[19755]: fatal: error reading
/etc/postfix/sender_access.db: Invalid argument
Feb 1 09:57:17 firewall postfix/cleanup[19781]: warning: premature end-of-input
from cleanup socket while reading input attribute name
so smtpd dies...
AFTER:
Feb 1 10:00:33 firewall postfix/smtpd[19883]: check_access: <>
Feb 1 10:00:33 firewall postfix/smtpd[19883]: generic_checks:
name=check_sender_access status=0
Feb 1 10:00:33 firewall postfix/smtpd[19883]: generic_checks:
name=permit_mynetworks
...
and so on...
as you can see, now it checks for <> instead of nothing.
and all works fine.
so, it seems that here is the bug hidden :)
now, someone with more knowledge in coding should take a look
into the sourcecode and find it ;)
i hope, that helps you all and someone can fix the problem :)
--
intraDAT AG http://www.intradat.com
Wilhelm-Leuschner-Strasse 7 Tel: +49 69-25629-0
D - 60329 Frankfurt am Main Fax: +49 69-25629-256
Junk mail is war. RFCs do not apply.
-
To unsubscribe, send mail to with content
(not subject): unsubscribe postfix-users
|
|
|