Found nn messages in the processing-messages database

[Julian Field]

On 01/05/2009 10:09, Nigel Kendrick wrote:
> Hi,
>
> I'm coming in a bit late here and am trying to catch up on this thread. I
> have had a good read but would appreciate some advice
> on the following:
>
> On the mail server that ground to a halt on me (frequently) about a week
> ago, it's currently showing 384 messages in the processing queue, stretching
> back
> to 20th April. Here's the top of the list:
>
> Number of messages: 384
> Tries   Message Next Try At
> =====   ======= ===========
> 1       762C72F0039.D1D4C       Fri May  1 05:12:13 2009
> 1       762C72F0039.9458D       Fri May  1 05:10:57 2009
> 1       762C72F0039.217F1       Fri May  1 05:09:31 2009
> 1       CA1472F003B.F132E       Fri May  1 04:17:22 2009
> 1       8511F2F0038.17722       Fri May  1 04:13:59 2009
> 1       847282F003A.0C804       Fri May  1 04:12:34 2009
> 1       25C4167800F.C6CF0       Thu Apr 30 19:21:03 2009
> 1       25C4167800F.AE019       Thu Apr 30 19:19:56 2009
> 1       25C4167800F.3120B       Thu Apr 30 19:17:54 2009
> 1       04BE62F003A.1F69E       Thu Apr 30 13:20:46 2009
> 1       02D6867800F.64CA4       Thu Apr 30 13:18:50 2009
> 1       02D6867800F.3EF79       Thu Apr 30 13:18:05 2009
> 1       8628B67800F.1D156       Wed Apr 29 15:23:21 2009
> 1       D694C678019.51D4F       Wed Apr 29 15:22:41 2009
> 1       B49BF678017.BC390       Wed Apr 29 15:22:27 2009
> 1       8628B67800F.5F79F       Wed Apr 29 15:20:27 2009
> 1       3DDF567800F.D497F       Wed Apr 29 13:41:58 2009
> 1       29634678033.E00D4       Wed Apr 29 13:39:45 2009
> 1       E1CB367801A.10092       Wed Apr 29 13:39:16 2009
> 1       AAFCC67802C.D024A       Wed Apr 29 13:38:52 2009
> 1       0B532678019.78254       Wed Apr 29 13:37:36 2009
> 1       6244F67800F.34B35       Wed Apr 29 11:18:31 2009
> 1       6244F67800F.0537D       Wed Apr 29 11:18:19 2009
> 1       6244F67800F.A73C3       Wed Apr 29 11:17:11 2009
>
> Are these entries now considered 'spurious' and do I need to take any
> action, wait for the current MailScanner beta release to go stable or even
> install it now?
It already is a stable release. I just haven't had time to announce it 
yet, sorry, that's tomorrow's job.
Install the stable release, stop MailScanner, destroy 
/var/spool/MailScanner/incoming/*db and fire it up again.

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.