Update reply_by_email_postfix_setup.md, included starting courier-authdaemon after installation.
What does this MR do?
Added a step to documentation to start courier-authdaemon after installation
Are there points in the code the reviewer needs to double check?
No
Why was this MR needed?
When using reply-by-email, mailroom fails to access imap on port 143, after diagnosing a fresh installation and following the steps stated in the docs, I discovered that that imapd
is not started and the instance is refusing connections on port 143. It is required to start imapd
after installation.
See example of customer error here:
2017-07-13_06:47:57.49409 Runit: waiting 5 seconds before restarting mail_room
2017-07-13_06:48:02.45984 Runit: starting mail_room
2017-07-13_06:48:04.05846 bundler: failed to load command: mail_room (/opt/gitlab/embedded/bin/mail_room)
2017-07-13_06:48:04.05852 Errno::ECONNREFUSED: Connection refused - connect(2) for "alm-ubuntu.westeurope.cloudapp.azure.com" port 143
2017-07-13_06:48:04.05853 /opt/gitlab/embedded/lib/ruby/2.3.0/net/imap.rb:1082:in `initialize'
2017-07-13_06:48:04.05853 /opt/gitlab/embedded/lib/ruby/2.3.0/net/imap.rb:1082:in `open'
2017-07-13_06:48:04.05854 /opt/gitlab/embedded/lib/ruby/2.3.0/net/imap.rb:1082:in `initialize'
2017-07-13_06:48:04.05854 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/connection.rb:74:in `new'
2017-07-13_06:48:04.05854 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/connection.rb:74:in `imap'
2017-07-13_06:48:04.05854 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/connection.rb:84:in `log_in'
2017-07-13_06:48:04.05855 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/connection.rb:68:in `setup'
2017-07-13_06:48:04.05855 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/connection.rb:8:in `initialize'
2017-07-13_06:48:04.05855 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/mailbox_watcher.rb:57:in `new'
2017-07-13_06:48:04.05856 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/mailbox_watcher.rb:57:in `connection'
2017-07-13_06:48:04.05857 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/mailbox_watcher.rb:28:in `run'
2017-07-13_06:48:04.05858 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/coordinator.rb:19:in `each'
2017-07-13_06:48:04.05858 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/coordinator.rb:19:in `run'
2017-07-13_06:48:04.05858 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/cli.rb:52:in `start'
2017-07-13_06:48:04.05858 /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/bin/mail_room:5:in `<top (required)>'
2017-07-13_06:48:04.05859 /opt/gitlab/embedded/bin/mail_room:22:in `load'
2017-07-13_06:48:04.05859 /opt/gitlab/embedded/bin/mail_room:22:in `<top (required)>'
2017-07-13_06:48:04.06839 Runit: waiting 5 seconds before restarting mail_room
Screenshots (if relevant)
Nill
Does this MR meet the acceptance criteria?
Nill
What are the relevant issue numbers?
NIll
/cc @lbot