Re: [Clamav-users] Weird timeout problem starting clmav milter after upgrade to 0.86.2

Erich Titl <[EMAIL PROTECTED]> writes: > I used to run clamav-milter without --external under 0.85. After > upgrading to 0.86.2 I see an error --timeout must not be given when > --external is not given. There is no such thing as timeout in my config > so this is really weird. The only way getting

Re: [Clamav-users] Weird timeout problem starting clmav milter after upgrade to 0.86.2

On Tue, 26 Jul 2005, Erich Titl wrote: I used to run clamav-milter without --external under 0.85. After upgrading to 0.86.2 I see an error --timeout must not be given when --external is not given. There is no such thing as timeout in my config so this is really weird. The only way getting rid of

Re: [Clamav-users] Weird timeout problem starting clmav milter after upgrade to 0.86.2

> Hi Folks > > I used to run clamav-milter without --external under 0.85. After > upgrading to 0.86.2 I see an error --timeout must not be given when > --external is not given. There is no such thing as timeout in my config > so this is really weird. The only way getting rid of this was to specify

[Clamav-users] Weird timeout problem starting clmav milter after upgrade to 0.86.2

Hi Folks I used to run clamav-milter without --external under 0.85. After upgrading to 0.86.2 I see an error --timeout must not be given when --external is not given. There is no such thing as timeout in my config so this is really weird. The only way getting rid of this was to specify --external.