[users] dovecot RFX upgrade breakage

[Greg Bailey]

I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL certificates
in /usr/share/ssl, when the default CentOS 5 dovecot RPM uses
/etc/pki/dovecot.

I understand the whole RFX replaces base packages thing, but shouldn't
we try to preserve the configuration file locations? In this case an
upgrade changed default configuration in such a way as to break things...

I was also unable to log in via imap; I get:

dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with mbox
file /var/mail/username_goes_here: Permission denied

in /var/log/maillog. Apparently there's something else I need to change
here...

Thanks in advance for any advice with the dovecot upgrade!

-Greg

[Matthew Feinberg]

I second this motion. I had the same problem twice tonight with the SSL
location.

Matthew

Post by Greg Bailey
I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL
certificates in /usr/share/ssl, when the default CentOS 5 dovecot RPM
uses /etc/pki/dovecot.
I understand the whole RFX replaces base packages thing, but shouldn't
we try to preserve the configuration file locations? In this case an
upgrade changed default configuration in such a way as to break things...
dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with
mbox file /var/mail/username_goes_here: Permission denied
in /var/log/maillog. Apparently there's something else I need to
change here...
Thanks in advance for any advice with the dovecot upgrade!
-Greg
_______________________________________________
users mailing list
users at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/users

[Dag Wieers]

Post by Matthew Feinberg

Post by Greg Bailey
I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL certificates
in /usr/share/ssl, when the default CentOS 5 dovecot RPM uses
/etc/pki/dovecot.
I understand the whole RFX replaces base packages thing, but shouldn't we
try to preserve the configuration file locations? In this case an upgrade
changed default configuration in such a way as to break things...
dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with mbox
file /var/mail/username_goes_here: Permission denied
in /var/log/maillog. Apparently there's something else I need to change
here...
Thanks in advance for any advice with the dovecot upgrade!

I second this motion. I had the same problem twice tonight with the SSL
location.

I support such a change. If you have any patches to the SPEC file that
have been tested to do what you need, I don't mind integrating them.
Beware though that simply changing the path using a configure option may
not be sufficient (or it might as well be ;-)).

Testing such a change is crucial here.

[Dag Wieers]

Post by Matthew Feinberg

Post by Greg Bailey
I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL certificates
in /usr/share/ssl, when the default CentOS 5 dovecot RPM uses
/etc/pki/dovecot.
I understand the whole RFX replaces base packages thing, but shouldn't we
try to preserve the configuration file locations? In this case an upgrade
changed default configuration in such a way as to break things...
dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with mbox
file /var/mail/username_goes_here: Permission denied
in /var/log/maillog. Apparently there's something else I need to change
here...
Thanks in advance for any advice with the dovecot upgrade!

I second this motion. I had the same problem twice tonight with the SSL
location.

I support such a change. If you have any patches to the SPEC file that
have been tested to do what you need, I don't mind integrating them.
Beware though that simply changing the path using a configure option may
not be sufficient (or it might as well be ;-)).

Testing such a change is crucial here.

[Dag Wieers]

Post by Matthew Feinberg

Post by Greg Bailey
I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL certificates
in /usr/share/ssl, when the default CentOS 5 dovecot RPM uses
/etc/pki/dovecot.
I understand the whole RFX replaces base packages thing, but shouldn't we
try to preserve the configuration file locations? In this case an upgrade
changed default configuration in such a way as to break things...
dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with mbox
file /var/mail/username_goes_here: Permission denied
in /var/log/maillog. Apparently there's something else I need to change
here...
Thanks in advance for any advice with the dovecot upgrade!

I second this motion. I had the same problem twice tonight with the SSL
location.

I support such a change. If you have any patches to the SPEC file that
have been tested to do what you need, I don't mind integrating them.
Beware though that simply changing the path using a configure option may
not be sufficient (or it might as well be ;-)).

Testing such a change is crucial here.

[Dag Wieers]

Post by Matthew Feinberg

Post by Greg Bailey
I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL certificates
in /usr/share/ssl, when the default CentOS 5 dovecot RPM uses
/etc/pki/dovecot.
I understand the whole RFX replaces base packages thing, but shouldn't we
try to preserve the configuration file locations? In this case an upgrade
changed default configuration in such a way as to break things...
dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with mbox
file /var/mail/username_goes_here: Permission denied
in /var/log/maillog. Apparently there's something else I need to change
here...
Thanks in advance for any advice with the dovecot upgrade!

I second this motion. I had the same problem twice tonight with the SSL
location.

I support such a change. If you have any patches to the SPEC file that
have been tested to do what you need, I don't mind integrating them.
Beware though that simply changing the path using a configure option may
not be sufficient (or it might as well be ;-)).

Testing such a change is crucial here.

[Dag Wieers]

Post by Matthew Feinberg

Post by Greg Bailey
I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL certificates
in /usr/share/ssl, when the default CentOS 5 dovecot RPM uses
/etc/pki/dovecot.
I understand the whole RFX replaces base packages thing, but shouldn't we
try to preserve the configuration file locations? In this case an upgrade
changed default configuration in such a way as to break things...
dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with mbox
file /var/mail/username_goes_here: Permission denied
in /var/log/maillog. Apparently there's something else I need to change
here...
Thanks in advance for any advice with the dovecot upgrade!

I second this motion. I had the same problem twice tonight with the SSL
location.

I support such a change. If you have any patches to the SPEC file that
have been tested to do what you need, I don't mind integrating them.
Beware though that simply changing the path using a configure option may
not be sufficient (or it might as well be ;-)).

Testing such a change is crucial here.

[Greg Bailey]

I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL certificates
in /usr/share/ssl, when the default CentOS 5 dovecot RPM uses
/etc/pki/dovecot.

I understand the whole RFX replaces base packages thing, but shouldn't
we try to preserve the configuration file locations? In this case an
upgrade changed default configuration in such a way as to break things...

I was also unable to log in via imap; I get:

dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with mbox
file /var/mail/username_goes_here: Permission denied

in /var/log/maillog. Apparently there's something else I need to change
here...

Thanks in advance for any advice with the dovecot upgrade!

-Greg

[Matthew Feinberg]

I second this motion. I had the same problem twice tonight with the SSL
location.

Matthew

Post by Greg Bailey
I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL
certificates in /usr/share/ssl, when the default CentOS 5 dovecot RPM
uses /etc/pki/dovecot.
I understand the whole RFX replaces base packages thing, but shouldn't
we try to preserve the configuration file locations? In this case an
upgrade changed default configuration in such a way as to break things...
dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with
mbox file /var/mail/username_goes_here: Permission denied
in /var/log/maillog. Apparently there's something else I need to
change here...
Thanks in advance for any advice with the dovecot upgrade!
-Greg
_______________________________________________
users mailing list
users at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/users

[Greg Bailey]

I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL certificates
in /usr/share/ssl, when the default CentOS 5 dovecot RPM uses
/etc/pki/dovecot.

I understand the whole RFX replaces base packages thing, but shouldn't
we try to preserve the configuration file locations? In this case an
upgrade changed default configuration in such a way as to break things...

I was also unable to log in via imap; I get:

dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with mbox
file /var/mail/username_goes_here: Permission denied

in /var/log/maillog. Apparently there's something else I need to change
here...

Thanks in advance for any advice with the dovecot upgrade!

-Greg

[Matthew Feinberg]

I second this motion. I had the same problem twice tonight with the SSL
location.

Matthew

Post by Greg Bailey
I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL
certificates in /usr/share/ssl, when the default CentOS 5 dovecot RPM
uses /etc/pki/dovecot.
I understand the whole RFX replaces base packages thing, but shouldn't
we try to preserve the configuration file locations? In this case an
upgrade changed default configuration in such a way as to break things...
dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with
mbox file /var/mail/username_goes_here: Permission denied
in /var/log/maillog. Apparently there's something else I need to
change here...
Thanks in advance for any advice with the dovecot upgrade!
-Greg
_______________________________________________
users mailing list
users at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/users

[Greg Bailey]

I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL certificates
in /usr/share/ssl, when the default CentOS 5 dovecot RPM uses
/etc/pki/dovecot.

I understand the whole RFX replaces base packages thing, but shouldn't
we try to preserve the configuration file locations? In this case an
upgrade changed default configuration in such a way as to break things...

I was also unable to log in via imap; I get:

dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with mbox
file /var/mail/username_goes_here: Permission denied

in /var/log/maillog. Apparently there's something else I need to change
here...

Thanks in advance for any advice with the dovecot upgrade!

-Greg

[Matthew Feinberg]

I second this motion. I had the same problem twice tonight with the SSL
location.

Matthew

Post by Greg Bailey
I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL
certificates in /usr/share/ssl, when the default CentOS 5 dovecot RPM
uses /etc/pki/dovecot.
I understand the whole RFX replaces base packages thing, but shouldn't
we try to preserve the configuration file locations? In this case an
upgrade changed default configuration in such a way as to break things...
dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with
mbox file /var/mail/username_goes_here: Permission denied
in /var/log/maillog. Apparently there's something else I need to
change here...
Thanks in advance for any advice with the dovecot upgrade!
-Greg
_______________________________________________
users mailing list
users at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/users

[Greg Bailey]

I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL certificates
in /usr/share/ssl, when the default CentOS 5 dovecot RPM uses
/etc/pki/dovecot.

I understand the whole RFX replaces base packages thing, but shouldn't
we try to preserve the configuration file locations? In this case an
upgrade changed default configuration in such a way as to break things...

I was also unable to log in via imap; I get:

dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with mbox
file /var/mail/username_goes_here: Permission denied

in /var/log/maillog. Apparently there's something else I need to change
here...

Thanks in advance for any advice with the dovecot upgrade!

-Greg

[Matthew Feinberg]

I second this motion. I had the same problem twice tonight with the SSL
location.

Matthew

Post by Greg Bailey
I recently upgraded dovecot to 1.0.13-1.el5.rfx, and my SSL setup was
broken, as apparently the newer dovecot expects to find SSL
certificates in /usr/share/ssl, when the default CentOS 5 dovecot RPM
uses /etc/pki/dovecot.
I understand the whole RFX replaces base packages thing, but shouldn't
we try to preserve the configuration file locations? In this case an
upgrade changed default configuration in such a way as to break things...
dovecot: IMAP(username_goes_here): file_lock_dotlock() failed with
mbox file /var/mail/username_goes_here: Permission denied
in /var/log/maillog. Apparently there's something else I need to
change here...
Thanks in advance for any advice with the dovecot upgrade!
-Greg
_______________________________________________
users mailing list
users at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/users