Re: [exim] Bug#360696: Bug#360696: Failed to get write lock …

Página Inicial
Delete this message
Reply to this message
Autor: Michel Meyers
Data:  
Para: Matthew Byng-Maddick, 360696-quiet
CC: exim-users, 360696-submitter
Tópicos Antigos: Re: [exim] Bug#360696: Failed to get write lock for/var/spool/exim4/db/retry.lockfile:timed out
Assunto: Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for/var/spool/exim4/db/retry.lockfile:timedout
Matthew Byng-Maddick wrote:
> 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,


No, I am not using MailScanner. I use amavisd-new and spamassassin
(spamc) with the configuration I described in my previous mail.

> or are you just passing the
> mail to amavis from the exim inbuilt scanner?


Correct, mail enters exim, then loops through amavis, gets piped through
spamc and then delivered to the destination.

Greetings,
           Michel