Milter-greylist

Jeff A. Earickson wrote:
 > it dies with:
 > 
 > milter-greylist: [ID 653641 mail.error] mkstemp("/var/milter-greylist/greylist.db-XXiTa40g") failed: Permission denied
 > 
 > after about five minutes of running successfully.

That's probably the first time it tries to save its database.

 > ./configure --prefix=/opt/milter-greylist --with-db=/opt/BerkeleyDB \
 > --mandir=/usr/local/man --with-user=smmsp

So your milter-greylist process is running as user "smmsp".

 > % ls -ld /var/milter-greylist
 > drwxr-xr-x   2 nobody   smmsp        512 Oct 12 13:27 /var/milter-greylist

But the directory is owned by nobody, so the user cannot
write to it, hence it dies.  The milter-greylist process
requires write access to the directory.

 > I originally created /var/milter-greylist as owner "smmsp" but 
 > it seems to have changed it to "nobody" at the time of the mkstemp.

That's unlikely.  The milter-greylist process cannot change
ownership of anything, because it's not running as root.

 > What should the owner and permissions of /var/milter-greylist be?

It should be sufficient to make the directory group-writable
(i.e. "chmod g+w /var/milter-greylist").  Either that, or
change the owner to smmsp (that's what I usually do).  Well,
or run milter-greylist as root, but I assume you don't want
that (it's not a good idea).

Best regards
   Oliver

-- 
Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"[...]  one observation we can make here is that Python makes
an excellent pseudocoding language, with the wonderful attribute
that it can actually be executed."  --  Bruce Eckel