Re: [exim] Bug#360696: Failed to get write lock for/var/spoo…

Top Page
Delete this message
Reply to this message
Author: Matthew Byng-Maddick
Date:  
To: exim-users
CC: 360696-submitter, 360696-quiet
New-Topics: Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for/var/spool/exim4/db/retry.lockfile:timedout
Subject: Re: [exim] Bug#360696: Failed to get write lock for/var/spool/exim4/db/retry.lockfile:timed out
On Wed, Apr 26, 2006 at 02:03:39PM +0200, Michel Meyers wrote:
> Matthew Byng-Maddick wrote:
>> On Wed, Apr 26, 2006 at 09:39:15AM +0100, Philip Hazel wrote:
>>> Ah! I don't know much about mailscanner. Am I right in thinking it looks
>>> at Exim's spool files itself? If so, then indeed it may have something
>>> to do with this.
>> Yes, it does.
>> Which is why it needs to know (and care) about the spool file format. It
>> ends up moving the queue files from one directory to another, and prodding
>> exim to deliver from the second (using -Mc).
> I might be wrong but as far as I know it doesn't. Amavis basically works
> as an SMTP loop here:


Amavis != MailScanner. Are you using MailScanner, or are you just passing the
mail to amavis from the exim inbuilt scanner?

Cheers

MBM

-- 
Matthew Byng-Maddick          <mbm@???>           http://colondot.net/
                      (Please use this address to reply)