Description of problem:

After a "yum update" which updates dovecot, dovecot fails to restart and refuses
to start manually because it can not access /usr/share/ssl/certs/dovecot.pem,
which had been a symbolic link to the real certificate file.

Version-Release number of selected component (if applicable):

dovecot-1.0-0.beta8.2.fc5 (and recent earlier updates.

How reproducible:

Very...  Has happened with the last couple of dovecot updates on 4 different
systems.

Steps to Reproduce:
1. Create a real certificate pair foo.crt/foo.key in
/usr/share/ssl/{certs/foo.crt,private/foo.key}, CA signed or selfsign as desired.

2. Create symlink from foo.crt to dovecot.pem in .../certs.

3. Create symlink from foo.key to dovecot.pem in .../private.

3. Configured ssl cert paths (dovecot.pem) in /etc/dovecot.conf

4. Update dovecot using yum

5. Note: dovecot refuses to start, unable to open cert file .../certs/dovecot.pem.

6. Note: .../certs/dovecot.pem is missing (only symlink, real cert file still
present).

7. Note: .../private/dovecot.pem is still present (undamaged).
  
Actual results:

Symlink to the cert file is deleted by yum update process.
Dovecot refuses to {re}start.
Dovecot in non-functional after an update until certs are repaired.

Expected results:

Existing cert and key files or symlinks should NEVER be tampered with (mine are
actual, real, signed X.509 certificates).  Dovecot should be functional after an
update.

Additional info: