Okay! I got it.
I guess it had to do with the chroot of smtp-vilter... I'm not sure why, because it doesn't do this on my 3.8 box... but on my 4.5 box, it is dropping its socket to /var/smtp-vilter/var/smtp-vilter/smtp-vilter.sock. So, the error I was getting in the log wasn't really appropriate. I would think it should have said something like: "unable to to connect to socket", rather than complain about the perms (which, as it turns out, were appropriate). At least its solved! Thanks Philip, John and Vijay for your input! Chris Quoting Chris <[email protected]>:
Hi, I have been playing with this for hours now, and I'm getting really frustrated. I'm building an email server, and I want to use smtp-vilter to send my emails through spamassassin and clamav. I'm using obsd 4.5 and sendmail. I keep getting this in my logs: Milter (smtp-vilter): local socket name /var/smtp-vilter/smtp-vilter.sock unsafe Milter (smtp-vilter): to error state Milter: initialization failed, temp failing commands This failure blocks all mail from being sent. I have tried switching users on this socket, I have tried switching perms, right now, I have it owned by _vilter:_vilter with the mode at 0600... it doesn't get much more "safe" than that... What am I doing wrong here?
