14

I'm trying to configure dovecot+postfix on a new 14.04 release image in EC2. I installed mail-stack-delivery without installing postfix or dovecot separately. Now I can't figure out how to restart dovecot because /etc/init.d/dovecot seems missing. Or am I missing something? Thanks.

jingx
  • 477
  • 2
  • 4
  • 12
  • 2
    `sudo service dovecot restart` might work. – douggro Apr 20 '14 at 15:38
  • 1
    Thanks! I actually did "sudo service --status-all" but dovecot wasn't on the list, and then "sudo service dovecot" returns "dovecot: unrecognized service", which made me believe dovecot wasn't converted to a service yet. So I never thought of actually trying with restart. – jingx Apr 20 '14 at 21:15
  • Is Dovecot installed? If it were, `service status dovecot` should return a `stopped/waiting` status. – douggro Apr 21 '14 at 06:29
  • @jingx you should better write your comment in an answer to this question and accept it. – Amir Ali Akbari May 01 '14 at 13:48
  • The answer is there is no /etc/init.d/dovecot by default, but you can download a functional init.d script that should meet your needs at: http://wiki2.dovecot.org/RunningDovecot I recommend the wiki as a whole as a good resource for helping you with dovecot. – wargasm May 15 '14 at 16:28

3 Answers3

12

Ok so after going through dovecot's wiki (version 2), it seems that we can restart/reload/stop dovecot by using:

For root:

# doveadm reload - to restart/reload dovecat

# doveadm stop - to stop dovecat

For sudo users:

# sudo doveadm reload - to restart/reload dovecat

# sudo doveadm stop - to stop dovecat

You can just type doveadm / sudo doveadm to see a list of other commands you can use with doveadm too.

AndrewL64
  • 345
  • 3
  • 16
2

Thanks to @douggro for the reminder! I actually did sudo service --status-all but dovecot wasn't on the list, and then sudo service dovecot returns dovecot: unrecognized service, which made me believe dovecot wasn't converted to a service yet. So I never thought of actually trying with restart.

muru
  • 193,181
  • 53
  • 473
  • 722
jingx
  • 477
  • 2
  • 4
  • 12
2

When the old services are converted from init.d to the upstart, service status xxxx returns service unrecognized. Instead please use servicename status

The coexistence of upstart and init.d is confusing, so in Vivid and later releases it is replaced with systemd

The current state in 14.04 is confusing and creating some issues when monitoring things as well, at least with my experience.

tony
  • 21
  • 3