Re: Spamassassin Child is just dying without advise...

2013-12-01 Thread Gino Semseo
Hello!!! loadplugin Mail::SpamAssassin::Plugin::ResourceLimits resource_limit_mem 268435456 Why do you limit the available memory to 256 MB? Do you still see spamd children dieing with that plugin and limit commented out? I am going to test, a) incrementing to 1024MB, b) disabling this

Re: Spamassassin Child is just dying without advise...

2013-12-01 Thread Martin Gregorie
On Sun, 2013-12-01 at 12:56 +0100, Gino Semseo wrote: That's huge and rather excessive for whitelisting configuration. Are there really 100k+ options, or does that include empty lines and comments? No... each line, is a mail address.. What conf does it contain: whitelist_*

Re: uribl problem

2013-12-01 Thread Nick Edwards
Hi Karsten, On 12/1/13, Karsten Bräckelmann guent...@rudersport.de wrote: On Fri, 2013-11-29 at 13:30 +1000, Nick Edwards wrote: Hi, have a problem with our internal uribl urirhsblINT_URI uri.int.lan. A bodyINT_URI eval:check_uridnsbl('INT_URI') describeINT_URI

Re: uribl problem

2013-12-01 Thread Karsten Bräckelmann
On Mon, 2013-12-02 at 07:58 +1000, Nick Edwards wrote: On 12/1/13, Karsten Bräckelmann guent...@rudersport.de wrote: The general SA method of verifying which domains are queried for, is to have a look at the debug output. In your case, you can also check your local DNSBL's logs.

Re: Spamassassin Child is just dying without advise...

2013-12-01 Thread Karsten Bräckelmann
On Fri, 2013-11-29 at 23:13 +0100, Gino Semseo wrote: 2013-11-29 20:29:01 1VmTkL-0002F8-5Q spam acl condition: cannot parse spamd output Nov 29 16:00:55 hyperserver spamd[38925]: prefork: ordered 38942 to accept Nov 29 16:00:55 hyperserver spamd[38925]: prefork: sysread(7) not ready, wait