Hi David,
I just found why queueing never really worked here on my side. We used a modified 'examples/init-script.in' as startup script and in this script, ALLOW_NEW_CONNECTIONS_TO_QUEUE is not defined in the header. If ALLOW_NEW_CONNECTIONS_TO_QUEUE=yes is not set, queueing only works up to 5-10 queued messages, afterwords the filter is tempfailing. I thought long time that this is some mimedefang bug and I never gave it significant importance. But since the spam amount is constantly growing, queueing is more and more important for us. So can you please add a comment to examples/init-script.in and maybe set ALLOW_NEW_CONNECTIONS_TO_QUEUE=no in the header too ? This way new users can change that value and don't need to stick with the sourcecode to find out what ALLOW_NEW_CONNECTIONS_TO_QUEUE really means :-) Martin Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> ------------------------------------------------------------------ ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: <finger -l [EMAIL PROTECTED]> PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E ------------------------------------------------------------------ _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
