queue.in clog

[Julian Field]

In which case you might just have to not use the auto-whitelist.

At 22:08 18/02/2004, you wrote:
>well, thanks to the debug from below, its looking like its not able to use
>the spamassassin autowhite list, its saying its there, but unable to open
>file.  In looking at the permissions, it was set to 600 so changed to 777
>and no change, same error. Backed up the files that were there, removed
>all, including the auto-whitelist and restarted mailscanner, it created the
>auto-whitelist and remade the users_pref. Restarted mailscanner in debug
>and it goes on through now, but its still queuing incoming mail its
>apparently using some kind of .lock file and locking the autowhitelist,
>when the next scanner runs, its not allowing the file to be read, so its
>queuing and basically halting the send part.
>
>
>Feb 18 16:00:58 web2 MailScanner[14564]: Using locktype = flock
>Feb 18 16:00:59 web2 MailScanner[14564]: New Batch: Found 453 messages waiting
>Feb 18 16:00:59 web2 MailScanner[14564]: New Batch: Forwarding 9 unscanned
>messages, 11695 bytes
>Feb 18 16:00:59 web2 MailScanner[14564]: New Batch: Scanning 200 messages,
>6212350 bytes
>
>next time mailscanner runs
>
>Feb 18 16:01:19 web2 MailScanner[14946]: New Batch: Found 456 messages waiting
>Feb 18 16:01:19 web2 MailScanner[14946]: New Batch: Forwarding 9 unscanned
>messages, 11695 bytes
>Feb 18 16:01:19 web2 MailScanner[14946]: New Batch: Scanning 200 messages,
>6212350 bytes
>
>it does this and the queue just grows and nothing seems to send except a
>small few.
>
>
>thanks
>Michael
>
>
>At 02:55 PM 2/18/2004, you wrote:
>
>>Run through a debug, (change some a couple of config options in
>>MailScanner.conf, Debug=yes, Spamassassin Debug = Yes). Stop
>>MailScanner, and restart it, then it will run through a batch in a
>>verbose mode, by observing it, you can see where the hang up is. Usually
>>it's one of the spamassassin test (Razor2, DCC, RBL checks), which you
>>can turn off/on in the spam_prefs for MailScanner, or reduce the
>>timeouts or whatever, after you determine which one is delaying your
>>queue.in processing.
>>
>>Regards
>>MIKE
>>
>> > Sorry if this is an old question...
>> >
>> > Im running MailScanner v4.25.14
>> > Sophos Version 3.78
>> > Redhat 7.3
>> >
>> >
>> > im seeing tons of mail getting into the scanner queue, but im seeing very
>> > little going out. The queue.in is constanly growing (right now shows
>> approx
>> > 2K messages waiting to scan). Right now there is approx a 40 min delay
>> > between receiving and actually sending the message. Any help would be much
>> > appreciated in speeding this up.This just started a few days ago. We
>> have 8
>> > children running, the delay is about 20 min from each "MailScanner"
>> log. It
>> > seems to scan about 50 messages wait 20-25 min then scans another  50
>> > messages. We've increased the children, the file scan size, etc,etc.
>> >
>> >
>> > Thanks in Advance.
>> > Michael
>> >
>> >
>> > --
>> > Outgoing mail is certified Virus Free.
>> > Checked by AVG Anti-Virus (http://www.grisoft.com).
>> > Version: 7.0.211 / Virus Database: 261.9.6 - Release Date: 2/18/2004
>> >
>>
>>--
>>This message has been scanned for viruses and
>>dangerous content by our MailScanner, and is
>>believed to be clean.
>>
>>
>>
>>
>>--
>>Incoming mail is certified Virus Free.
>>Checked by AVG Anti-Virus (http://www.grisoft.com).
>>Version: 7.0.211 / Virus Database: 261.9.6 - Release Date: 2/18/2004
>
>
>--
>Outgoing mail is certified Virus Free.
>Checked by AVG Anti-Virus (http://www.grisoft.com).
>Version: 7.0.211 / Virus Database: 261.9.6 - Release Date: 2/18/2004

--
Julian Field
www.MailScanner.info
MailScanner thanks transtec Computers for their support

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654