Milter-greylist

While most of my scanners have 512mb of ram, the main scanner has a 
gig of ram and 'free' reveals using 946megs, 85 megs available, 445 
megs in buffers/cache so its operating just fine.  a PS -aux looks 
good in terms of the # of processes and % of memory.  I can't see 
this as being a resource issue given the above. Thanks for your 
comments!!! We'll get this figured out eventually!

--- In milter-greylist@yahoogroups.com, "hwdahm" <hwdde@...> wrote:
>
> --- In milter-greylist@yahoogroups.com, manu@ wrote:
> >
> > Brian J. Lewis <brianlewis@> wrote:
> > 
> > > Maybe this is a clue?  Check this out, these are weird errors, 
its 
> > > greylisting but its also erroring same time.  I can email you a 
GZIP 
> > > of the log that has all this weird stuff in it if it will 
help.  
> > > Maybe a corrupt greylist.db? Or just too large? (21 megs)
> > 
> > The "timeout before data read" simply means the milter stopped
> > responding, probably because it crashed.
> > 
> > There are two usual suspects
> > 1) DNS query with a thread-unsafe resolver (if you use DNSRBL or 
SPF)
> > 2) system limit (ulimit) exhausted.
> > 
> > -- 
> > Emmanuel Dreyfus
> > http://hcpnet.free.fr/pubz
> > manu@
> >
> 
> I had the same problems, but I don´t use SPF or DNSRBL.
> I used ./configure without arguments (I think --with-libbind is only
> necessary if spf or dnsrbl, am I right?).
> 
> So - imho - there is only one "usual suspect" left, i.e. system 
limit
> exhausted, although an ulimit -a shows an "unlimited" system.
> Are there any other system restrictions to look at? Are there any
> recommended sizes of RAM or virt.memory?
> 
> Deactivating mx-syncing made my systems more reliable.
> 
> Regards - and thank you all for your work and assistance
> Hans
>