Yeah, I just did that too. Wonder why the timeouts were not working. Oh
well, at least I now have better spam filtering than "-L". Thanks!

-Steve

-------------------------------------------------------------------------
Stephen Bader                  JORSM Internet, Regional Internet Services
Systems Administrator          7 Area Codes in Chicagoland and NW Indiana
[EMAIL PROTECTED]               100Mbps+ Connectivity, 56K-DS3, V.90, ISDN
(219) 322-2180                 Quality Service, Affordable Prices
http://www.jorsm.com           Serving Gov, Biz, Indivds Since 1995
-------------------------------------------------------------------------

On 10 Oct 2002, Ken Causey wrote:

> I found that razor is the culprit.  It's blocking for very long periods
> of time trying to access 194.109.217.74 which appears to be razor
> related.  I disabled RAZOR with
>
> score RAZOR_CHECK     0
>
> and now things are flying along smoothly.
>
> Ken
>
> On Thu, 2002-10-10 at 21:46, Stephen Bader wrote:
> > I just ran spamd with the "-L" flag so it will do local checks only. I
> > know this isn't the best, but it has solved my problem for now. Maybe
> > someone has some answers to what is wrong, but for now, this will have to
> > do.
> >
> > -Steve
> >
> > -------------------------------------------------------------------------
> > Stephen Bader                  JORSM Internet, Regional Internet Services
> > Systems Administrator          7 Area Codes in Chicagoland and NW Indiana
> > [EMAIL PROTECTED]               100Mbps+ Connectivity, 56K-DS3, V.90, ISDN
> > (219) 322-2180                 Quality Service, Affordable Prices
> > http://www.jorsm.com           Serving Gov, Biz, Indivds Since 1995
> > -------------------------------------------------------------------------
> >
> > On 10 Oct 2002, Ken Causey wrote:
> >
> > > spamassassin is very SLOW tonight, so slow I can't get any response to
> > > figure out what is making it slow.  In my config I have:
> > >
> > > rbl_timeout     5
> > > razor_timeout   2
> > > timelog_path    /tmp/salogs
> > >
> > > I'm not using pyzor and I don't see any other timeouts to mess with that
> > > would make a significant difference.  It's stalling for many minutes
> > > (I'm at 8 right now and still waiting) so I can't even get any logs to
> > > see what's taking so long.  Anyone have any ideas?  This is killing my
> > > server.
> > >
> > > Ken Causey
> > >
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > Spamassassin-talk mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
> > >
> >
>
>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to