email in exim incoming queue is not getting processed -- Please help

[Hancock, Scott]

Here is some of my mail.log file.

I did the restart at 8:23.  Looks like the queue went down yesterday at
14:21

Gaps below indicate places I snipped the log.


Thanks

Scott


Mar 26 14:21:09 pebbles MailScanner[17287]: New Batch: Found 36 messages
waiting
Mar 26 14:21:09 pebbles MailScanner[17287]: New Batch: Scanning 1
messages, 2078 bytes
Mar 26 14:21:09 pebbles MailScanner[17287]: Virus and Content Scanning:
Starting
Mar 26 14:21:10 pebbles MailScanner[17287]: Uninfected: Delivered 1
messages
Mar 26 14:21:29 pebbles MailScanner[12401]: MailScanner child caught a
SIGHUP
Mar 26 14:21:29 pebbles MailScanner[17681]: MailScanner child caught a
SIGHUP
Mar 26 14:21:29 pebbles MailScanner[13277]: MailScanner child caught a
SIGHUP
Mar 26 14:21:29 pebbles MailScanner[17287]: MailScanner child caught a
SIGHUP
Mar 26 14:21:29 pebbles MailScanner[16329]: MailScanner child caught a
SIGHUP
Mar 26 14:21:29 pebbles MailScanner[15128]: MailScanner child caught a
SIGHUP
Mar 26 14:21:29 pebbles MailScanner[13549]: MailScanner child caught a
SIGHUP
Mar 26 14:21:29 pebbles MailScanner[14608]: MailScanner child caught a
SIGHUP
Mar 26 14:21:29 pebbles MailScanner[761]: MailScanner child caught a
SIGHUP
Mar 26 14:21:29 pebbles MailScanner[26346]: MailScanner child caught a
SIGHUP
Mar 26 15:01:56 pebbles F-Prot autoupdate[28704]: F-Prot successfully
updated.
Mar 26 18:00:08 pebbles F-Prot autoupdate[31632]: F-Prot did not need
updating.
Mar 26 21:00:02 pebbles F-Prot autoupdate[5522]: F-Prot did not need
updating.
Mar 27 00:00:02 pebbles F-Prot autoupdate[14688]: F-Prot did not need
updating.
Mar 27 03:00:04 pebbles F-Prot autoupdate[27398]: F-Prot did not need
updating.
Mar 27 06:00:02 pebbles F-Prot autoupdate[11650]: F-Prot did not need
updating.
Mar 27 08:23:54 pebbles MailScanner[23069]: MailScanner E-Mail Virus
Scanner version 4.13-3 starting...
Mar 27 08:23:54 pebbles MailScanner[23069]: User's home directory /root
is not writable
Mar 27 08:23:56 pebbles MailScanner[23069]: Using locktype = posix
Mar 27 08:23:56 pebbles MailScanner[23069]: Creating hardcoded
struct_flock subroutine for linux (Linux-type)
Mar 27 08:23:56 pebbles MailScanner[23069]: New Batch: Found 2180
messages waiting
Mar 27 08:23:56 pebbles MailScanner[23069]: New Batch: Scanning 100
messages, 4393367 bytes
Mar 27 08:24:04 pebbles MailScanner[23097]: MailScanner E-Mail Virus
Scanner version 4.13-3 starting...
Mar 27 08:24:04 pebbles MailScanner[23097]: User's home directory /root
is not writable
Mar 27 08:24:09 pebbles MailScanner[23097]: Using locktype = posix
Mar 27 08:24:09 pebbles MailScanner[23097]: Creating hardcoded
struct_flock subroutine for linux (Linux-type)
Mar 27 08:24:09 pebbles MailScanner[23097]: New Batch: Found 2181
messages waiting
Mar 27 08:24:09 pebbles MailScanner[23097]: New Batch: Scanning 100
messages, 11392498 bytes
Mar 27 08:24:14 pebbles MailScanner[23150]: MailScanner E-Mail Virus
Scanner version 4.13-3 starting...
Mar 27 08:24:14 pebbles MailScanner[23150]: User's home directory /root
is not writable
Mar 27 08:24:17 pebbles MailScanner[23150]: Using locktype = posix
Mar 27 08:24:17 pebbles MailScanner[23150]: Creating hardcoded
struct_flock subroutine for linux (Linux-type)
Mar 27 08:24:18 pebbles MailScanner[23150]: New Batch: Found 2182
messages waiting
Mar 27 08:24:18 pebbles MailScanner[23150]: New Batch: Scanning 100
messages, 5726911 bytes
Mar 27 08:24:24 pebbles MailScanner[23232]: MailScanner E-Mail Virus
Scanner version 4.13-3 starting...
Mar 27 08:24:24 pebbles MailScanner[23232]: User's home directory /root
is not writable
Mar 27 08:24:27 pebbles MailScanner[23232]: Using locktype = posix
Mar 27 08:24:27 pebbles MailScanner[23232]: Creating hardcoded
struct_flock subroutine for linux (Linux-type)
Mar 27 08:24:28 pebbles MailScanner[23232]: New Batch: Found 2182
messages waiting
Mar 27 08:24:28 pebbles MailScanner[23232]: New Batch: Scanning 100
messages, 4924347 bytes




Mar 27 08:25:36 pebbles MailScanner[23590]: New Batch: Found 2185
messages waiting
Mar 27 08:25:36 pebbles MailScanner[23590]: New Batch: Scanning 100
messages, 1542723 bytes
Mar 27 08:25:38 pebbles MailScanner[23097]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:25:48 pebbles MailScanner[23422]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:26:04 pebbles MailScanner[23150]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:26:07 pebbles MailScanner[23232]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:26:19 pebbles MailScanner[23307]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:26:25 pebbles MailScanner[23590]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:26:47 pebbles MailScanner[23484]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:27:07 pebbles MailScanner[23097]: Spam Checks: Found 13 spam
messages
Mar 27 08:27:23 pebbles MailScanner[23534]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:27:40 pebbles MailScanner[23097]: Virus and Content Scanning:
Starting
Mar 27 08:27:47 pebbles MailScanner[23307]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:27:56 pebbles MailScanner[23097]: Uninfected: Delivered 100
messages
Mar 27 08:28:01 pebbles MailScanner[23097]: New Batch: Found 2093
messages waiting
Mar 27 08:28:01 pebbles MailScanner[23097]: New Batch: Scanning 100
messages, 1443894 bytes
Mar 27 08:28:23 pebbles MailScanner[23150]: Spam Checks: Found 12 spam
messages
Mar 27 08:28:33 pebbles MailScanner[23534]: SpamAssassin timed out and
was killed, consecutive failure 2 of 20
Mar 27 08:28:38 pebbles MailScanner[23365]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:28:44 pebbles MailScanner[23150]: Virus and Content Scanning:
Starting
Mar 27 08:28:51 pebbles MailScanner[23150]:
/var/spool/MailScanner/incoming/23150/18yMjm-00026K-00/UGINE.zip->103290
$
Mar 27 08:28:51 pebbles MailScanner[23150]:
/var/spool/MailScanner/incoming/23150/18yMjm-00026K-00/UGINE.zip->103290
$
Mar 27 08:28:51 pebbles MailScanner[23150]:
/var/spool/MailScanner/incoming/23150/18yMjm-00026K-00/UGINE.zip->103290
$
Mar 27 08:28:51 pebbles MailScanner[23150]:
/var/spool/MailScanner/incoming/23150/18yMjm-00026K-00/UGINE.zip->103290
$
Mar 27 08:28:51 pebbles MailScanner[23150]:
/var/spool/MailScanner/incoming/23150/18yMjm-00026K-00/UGINE.zip->103296
$
Mar 27 08:28:51 pebbles MailScanner[23150]:
/var/spool/MailScanner/incoming/23150/18yMjm-00026K-00/UGINE.zip->103296
$
Mar 27 08:28:57 pebbles MailScanner[23150]: Uninfected: Delivered 100
messages
Mar 27 08:29:01 pebbles MailScanner[23150]: New Batch: Found 1998
messages waiting
Mar 27 08:29:02 pebbles MailScanner[23150]: New Batch: Scanning 100
messages, 5453460 bytes
Mar 27 08:29:26 pebbles MailScanner[23097]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:29:56 pebbles MailScanner[23150]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:30:02 pebbles MailScanner[23307]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:30:04 pebbles MailScanner[23590]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:30:43 pebbles MailScanner[23097]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:30:48 pebbles MailScanner[23590]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:31:07 pebbles MailScanner[23307]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20
Mar 27 08:31:30 pebbles MailScanner[23307]: Spam Checks: Found 16 spam
messages
Mar 27 08:32:05 pebbles MailScanner[23307]: Virus and Content Scanning:
Starting
Mar 27 08:32:17 pebbles MailScanner[23307]:
/var/spool/MailScanner/incoming/23307/18yNkh-0005cs-00/msg-23307-29.txt-
$
Mar 27 08:32:17 pebbles MailScanner[23307]: Virus Scanning: F-Prot found
virus W32/Klez.H at mm
Mar 27 08:32:17 pebbles MailScanner[23307]: Virus Scanning: f-prot found
1 infections
Mar 27 08:32:17 pebbles MailScanner[23307]: Virus Scanning: Found 1
viruses
Mar 27 08:32:19 pebbles MailScanner[23307]: Saved infected
"msg-23307-29.txt" to /var/spool/MailScanner/quarantine/2$
Mar 27 08:32:20 pebbles MailScanner[23150]: SpamAssassin timed out and
was killed, consecutive failure 1 of 20








Mar 27 12:39:59 pebbles MailScanner[737]: Expanding TNEF archive at
/var/spool/MailScanner/incoming/737/18yg2L-0001uC-00/winmail.dat
Mar 27 12:40:00 pebbles MailScanner[737]: Corrupt TNEF winmail.dat that
cannot be analysed in message 18yg2L-0001uC-00
Mar 27 12:40:00 pebbles MailScanner[737]: Virus and Content Scanning:
Starting
Mar 27 12:51:54 pebbles MailScanner[737]: Virus and Content Scanning:
Starting
Mar 27 12:51:54 pebbles MailScanner[737]: Content Checks: Fixed awkward
MIME boundary for Cyrus IMAP server in 18ygDM-0002tP-00
Mar 27 12:51:54 pebbles MailScanner[737]: Uninfected: Delivered 1
messages
Mar 27 12:51:58 pebbles MailScanner[775]: New Batch: Found 1414 messages
waiting
Mar 27 12:58:08 pebbles MailScanner[737]: Virus and Content Scanning:
Starting
Mar 27 12:58:08 pebbles MailScanner[737]: Uninfected: Delivered 1
messages
Mar 27 12:58:11 pebbles MailScanner[775]: SpamAssassin timed out and was
killed, consecutive failure 1 of 20
Mar 27 12:58:16 pebbles MailScanner[737]: New Batch: Found 1421 messages
waiting
Mar 27 12:58:16 pebbles MailScanner[737]: New Batch: Scanning 1
messages, 3036 bytes
 pebbles MailScanner[775]: New Batch: Scanning 1 messages, 1521 bytes
Mar 27 12:32:33 pebbles MailScanner[775]: Virus and Content Scanning:
Starting
Mar 27 12:32:33 pebbles MailScanner[737]: New Batch: Found 2120 messages
waiting
Mar 27 12:32:33 pebbles MailScanner[737]: New Batch: Scanning 1
messages, 3360 bytes
Mar 27 12:32:33 pebbles MailScanner[775]: Uninfected: Delivered 1
messages
Mar 27 12:32:34 pebbles MailScanner[737]: Virus and Content Scanning:
Starting
Mar 27 12:32:35 pebbles MailScanner[737]: Uninfected: Delivered 1
messages
Mar 27 12:32:41 pebbles MailScanner[775]: New Batch: Found 1414 messages
waiting
Mar 27 12:32:41 pebbles MailScanner[775]: New Batch: Scanning 1
messages, 5214 bytes
Mar 27 12:32:42 pebbles MailScanner[775]: Virus and Content Scanning:
Starting
Mar 27 12:32:43 pebbles MailScanner[775]: Uninfected: Delivered 1
messages
Mar 27 12:32:55 pebbles MailScanner[737]: New Batch: Found 2826 messages
waiting
Mar 27 12:32:55 pebbles MailScanner[737]: New Batch: Scanning 1
messages, 1265 bytes
Mar 27 12:32:56 pebbles MailScanner[737]: Virus and Content Scanning:
Starting
Mar 27 12:32:57 pebbles MailScanner[737]: Uninfected: Delivered 1
messages
Mar 27 12:33:58 pebbles MailScanner[775]: New Batch: Found 9180 messages
waiting
Mar 27 12:33:58 pebbles MailScanner[775]: New Batch: Scanning 1
messages, 2093 bytes
Mar 27 12:33:59 pebbles MailScanner[775]: Spam Checks: Found 1 spam
messages
Mar 27 12:33:59 pebbles MailScanner[775]: Virus and Content Scanning:
Starting
Mar 27 12:33:59 pebbles MailScanner[775]: Uninfected: Delivered 1
messages
Mar 27 12:34:01 pebbles MailScanner[775]: New Batch: Found 707 messages
waiting
Mar 27 12:34:01 pebbles MailScanner[775]: New Batch: Scanning 1
messages, 3288 bytes
Mar 27 12:34:02 pebbles MailScanner[775]: Virus and Content Scanning:
Starting
Mar 27 12:34:03 pebbles MailScanner[775]: Uninfected: Delivered 1
messages
Mar 27 12:34:04 pebbles MailScanner[775]: New Batch: Found 707 messages
waiting
Mar 27 12:34:04 pebbles MailScanner[775]: New Batch: Scanning 1
messages, 4155 bytes
Mar 27 12:34:06 pebbles MailScanner[775]: Virus and Content Scanning:
Starting
Mar 27 12:34:06 pebbles MailScanner[775]: Uninfected: Delivered 1
messages
Mar 27 12:35:38 pebbles MailScanner[737]: New Batch: Found 19065
messages waiting
Mar 27 12:35:38 pebbles MailScanner[737]: New Batch: Scanning 1
messages, 7559 bytes
Mar 27 12:35:40 pebbles MailScanner[737]: Virus and Content Scanning:
Starting
Mar 27 12:35:41 pebbles MailScanner[737]: Uninfected: Delivered 1
messages
Mar 27 12:35:45 pebbles MailScanner[775]: New Batch: Found 12004
messages waiting
Mar 27 12:35:45 pebbles MailScanner[775]: New Batch: Scanning 1
messages, 9559 bytes
Mar 27 12:35:47 pebbles MailScanner[775]: Virus and Content Scanning:
Starting
Mar 27 12:35:48 pebbles MailScanner[775]: Uninfected: Delivered 1
messages
Mar 27 12:35:49 pebbles MailScanner[737]: New Batch: Found 1414 messages
waiting
Mar 27 12:35:49 pebbles MailScanner[737]: New Batch: Scanning 1
messages, 3765 bytes
Mar 27 12:35:50 pebbles MailScanner[737]: Virus and Content Scanning:
Starting



Mar 27 12:58:17 pebbles MailScanner[737]: Virus and Content Scanning:
Starting
Mar 27 12:58:18 pebbles MailScanner[737]: Uninfected: Delivered 1
messages
Mar 27 12:58:32 pebbles MailScanner[737]: New Batch: Found 2131 messages
waiting
Mar 27 12:58:32 pebbles MailScanner[737]: New Batch: Scanning 1
messages, 9922 bytes
Mar 27 12:58:57 pebbles MailScanner[775]: SpamAssassin timed out and was
killed, consecutive failure 1 of 20
Mar 27 12:59:02 pebbles MailScanner[737]: SpamAssassin timed out and was
killed, consecutive failure 1 of 20
Mar 27 12:59:15 pebbles MailScanner[737]: Virus and Content Scanning:
Starting
Mar 27 12:59:16 pebbles MailScanner[737]: Uninfected: Delivered 1
messages
Mar 27 12:59:17 pebbles MailScanner[737]: New Batch: Found 716 messages
waiting
Mar 27 12:59:17 pebbles MailScanner[737]: New Batch: Scanning 6
messages, 8703101 bytes
Mar 27 12:59:41 pebbles MailScanner[775]: SpamAssassin timed out and was
killed, consecutive failure 2 of 20
Mar 27 12:59:49 pebbles MailScanner[737]: SpamAssassin timed out and was
killed, consecutive failure 1 of 20
Mar 27 12:59:54 pebbles MailScanner[775]: Virus and Content Scanning:
Starting
Mar 27 12:59:55 pebbles MailScanner[775]: Uninfected: Delivered 4
messages
Mar 27 12:59:56 pebbles MailScanner[775]: New Batch: Found 715 messages
waiting
Mar 27 12:59:57 pebbles MailScanner[775]: New Batch: Scanning 3
messages, 21151 bytes
Mar 27 13:00:27 pebbles MailScanner[775]: SpamAssassin timed out and was
killed, consecutive failure 3 of 20
Mar 27 13:00:35 pebbles MailScanner[737]: SpamAssassin timed out and was
killed, consecutive failure 2 of 20
Mar 27 13:01:10 pebbles MailScanner[775]: SpamAssassin timed out and was
killed, consecutive failure 4 of 20
Mar 27 13:01:19 pebbles MailScanner[737]: SpamAssassin timed out and was
killed, consecutive failure 1 of 20
Mar 27 13:01:23 pebbles MailScanner[775]: Virus and Content Scanning:
Starting
Mar 27 13:01:24 pebbles MailScanner[775]: Uninfected: Delivered 3
messages
Mar 27 13:01:26 pebbles MailScanner[775]: New Batch: Found 720 messages
waiting
 

> -----Original Message-----
> From: Daniel Bird [mailto:dbird at SGHMS.AC.UK]
> Sent: Thursday, March 27, 2003 1:03 PM
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: Re: email in exim incoming queue is not getting processed --
> Please help
> 
> I didn't read the last bit of your mail properly! It sounds MS is
> processing your mail.
> 
> What does your maillog say?  Or your exim log?
> 
> Hancock, Scott wrote:
> 
> >Dan,
> >
> >Do you think this could still be the problem given I'm able to
process
> >new mail?
> >
> >This email passed through the same queue's to and from the list.
> >
> >To me you're suggestion infers the assumption it's not working at
all.
> >
> >What do you think?
> >
> >
> Sorry, I didn't read your mail properly! It sounds MS is processing
your
> mail OK if new mails are delivered.
> 
> What does your maillog say?  MS should give an indication of how many
> messages it sees in your input queue
> 
> Or your exim log? Any unusual events there?
> 
> Dan
> 
> >Scott
> >
> >
> >
> >>-----Original Message-----
> >>From: Daniel Bird [mailto:dbird at SGHMS.AC.UK]
> >>Sent: Thursday, March 27, 2003 12:17 PM
> >>To: MAILSCANNER at JISCMAIL.AC.UK
> >>Subject: Re: email in exim incoming queue is not getting processed
--
> >>Please help
> >>
> >>Scott,
> >>I had a similar problem with exim and finding it's input and ouput
> >>
> >>
> >queues.
> >
> >
> >>For some reason my version (4.12, but also when I was using 3.x -
> >>probably a configure option;-) decided if I told it to use
> >>
> >>/var/spool/exim/input
> >>
> >>it actually looked in /var/spool/exim/input/input
> >>and likewise for /var/spool/exim/output
> >>
> >>
> >(/var/spool/exim/output/input).
> >
> >
> >>ie, always added 'input' to the dir structure
> >>
> >>To get 'round this I have :
> >>
> >>in exim.conf.out
> >>spool_directory = /var/spool/exim/outgoing
> >>
> >>and in MailScanner.conf
> >>Incoming Queue Dir = /var/spool/exim/input
> >>Outgoing Queue Dir = /var/spool/exim/outgoing/input
> >>
> >>Works for me!
> >>
> >>Regards
> >>Dan
> >>
> >>Hancock, Scott wrote:
> >>
> >>
> >>
> >>>Greetings all,
> >>>
> >>>This is a restate of a previous help request.
> >>>
> >>>Exim incoming has written a pile of messages to
> >>>/var/spool/exim/incoming/input.
> >>>
> >>>For some reason mailscanner is not acting on these messages.
> >>>
> >>>Any guidance on how to troubleshoot or information on under what
> >>>conditions mailscanner would not find or accept these files would
be
> >>>greatly appreciated.
> >>>
> >>>Debian sarge
> >>>Exim 3.36
> >>>MS 4.13
> >>>Sa 2.44
> >>>
> >>>All new incoming mails are scanned and delivered.
> >>>
> >>>exim -bp  shows the mail in the incoming directory without any
> >>>
> >>>
> >errors.
> >
> >
> >>>The queue originally had 1500 unscanned emails a Mainscanner
restart
> >>>delivered half of these but I still have about 700 waiting for
> >>>
> >>>
> >deliver.
> >
> >
> >>>I'll gladly post any conf files.
> >>>
> >>>Please help.
> >>>
> >>>Scott Hancock
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>--
> >>This message has been scanned for viruses and
> >>dangerous content by MailScanner, and is
> >>believed to be clean.
> >>Mailscanner thanks transtec Computers for their support.
> >>
> >>
> >
> >
> >
> 
> 
> 
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> Mailscanner thanks transtec Computers for their support.