Milter-greylist

I have just installed milter-greylist on my server and it seems to be 
working pretty well, but I have a couple of questions.

First, how do I get the logging to work. I'm running milter-greylist 
with one of the sample config files. I've removed the # from the log to 
file section. When I start or check (-c) milter-greylist I get this 
output...

ignored "/var/log/greylist/greylist.log" stat output line 15
config file "/etc/mail/greylist.conf" is okay

I've checked th log location is correct and that it is writable by the 
milter-greylist user (smmsp). Nothing is being written to the log file.

Second, I've found this in my log files (logwatch)...

Milter (greylist): timeout before data read, where=mail: 10 Time(s)


Iam going to increase the milter-greylist timeout as shown in the wiki. 
Is this likely to solve this timeout error?

Thanks,
Rick

Rick Knight <rick_knight@...> wrote:

> ignored "/var/log/greylist/greylist.log" stat output line 15
> config file "/etc/mail/greylist.conf" is okay
> 
> I've checked th log location is correct and that it is writable by the
> milter-greylist user (smmsp). Nothing is being written to the log file.

Your stat output must be prepended by > if it is a file or by | if it is
a pipeline.

> Milter (greylist): timeout before data read, where=mail: 10 Time(s)
> 
> Iam going to increase the milter-greylist timeout as shown in the wiki.
> Is this likely to solve this timeout error?

Sure.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

manu@... wrote:
>
> Rick Knight <rick_knight@... 
> <mailto:rick_knight%40rlknight.com>> wrote:
>
> > ignored "/var/log/greylist/greylist.log" stat output line 15
> > config file "/etc/mail/greylist.conf" is okay
> >
> > I've checked th log location is correct and that it is writable by the
> > milter-greylist user (smmsp). Nothing is being written to the log file.
>
> Your stat output must be prepended by > if it is a file or by | if it is
> a pipeline.
>
> > Milter (greylist): timeout before data read, where=mail: 10 Time(s)
> >
> > Iam going to increase the milter-greylist timeout as shown in the wiki.
> > Is this likely to solve this timeout error?
>
> Sure.
>
> -- 
> Emmanuel Dreyfus
> http://hcpnet.free.fr/pubz <http://hcpnet.free.fr/pubz>
> manu@... <mailto:manu%40netbsd.org>
>
>  
So I would want to change the line to ... ?

|stat > "/var/milter-greylist/greylist.log" \
      "%T{%Y/%m/%d %T} %d [%i] %r -> %f %S (ACL %A) %Xc %Xe %Xm %Xh"

Thanks,
Rick

|

manu@... wrote:
>
> Rick Knight <rick_knight@... 
> <mailto:rick_knight%40rlknight.com>> wrote:
>
> > ignored "/var/log/greylist/greylist.log" stat output line 15
> > config file "/etc/mail/greylist.conf" is okay
> >
> > I've checked th log location is correct and that it is writable by the
> > milter-greylist user (smmsp). Nothing is being written to the log file.
>
> Your stat output must be prepended by > if it is a file or by | if it is
> a pipeline.
>
> > Milter (greylist): timeout before data read, where=mail: 10 Time(s)
> >
> > Iam going to increase the milter-greylist timeout as shown in the wiki.
> > Is this likely to solve this timeout error?
>
> Sure.
>
> -- 
> Emmanuel Dreyfus
> http://hcpnet.free.fr/pubz <http://hcpnet.free.fr/pubz>
> manu@... <mailto:manu%40netbsd.org>
>
>  
Ok, I have the syntax correct for prepending > to the command. When I 
look at the new log file, everything is one line. Is there a way to have 
each event on a seperate line?

Thanks again,
Rick

Rick Knight wrote:
>
> manu@... <mailto:manu%40netbsd.org> wrote:
> >
> > Rick Knight <rick_knight@... 
> <mailto:rick_knight%40rlknight.com>
> > <mailto:rick_knight%40rlknight.com>> wrote:
> >
> > > ignored "/var/log/greylist/greylist.log" stat output line 15
> > > config file "/etc/mail/greylist.conf" is okay
> > >
> > > I've checked th log location is correct and that it is writable by the
> > > milter-greylist user (smmsp). Nothing is being written to the log 
> file.
> >
> > Your stat output must be prepended by > if it is a file or by | if it is
> > a pipeline.
> >
> > > Milter (greylist): timeout before data read, where=mail: 10 Time(s)
> > >
> > > Iam going to increase the milter-greylist timeout as shown in the 
> wiki.
> > > Is this likely to solve this timeout error?
> >
> > Sure.
> >
> > --
> > Emmanuel Dreyfus
> > http://hcpnet.free.fr/pubz <http://hcpnet.free.fr/pubz> 
> <http://hcpnet.free.fr/pubz <http://hcpnet.free.fr/pubz>>
> > manu@... <mailto:manu%40netbsd.org> <mailto:manu%40netbsd.org>
> >
> >
> Ok, I have the syntax correct for prepending > to the command. When I
> look at the new log file, everything is one line. Is there a way to have
> each event on a seperate line?
>
> Thanks again,
> Rick
>
>  
I've tried adding the new line character to the end of the command but 
that didn't work. Just produced an empty file.

Thanks,
Rick

Rick Knight <rick_knight@...> wrote:

> Ok, I have the syntax correct for prepending > to the command. When I
> look at the new log file, everything is one line. Is there a way to have
> each event on a seperate line?

What about adding a \n at the end of your format string?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

Rick Knight <rick_knight@...> wrote:

> I've tried adding the new line character to the end of the command but
> that didn't work. Just produced an empty file.

Um, reading the doc, it's >> and not >, actually.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

manu@... wrote:
>
> Rick Knight <rick_knight@... 
> <mailto:rick_knight%40rlknight.com>> wrote:
>
> > I've tried adding the new line character to the end of the command but
> > that didn't work. Just produced an empty file.
>
> Um, reading the doc, it's >> and not >, actually.
>
> -- 
> Emmanuel Dreyfus
> http://hcpnet.free.fr/pubz <http://hcpnet.free.fr/pubz>
> manu@... <mailto:manu%40netbsd.org>
>
>  

Thanks,

I also had my new line character wrong. I had /n instead of \n.

I read the wiki and looked at the man pages. I also read the 
installation part of the README and scanned through the whole document. 
I missed the Custom log section. My apologies.

Everything seems to be working well now and I think I'll go site wide.

Thanks for a great tool,
Rick