dovecot.conf configuration broken on SSL renewal

Hi Gents,

Here's the issue.

When a Virtualhost with a Dedicated IP has its SSL renewal triggered it seems to look in dovecot.conf for a line that contains the dedicated IP and INSERT this line if it was missing. Something like below

local 123.456.789.123 {
  protocol imap {
    ssl_cert = </home/domain/ssl.cert
    ssl_key = </home/domain/ssl.key
    ssl_ca = </home/domain/ssl.ca
  }
  protocol pop3 {
    ssl_cert = </home/domain/ssl.cert
    ssl_key = </home/domain/ssl.key
    ssl_ca = </home/domain/ssl.ca
  }
}

The reasoning makes sense, however this actually breaks the mail server in some cases for 'whatever' reason. The only way to get Dovecot to startup is to remove those lines.

Is there a way to instruct the SSL Renewal process for a virtualhost to leave the dovecot.conf untouched?

Status: 
Active

Comments

Assigned: Unassigned »
Body: View changes

Howdy -- thanks fr your report!

I've passed this along to Jamie for comment.

Gents, this issue just occurred again...

The following was added to dovecot.conf and prevents other dedicated IP mail services from accessing their mailbox.

local 192.99.60.55 {
  protocol imap {
    ssl_cert = </home/wiserweb.com/ssl.cert
    ssl_key = </home/wiserweb.com/ssl.key
    ssl_ca = </home/wiserweb.com/ssl.ca
  }
  protocol pop3 {
    ssl_cert = </home/wiserweb.com/ssl.cert
    ssl_key = </home/wiserweb.com/ssl.key
    ssl_ca = </home/wiserweb.com/ssl.ca
  }
}

Is this something that can be fixed in upcoming release?

Thanks.

What error message are you getting in your Dovecot logs (usually /var/log/maillog) when you try to start it after those lines are added?