[Dovecot] Slackware Dovecot recompile with SSL/TLS question
I am having some problems and was told to ask in this list to try and
get some help.
When asking elsewhere, I was told that I was too verbose, so I'll try to be as brief as possible, while still including all the pertinent info.
Slackware 13.1.0 Dovecot 2.0.8 Postfix 2.4.3 MySQL (virtual users) Spamassassin 3.3.1 ClamAV 0.97.1 (without Amavis) Have wild-card SSL certs and CA from GoDaddy
##"postconf -a"
cyrus dovecot
I compiled Dovecot without SASL support and need to re-compile it WITH SASL support, but I don't want to mess up my existing configuration. (I have it the way I want it as far as where it's installed, where the conf files are located, UID, GID settings, etc.)
Dovecot 2.0.13 is out and I would prefer to use the newer version assuming it doesn't have any problems that would prevent me from using it.
Is there a way to re-compile (or upgrade) so that it doesn't change any of my existing settings?
I would like to be able to bring it down, do upgrade, maybe copy some config files over the defaults etc, and bring it all back up within a few minutes instead of a week of tweaking and fixing stuff.
Is there a way to do something like this :
stop dovecot backup all dovecot conf files
./configure CPPFLAGS=-I/path/to/openssl LDFLAGS=-L/path/to/openssl --config_dir /etc/dovecot/dovecot.conf (or something like that..not sure what it actually is)
make sudo make install edit conf files to point to SSL certs start dovecot
IN CASE anything goes wrong, copy old config files back and restart dovecot to make it go back the way it was (only it's using the new 2.0.13 version)
any suggestions and/or tips on how-to do this would be greatly appreciated.
Thanks!
On Mon, Aug 15, 2011 at 06:07:37PM -0500, CopalFreak wrote:
Slackware 13.1.0 Dovecot 2.0.8 Postfix 2.4.3
That's rather old, BTW.
MySQL (virtual users) Spamassassin 3.3.1 ClamAV 0.97.1 (without Amavis) Have wild-card SSL certs and CA from GoDaddy
##"postconf -a"
cyrus dovecot
I compiled Dovecot without SASL support and need to re-compile it WITH SASL support,
The Subject line says "SSL/TLS", and then here you say "SASL". I suppose the Subject is correct, right? I don't recall there being options to enable/disable SASL in Dovecot.
but I don't want to mess up my existing configuration. (I have it the way I want it as far as where it's installed, where the conf files are located, UID, GID settings, etc.)
Dovecot 2.0.13 is out and I would prefer to use the newer version assuming it doesn't have any problems that would prevent me from using it.
Is there a way to re-compile (or upgrade) so that it doesn't change any of my existing settings?
Did you look at the wiki yet? Upgrading from one minor version to another should be rather simple. Check the NEWS. http://wiki2.dovecot.org/Upgrading http://dovecot.org/doc/NEWS
I would like to be able to bring it down, do upgrade, maybe copy some config files over the defaults etc, and bring it all back up within a few minutes instead of a week of tweaking and fixing stuff.
Spend some time in advance, and this should be simple.
Is there a way to do something like this :
stop dovecot
No, this is too early in the process. Compile first.
backup all dovecot conf files
./configure CPPFLAGS=-I/path/to/openssl LDFLAGS=-L/path/to/openssl --config_dir /etc/dovecot/dovecot.conf (or something like that..not sure what it actually is)
make
Here's where you'd "dovecot stop".
sudo make install edit conf files to point to SSL certs
Actually you can edit the modular /etc/dovecot/conf.d/10-ssl.conf file ahead of time, then just uncomment the include line at this point.
start dovecot
IN CASE anything goes wrong, copy old config files back and restart dovecot to make it go back the way it was (only it's using the new 2.0.13 version)
any suggestions and/or tips on how-to do this would be greatly appreciated.
You might gain some confidence by doing this in a virtual machine and/or chroot in advance.
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: headerOn Mon, Aug 15, 2011 at 09:21:22PM -0500, I wrote stuff under this header: Reply-To: dovecot@dovecot.org
List mail belongs on the list. The only reason to reply offlist as described below is if specifically requested, or if not relevant to the issue at hand. I have no particular interest in this nor any other problem posted on list unless I have been hired to fix it.
I see offlist mail as detailed below in the .sig, but I won't participate in offlist discussions which belong on the list.
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
participants (2)
-
/dev/rob0
-
CopalFreak