Dovecot 1.2.10 fails to start

[Mark Hattam]

On 7 Feb 2010, at 19:41, Bradley Giesbrecht wrote:

> 
> On Feb 6, 2010, at 4:42 AM, Mark Hattam wrote:
> 
>> On 6 Feb 2010, at 10:43, Ryan Schmidt wrote:
>> 
>>> 
>>> On Feb 5, 2010, at 12:01, Mark Hattam wrote:
>>> 
>>>> sudo port upgrade'd Dovecot to 1.2.10 from 1.1.16
>>>> 
>>>> upgrade appeared to go OK, but then found Dovecot 1.2.10 unable to start up
>>>> 
>>>> Feb  5 17:39:42 iMac com.apple.launchd[1] (org.macports.dovecot[389]): Exited with exit code: 2
>>>> Feb  5 17:39:42 iMac org.macports.dovecot[401]: Error: Error in configuration file /opt/local/etc/dovecot/dovecot.conf line 87: Unknown setting: ssl_disable
>>>> Feb  5 17:39:42 iMac org.macports.dovecot[401]: Fatal: Invalid configuration in /opt/local/etc/dovecot/dovecot.conf
>>>> 
>>>> OK ... that's easy to change ... compare with dovecot-example.conf and notice the subtle change
>>>> 
>>>> less dovecot-example.conf
>>>> # SSL/TLS support: yes, no, required. <doc/wiki/SSL.txt>
>>>> #ssl = yes
>>>> 
>>>> less dovecot.conf
>>>> # Disable SSL/TLS support.
>>>> ssl_disable = yes
>>>> 
>>>> So comment out the
>>>> ssl_disable line and add the ssl line (with no)
>>>> 
>>>> 
>>>> HOWEVER, that just led to this error
>>>> 
>>>> Feb  5 17:44:12 iMac com.apple.launchd[1] (org.macports.dovecot[448]): Exited with exit code: 2
>>>> Feb  5 17:44:12 iMac org.macports.dovecot[462]: Last died with error (see error log for more information): Socket already exists: /opt/local/var/run/dovecot/dict-server
>>>> Feb  5 17:44:12 iMac dovecot[464]: Fatal: Socket already exists: /opt/local/var/run/dovecot/dict-server
>>>> 
>>>> 
>>>> But the error log just says the same thing
>>>> Feb  5 17:44:12 iMac dovecot[464]: Dovecot v1.2.10 starting up (core dumps disabled)
>>>> Feb  5 17:44:12 iMac dovecot[464]: Fatal: Socket already exists: /opt/local/var/run/dovecot/dict-server
>>>> 
>>>> 
>>>> Googling the error, suggests that this is a known problem with a patch in Oct 2008
>>>> 
>>>> But how to apply the patch?
>>>> 
>>>> [Gone back to 1.1.16 so I can write this]
>>> 
>>> I'm sorry you're having difficulties. Unfortunately I don't know anything about dovecot; I just committed the update that was attached to a ticket. If there is a patch we should be applying, can you refer me to the appropriate URL? Have you already contacted the developers of dovecot for assistance? They should know better than I how to get their software working.
>>> 
>>> Off the top of my head, to the error "Socket already exists" -- does it? If so, why? Is dovecot running? If so, stop it, make sure the socket doesn't exist anymore (delete it if it doesn't go away on its own), then start dovecot again. Does it now start cleanly?
>> 
>> 
>> Ah OK ... it doesn't go away on its own. It's been there a long time through lots of reboots.
>> 
>> iMac:dovecot mark$ ls -la /opt/local/var/run/dovecot/
>> total 8
>> drwxr-xr-x  6 root  admin    204  5 Feb 17:51 .
>> drwxr-xr-x  4 root  admin    136 21 Nov 02:50 ..
>> srw-------  1 root  wheel      0  5 Feb 17:51 auth-worker.552
>> -rwxrwxrwx  1 root  admin      0 30 Aug 23:43 dict-server
>> drwxr-x---  3 root  dovecot  102  5 Feb 17:51 login
>> -rw-------  1 root  admin      4  5 Feb 17:51 master.pid
>> 
>> iMac:dovecot mark$ sudo rm dict-server
>> 
>> iMac:dovecot mark$ sudo port deactivate dovecot at 1.1.16_0+darwin_10
>> --->  Deactivating dovecot @1.1.16_0+darwin_10
>> 
>> <reboot> to ensure nothing is running that oughtn't be
>> 
>> iMac:~ mark$ sudo port activate dovecot at 1.2.10_0
>> --->  Activating dovecot @1.2.10_0
>> 
>> make the above changes to dovecot.conf
>> iMac:~ mark$ sudo vi /opt/local/etc/dovecot/dovecot.conf
>> 
>> run the new version again
>> iMac:~ mark$ sudo launchctl load -w /Library/LaunchDaemons/org.macports.dovecot.plist
>> 
>> Now I see
>> iMac:dovecot mark$ ls -la /opt/local/var/run/dovecot/
>> total 16
>> drwxr-xr-x  7 root  admin    238  6 Feb 12:32 .
>> drwxr-xr-x  4 root  admin    136 21 Nov 02:50 ..
>> srw-------  1 root  wheel      0  6 Feb 12:32 auth-worker.64
>> srwxrwxrwx  1 root  admin      0  6 Feb 12:32 dict-server
>> 
>> ls: /opt/local/var/run/dovecot//dovecot.conf: Permission denied
>> lrwx------  1 root  admin     35  6 Feb 12:32 dovecot.conf
>> drwxr-x---  3 root  dovecot  102  6 Feb 12:32 login
>> -rw-------  1 root  admin      3  6 Feb 12:32 master.pid
>> 
>> repeated with sudo
>> 
>> iMac:dovecot mark$ sudo ls -la /opt/local/var/run/dovecot/
>> Password:
>> total 16
>> drwxr-xr-x  7 root  admin    238  6 Feb 12:32 .
>> drwxr-xr-x  4 root  admin    136 21 Nov 02:50 ..
>> srw-------  1 root  wheel      0  6 Feb 12:32 auth-worker.64
>> srwxrwxrwx  1 root  admin      0  6 Feb 12:32 dict-server
>> lrwx------  1 root  admin     35  6 Feb 12:32 dovecot.conf -> /opt/local/etc/dovecot/dovecot.conf
>> drwxr-x---  3 root  dovecot  102  6 Feb 12:32 login
>> -rw-------  1 root  admin      3  6 Feb 12:32 master.pid
>> 
>> So dovecot 1.2.10 is now running without chucking errors into system.log or mail.log which appears to be good.
> 
> Sorry, I meant to try to help you out with this but ended up with a day of flames.
> 
> I use dovecot and may have been the person who submitted the update patch. Is dovecot 1.2 working for you now?
> 
> Were you using virtual users?
> 
> If so did the mailbox locations change?
> Mine did, dovecot 1.2 added a subdir "mailboxes" which I could not figure out why and ended up just moving all my mailboxes into this new subdir to get things working.
> 
> I'm working on a dovecot-sieve port if your interested. If you are I'll share my portfile with you. I wouldn't mind having another set of eyes working on dovecot-sieve with me. I have no sieve experience.
> 
> My dovecot-sieve port currently installs fine so mostly I just need to work on some sieve scripts to test it and then I want to put together a dovecot-managesieve port.
> 
> 
> // Brad


Hi Brad

Yes it's running fine now. The subtle change in dovecot.conf I could suss out by the error, and if I'd known to delete the zero byte dict-server file, it'd have been fixed quicker. But it's fixed now.

I'm not using virtual users - though I would like to have a public read-only archive of emails served up. I can get most of that working, but SquirrelMail's search doesn't work.

I use Maildir rather than mbox and that's all working the same as it did before. The only change I had to make was the SSL=no rather than SSL-disable=yes in the conf.

In totality,
I use  getmail  to received mail using SDPS from my ISP's POP3 server
That gets passed to MailDrop which sends it to DSPAM using xfilter line in .mailfilter
DSPAM returns it to Maildrop which filters the mail into required Maildir directories

DSPAM uses a MySQL database which is clean-up'd daily using DSPAM's MySQL script.

So all the Macs and PCs here have the same server based mail, all have their Junk filtering turned off, and SquirrelMail serves it up as webmail (with the exception of "search" for a non-admin user).

Mark