On Jan 2, 2011, at 11:20 PM, LuKreme wrote: > I am seeing this about ever 10-11 seconds > > Jan 2 16:24:07 shiva org.dovecot.dovecotd[22677]: Warning: Last died with > error (see error log for more information): Auth process died too early - > shutting down > Jan 2 16:24:07 shiva dovecot[22677]: Fatal: auth(default): Unknown > authentication mechanism 'none' > Jan 2 16:24:07 shiva dovecot[22677]: Fatal: Auth process died too early - > shutting down > Jan 2 16:24:07 shiva com.apple.launchd[1] (org.dovecot.dovecotd[22677]): > Exited with exit code: 89 > Jan 2 16:24:07 shiva com.apple.launchd[1] (org.dovecot.dovecotd): Throttling > respawn: Will start in 10 seconds > > The machine is NOT running dovecot (or any mail service), but it appears this > gets loaded by default by OS X Server.
It's not loaded by default, it's getting loaded on demand and because someone is trying to connect to your server via IMAP or POP. Have them stop or block that port traffic like a good sysadmin who only allows traffic to ports & services which are enabled. > I've done > > # launchctl remove org.dovecot.dovecotd > > but it seems to be coming back. Correct, all you did was remove it. > If I look at the org.dovecot.dovecotd.plist file I see: > > # cat /System/Library/LaunchDaemons/org.dovecot.dovecotd.plist > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" > "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> > <plist version="1.0"> > <dict> > <key>Disabled</key> > <true/> > <key>Label</key> > <string>org.dovecot.dovecotd</string> > <key>OnDemand</key> > <false/> > <key>Program</key> > <string>/usr/sbin/dovecotd</string> > <key>ProgramArguments</key> > <array> > <string>dovecotd</string> > <string>-F</string> > </array> > <key>ServiceIPC</key> > <false/> > <key>HardResourceLimits</key> > <dict> > <key>NumberOfFiles</key> > <integer>8192</integer> > </dict> > <key>SoftResourceLimits</key> > <dict> > <key>NumberOfFiles</key> > <integer>8192</integer> > </dict> > </dict> > </plist> > > It seems to me that the Disabled key should be preventing this process from > even trying to start, yet it tries to start ever 10 seconds or so. Because it's getting relaunched on demand. Unload it. -d ------------------------------------------------------------------------ Dan Shoop [email protected] GoogleVoice: 1-646-402-5293 aim: iWiring twitter: @colonelmode _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
