Ownership of /etc/authlib/authdaemonrc is daemon:daemon. Permissions are 0660.
Ownership of /etc/authlib/authdaemonrc.dist is courier:courier. Permissions are 0660. After changing the filter setting using WebAdmin but before installing the changes, I found a zero byte authdaemonrc file in /etc/courier/webadmin/. Ownership of that file is courier:courier and permissions are 0644. Sam Varshavchik writes: > Stan Minify writes: > >> 6. I looked at the authdaemonrc.dist file and it seemed to be a valid >> file >> so I copied it to authdaemonrc and restarted courier-authlib and courier. >> I > > When you did that, did you take care to preserve the ownership and the > permissions on the authdaemonrc file? authdaemonrc's ownership and > permissions need to be the same as authdaemonrc.dist -- it should be mode > 0660, and owned by the Courier userid (usually daemon, for rpm builds). > >> 9. I also noticed the following in maillog: >> >> Feb 15 21:44:52 mail authdaemond: libauthpipe.so: cannot open shared >> object file: No such file or directory >> >> Since I do not use authpipe and also do not use authpgsql, authmysql or >> authcustom, I figured I would remove these from authdaemon. The >> _one_and_only_ line I modified in authdaemonrc was the line starting with >> authdaemonlist. I _did_not_ modify the line authdaemonlistorig. > > Ok, fine. The above diagnostic is informational. It does no harm removing > authpipe, but it does no benefit either. > >> I hope this is clear. I will certainly do whatever it takes to clarify >> anything. >> >> Should I just run the whole rpmbuild -ta / rpm -i process again. Will I >> need to blow out the current files and directories if I do that? > > No, I think it would be a waste of time. It's not clear what the problem > is; experience indicates that making random attempts to fix a problem > that's not clearly understood does not often really fix anything. > > Some settings on the webmail configuration screen do involve updating > authdaemonrc. The webadmin interface uses a direct, no-frills approach. > The current settings are shown. When the screen is saved, all settings on > the screen are saved in the corresponding configuration file. Little is to > be gained by checking whether or not each individual setting was changed. > All settings are simply saved back to their original configuration files. > > Saving an individual settings to a given config file involves reading the > existing contents of the config file, inserting the new value, then > writing out the new file. The new file does not immediately replace the > existing configuration file. This occurs only after selecting "Install new > configuration" from the main menu. > > It's not clear why you're having a problem. One data point that needs to > be collected is whether the problem occurs when saving the new file, or > when installing it. > > The new file is saved to /etc/courier/webadmin/added directory (for rpm > builds). After saving your updated webmail configuration, but before > installing it, check the /etc/courier/web/admin/added directory, and see > what the new authdaemonrc file there contains. > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
