Error message starting/restarting MailScanner?

[Randal, Phil]

mailscanner-bounces at lists.mailscanner.info wrote:
> Drew Marshall wrote:
>> On 29 Mar 2007, at 16:39, Dhawal Doshy wrote:
>> 
>>> Paul Hutchings wrote:
>>>> I'm not sure entirely what you mean, but from a quick google
>>>> /var/spoolpostfix/incoming is empty.
>>>> I'm running Postfix 2.3.3 on OpenSuse (the default rpm).
>>>> MailScanner does seem to be working and processing mail (this is
>>>> just a test box). ls -lh /var/spool/MailScanner/incoming
>>>> drwx------ 2 postfix postfix 4.0K Mar 29 14:08 11431
>>>> drwx------ 2 postfix postfix 4.0K Mar 29 14:08 11475
>>>> drwx------ 2 postfix postfix 4.0K Mar 29 14:09 11513
>>>> drwx------ 2 postfix postfix 4.0K Mar 29 14:08 11547
>>>> drwx------ 2 postfix postfix 4.0K Mar 29 14:24 11581
>>>> -rw------- 1 postfix postfix 7.0K Mar 29 14:09
>>>> SpamAssassin.cache.db 
>>> 
> ^^^^^^^^^^^^^^^^^^^^^
>>> 
>>> This file is not supposed to exist here, rather move it
>>> /var/spool/MailScanner/SpamAssassin.cache.db using the "SpamAssassin
>>> Cache Database File" configuration option in MailScanner.conf
>> 
>> Mine's there too. I never noticed or worried about it before :-o
>> 
>> Drew
> 
> Well this link mentions
> /var/spool/MailScanner/incoming/SpamAssassin.cache.db as the default
> value as well.. but why have non-queue/mail files in the MS workdir?
> http://mailscanner.info/MailScanner.conf.index.html#SpamAssass
> in%20Cache%20Database%20File

It's a good place for it.

If you mount /var/spool/MailScanner/incoming using tmpfs, you'll get
performance improvements.  And it doesn't matter if the SA cache DB is
trashed on reboot, another will be built on the fly.

Thar's method in yonder madness.

Phil

-- 
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK