This is kind of a followup of bug 10650 (notice the similar title ;)). I think the standard is to have all config files in /etc. When I do an upgrade of sasl2 (or replace), my stmpd.conf is always replaced without any warning. In my case, the default config doesn't work. I then have to battle to find out why postfix stopped authenticating which can be hard if I forget about this config file. What about putting smtpd.conf back in /etc and put a symbolic link in /usr/lib/sasl2? No patch in sasl, no config silently overridden, and follow the standard
I updated my server to postfix-2.0.9 and got bitten by this bug again, my stmpd.conf file was again replaced in my back without any warning. Had to recover the file from the backup
Marking critical since there is data loss.
You mail folks able to take this one?
Im not sure if this should be posted here, but im using cyrus-sasl and when i go like this: /etc/init.d/saslauthd start it complains that there is not /var/lib/sasl2 and thats because portage installed it into /usr/lib/sasl2 If i make a symlink from /usr/lib/sasl2 to /var/lib then everything works properly.
seeing as how old this bug is, I'll look into it
please test 2.0.11 and report. sorry I didn't get it before raker upgraded the thing to *stable*. sheesh.
Stable? I don't see any new postfix in stable. 2.0.11 is still marked ~x86. Which bring up this question: how stable is the new version? I have only one gentoo machine and it's the company's server. How likely am I to break it if I test the new package? Going from 2.0.9 to 2.0.11 seems safe enough but I prefer to ask.
I'm not sure how stable postifx-2.0.11 is. I've been running 2.0.3 for months. I'm not upgrading unless I have a really good reason to do so. I did however talk to lolo today about the ebuild. It's getting fixed shortly. Until then make sure you backup your smtp.conf file. Or better yet, just symlink it into /etc/sasl2.
Works as it should (file in /etc/sasl, symlink in /usr/lib/sasl2) on a clean install or where this setup ( /etc/sasl, symlink /usr/lib/sasl2) already exists. In my setup though, it still overwrites my sasl config because I have the real file in /usr/lib/sasl2, and a symlink in /etc/sasl. Some others might have this setup from the cyrus-sasl bug. I have my real file in /usr/lib/sasl2 because that is where cyrus looks for it, and that is where it should be. If I am fooled into thinking it should be in /etc/sasl, and somehow the symlink gets nerfed, I can imagine pulling my hair out wondering why sasl isn't working, when I have all the settings right ;) Anyway, net result, it works as expected unless you have the symlinks reversed in your existing install.
Off Topic, but in regards to the postfix version, the patch levels are official releases, and do not change except for bugfixes and for portability fixes. I like bugfixes, and since Wietse think's it stable I always upgrade (it's now up to r12) to get the bug fixes. The only thing you have to worry about is anything the ebuild itself might do different between versions, not postfix itself.
Ok, so here's my theory, if the user already has a REAL /usr/lib/whatever/conffile then move the new one in /etc to a ._cfg file THEN move their REAL file to /etc and make a link in /usr/lib... IF they have a real file in BOTH locations display a warning, but overwrite NOTHING, thoughts?
Sounds good.
Ok, I'm now confused... having taken a closer look at this, it looks like it should be OK the way it is... I'm not sure how it's still clobbering any config files...
I set my system back up again in the original method and installed postfix-2.0.11.ebuild. There was a twist I didn't notice before, but the results are still the same. Before Ebuild: Config file: /usr/lib/sasl2/smtpd.conf Link to it in: /etc/sasl2/smtpd.conf Contents: pwcheck_method=saslauthd After Ebuild Config file: /etc/sasl2/smtpd.conf Link to it in: /etc/sasl2/smtpd.conf Contents: pwcheck_method=pam --- So, it has messed up my config file - My postfix authentications are now setup for pam, and will fail (I use saslauthd). Here is the twist I didn't notice - There is a ._cfg0000_smtpd.conf file that has the contents of my old smtpd.conf file (pwcheck_method=saslauthd). My ebuild is dated Jun 13, 05:21
This should be all totally fixored as of late, closing... IF this is not the case feel free to either re-bug me directly OR REOPEN this bug.
