FS#8358 - [courier-mta] broken after last update
Attached to Project:
Arch Linux
Opened by Gerhard Brauer (GerBra) - Saturday, 20 October 2007, 08:18 GMT
Last edited by Tobias Kieslich (tobias) - Monday, 07 January 2008, 22:17 GMT
Opened by Gerhard Brauer (GerBra) - Saturday, 20 October 2007, 08:18 GMT
Last edited by Tobias Kieslich (tobias) - Monday, 07 January 2008, 22:17 GMT
|
Details
Description:
After update the new package still overwrite some configuration settings and make courier unusable. Afftected file is /etc/courier/esmtpauthclient which stores auth data ex. for extern mail relaying. Additional info: * package version(s) courier-mta (0.55.1-1 -> 0.55.1-2) updated Solution: Backup esmtpauthclient also like the other config files. Also it would be IMHO a better way not only backup user configs somewhere but also restore these backuped files after update. |
This task depends upon
Closed by Tobias Kieslich (tobias)
Monday, 07 January 2008, 22:17 GMT
Reason for closing: Fixed
Additional comments about closing: I stay with the homemade simple backup, since courier needs special ways
Monday, 07 January 2008, 22:17 GMT
Reason for closing: Fixed
Additional comments about closing: I stay with the homemade simple backup, since courier needs special ways
(First: sorry for my bad english)
I don't agree with that ;-)
During this update for example not restoring the old configuration (it was aliases and smtpaccess in _backup,
and the not saved esmtpauthclient) result in a *definitely* broken mta (courier restart itself in intervals).
If you restore these user settings there is *mostly* a chance that courier works after that.
For this update ex. there are IMHO no significantly changes from backup to new files.
Or maybe better: Put *new* configs in a manner like .PACNEW in /etc/courier - or when this is not possible
(ex. on dirs in which courier parse ALL files) maybe a structute like /etc/courier/_newetc, where all
new or default configs from update goes.
And so don't update any config in the actually running courier but put the admins eyes on that - as you
do already during .INSTALL.
If the updated (not restarted courier) doesn't work with the currerent, admin-changed, config the admin
surely will notice that and do his work.
But above is more a general discussion. For this current bugreport it's important that we backup *all*
config files which a user maybe could have changed.
The user can decide if s/he wants all configuration in one file such as /etc/courier/aliases or if it should be broken up into subfiles (/etc/courier/aliases/*) In the latter case courier concatenates al files in this directory (and possible subdirectories IIRC) into one file before it reads it as configuration. This leaves us with two problems:
1. what do we backup? files or directories
2. we can't use .pacnew .pacold and what so ever files, because courier would read them as part of the directory and gets confused with the content.
esmtpauthclient might be a candidtate for backups=(), but firstly I have to investigate how courier smart reading functions effect that.