"System Support" <[email protected]> writes: > On 28 Aug 2009 at 13:45, Murray S. Kucherawy wrote: > >> > >> > Everything seems fine on my dkim signing service. However, every hour, >> > almost exactly at the same time, I get this error >> > in my logs: >> > >> > Aug 26 14:02:45 mx2 postfix/cleanup[12057]: warning: connect to Milter >> > service unix:/var/run/dkim-filter/dkim-filter.sock: No such file or >> > directory > > The message is from the cleanup process. "The cleanup daemon is the > final processing stage for new messages. It adds any required missing > headers, arranges for address rewriting, and (optionally) extracts > recipient addresses from message headers. The cleanup daemon inserts > the result into the incoming queue and then notifies the queue manager > that new mail has arrived."
Correct.... in fact this made me think about things more and I had an epiphany. The logcheck cronjob is actually run at :02 at the hour. The log indicated above comes from the same time. After some investigation, I find that when logcheck has something to report, it utilizes the local mail facility (ala mail/mailx/sendmail): cat $TMPDIR/report | mail -s "$subject" "$SENDMAILTO" When I do this command manually, I see it: Sep 2 13:02:00 mx2 postfix/cleanup[17777]: warning: connect to Milter service unix:/var/run/dkim-filter/dkim-filter.sock: No such file or directory Aha. So now i've located where it comes from, and can replicate it! The local sendmail delivery process, which typically are handled by postfix in the configuration option which I have set: non_smtpd_milters = unix:/var/run/dkim-filter/dkim-filter.sock Quote from http://www.postfix.org/MILTER_README.html: The non-SMTP filters handle mail that arrives via the Postfix sendmail(1) command-line or via the Postfix qmqpd(8) server. They are typically used to digitally sign mail only. Looking at my /etc/postfix/master.cf, I find that my smtp process is not chrooted, however, the cleanup one is: # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # ========================================================================== cleanup unix n - - - 0 cleanup Replacing that - in the chroot column, restarting postfix and then attempting the test again reveals that the problem is gone! Thanks for the help folks, I've been beating my head on this one for months :) micah ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
