[milters] Archive

Lists Index Date Thread Search

Article: 721
From: Jeff Powell
Date: 2005-09-10 18:06:38 -0400
Subject: Re: Can't get milter-sender 1.4 to start

Removal...........: milters-request@milter.info?subject=remove
More information..: http://www.milter.info/#Support

>Are you using the startup script supplied with the milter or some other
startup script?

The one supplied with the milter.

>Since its a Linux, then milter-sender lives in /usr/local/sbin, so what
happens if you simply type:
>	# milter-sender
>	# ps axf
>	# tail -f -n 30 /var/log/maillog

Nothing at all.  No output from the milter-sender command, it does not
appear in the process list, and no log entries.
>milter-sender can be started directly without a startup script and
stopped directly without one too:
>	# milter-sender -x

No output from this either.

>Typical reasons for not starting are read permission issues with
/etc/mail/sendmail.cf and/or >/etc/mail/access.db, also
/var/cache/milter-sender and /var/run/milter-sender.pid and

All these files have at least the permissions specified at
http://www.snertsoft.com/sendmail/milter-sender/ under
"Notes."  In some
cases the permissions are greater than those specified.
Milter-sender.pid and milter-sender.socket do not exist because it is
not running.

>The 1.x milter-sender must initial start as root so that it can
create/open the necessary files in root-only >>>>locations (/var/cache
and /var/run), but once running switches to milter:milter ownership so
the above file >>must continue to be accessible to "milter" user or

>If you're using a Mandrake, they have/had some annoying script that
periodically looks for changes of >>>>>>>>>file/directory
and ownership of key files, typically /etc/mail/access.db and
/etc/mail/sendmail.cf to stop undoing the permissions required by the

You're referring to msec.  That only becaomes a problem when you have
your machine set at a security level higher than I have mine.
Milter-sender has been working happily until now, so unless
milter-sender's permission requirements have changed between 1.2 (my
previous version) and 1.4, this is not the issue.

What I find odd is that there are no log entries at all.

For the record, here are the permissions for the relevant files:

drwxr-xr-x   3 root smmsp  4096 Sep  9 17:42 ./
drwxr-xr-x  86 root root   8192 Sep  9 16:34 ../
-rw-r--r--   1 root root  12056 Sep  2 15:21 access
-rw-r--r--   1 root smmsp 24576 Sep  9 16:34 access.db
lrwxrwxrwx   1 root root     12 Apr 25 15:28 aliases -> /etc/aliases
lrwxrwxrwx   1 root smmsp    15 Apr 25 15:28 aliases.db ->
-rw-r--r--   1 root root   8397 Sep  9 17:14 milter-sender.cf
-rw-r--r--   1 root smmsp 62974 Sep  9 17:42 sendmail.cf

drwxr-xr-x  17 root   root    4096 Sep 10 15:01 ./
drwxr-xr-x  20 root   root    4096 Jun 20 20:51 ../

drwxr-xr-x   8 root   root    4096 Sep 10 14:48 ./
drwxr-xr-x  20 root   root    4096 Jun 20 20:51 ../
-rw-r--r--   1 milter milter 24576 Sep  9 16:41 milter-sender

drwxr-xr-x   2 root root     4096 Sep 10 14:51 ./
drwxr-xr-x  17 root root     4096 Jul 15 21:24 ../
-r-xr-xr-x   1 root milter 409656 Sep 10 14:51 milter-sender*

Lists Index Date Thread Search