As per:
http://www.postfix.org/SMTPD_POLICY_README.html
You might try something like:
smtpd_policy_service_timeout = 240s
127.0.0.1:2552_time_limit = 3730
smtpd_policy_service_max_idle = 900s
I'm not all that familiar with exactly what these setting affect but
it may help prevent maRBL
Heute (19.01.2007/17:17 Uhr) schrieb Gary V,
Gary wrote:
Hi Gary,
I had looked at that as a stop-gap measure until I figured out what
was going wrong with maRBL. Unfortunately, maRBL would come back up
and then die almost immediately again. I spoke, briefly, with Ian
(the author of
Gary Buckmaster wrote the following on 19/01/2007 15:57:
I had looked at that as a stop-gap measure until I figured out what
was going wrong with maRBL. Unfortunately, maRBL would come back up
and then die almost immediately again. I spoke, briefly, with Ian
(the author of maRBL) and Mark
Jim wrote:
What do you think? Work the patched policyd-weigt with Cami`s
Policy Daemon? http://policyd.sourceforge.net
DUNNO, I have never tried policyd but I have heard only good things
when people talk about it.
Gary V
Heute (19.01.2007/19:44 Uhr) schrieb Gary V,
Jim wrote:
What do you think? Work the patched policyd-weigt with Cami`s
Policy Daemon? http://policyd.sourceforge.net
DUNNO, I have never tried policyd but I have heard only good things
when people talk about it.
Gary V
yes, and have many
I wonder if anyone has seen this issue coming up. It _just_ started
happening on Friday and I've been hacking around with it over the
weekend trying to figure out what happened. I have maRBL running with
amavisd-new on a FreeBSD server. Upon startup, you get the usual
messages:
Jan 16 09:25:49
