On Jan 4, 2011, at 2:00 PM, [email protected] wrote: > Message: 12 > Date: Tue, 4 Jan 2011 10:31:31 -0500 > From: Dan Shoop <[email protected]> > Subject: Re: dovecot errors > To: Scott Ribe <[email protected]> > > > On Jan 3, 2011, at 6:09 PM, Scott Ribe wrote: > >> Is it possible that there's some other service enabled which starts up >> dovecot directly rather than depending on the launchd service? > > No, it's started by launchd and that was also abundantly clear by the log > entries for which launchd was it's parent. > > But as I pointed out, any attempt at mail delivery will require dovecot in OS > X Server (unless you've set delivery directly to a user mail spool as per the > user account record in WGM.) > > -d
If postfix is running then it is setup by default in /etc/postfix/main.cf to use mailbox_transport=dovecot and there is a transport for dovecot specified in /etc/postfix/master.cf. Even if it is not running in daemon mode, postfix can still handle local mail generated by syslog or other means. AFAICT, you can't change this via Server Admin. So, unless you've already made changes to postfix configuration, It will call dovecot. From there, I guess it's up to launchd whether the process gets spawned or not. Also, I'd check that log levels aren't set too high. Verbose and/ Debug logging may generate additional mail to root, especially if you're using log reporting. In particular check, /etc/dovecot/dovecot.conf for auth_verbose = yes Looks to me like the options are to reconfigure postfix to use a different local delivery agent or go ahead and set up AUTH for Dovecot. The latter seems much more simple to me. Best, Tim Roberts_______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
