Re: clamav-milter notify problem

[Simone Marchioni]

> Not sure off hand... file a bug?
> You do have the milter running I assume?
> Also, have you edited the /etc/clamd.d/milter.conf and commented the
> stupid "Example" line?

Hi Kevin,

thanks for the answer.
Yes, I have the milter running and it works well: as I stated in the previous mail it does the job well.
I have the milter for both Spamassassin and Clamav.
And yes I commented the Example line.

Maybe the last possibility is just to file a bug... :-(((
But it's strange the packager didn't realize this problem.
> kevin

I'll file a bug.
Thank you!
Simo

clamav-milter notify problem

[Simone Marchioni]

> I'll file a bug.

Filed.

https://bugzilla.redhat.com/show_bug.cgi?id=428158

clamav-milter notify problem

[Michael Schwendt]

On Wed, 09 Jan 2008 18:59:25 +0100, Simone Marchioni wrote:
> > Not sure off hand... file a bug?
> > You do have the milter running I assume?
> > Also, have you edited the /etc/clamd.d/milter.conf and commented the
> > stupid "Example" line?
>
> Hi Kevin,
>
> thanks for the answer.
> Yes, I have the milter running and it works well: as I stated in the previous mail it does the job well.
> I have the milter for both Spamassassin and Clamav.
> And yes I commented the Example line.
>
> Maybe the last possibility is just to file a bug... :-(((
> But it's strange the packager didn't realize this problem.
> > kevin
>
> I'll file a bug.

It sounded familiar... but:

https://www.redhat.com/archives/fedora-list/2005-July/msg02794.html

Hmmm...

"sh: no: command not found" errors sometimes occur in sloppy sh/bash based
feature check expressions (e.g. in configure scripts) when a variable is
assigned "no" or remains at a "no" default because something is missing.

clamav-milter notify problem

[Simone Marchioni]

> It sounded familiar... but:
>
> https://www.redhat.com/archives/fedora-list/2005-July/msg02794.html
>
> Hmmm...
>
> "sh: no: command not found" errors sometimes occur in sloppy sh/bash based
> feature check expressions (e.g. in configure scripts) when a variable is
> assigned "no" or remains at a "no" default because something is missing.

Thanks for the tip Michael!
Sadly the problem is more than two years old... :-(

Did you solved it? What can I check to find where the problem is?

Many thanks!
Simo