On 12-12-13 14:09, Ken Drummond wrote:
> Hi,
>
> I am a gentoo user and having been successfully using dbmail 2.2.17 for
> quite a while now with mysql. I am finally upgrading to 3.1.7 and I
> have read what I can find about the steps to upgrade. I'd appreciate it
> if you could have a look at the steps I have set out.
>
> My basic plan is
>
> 1. stop postfix (I have a couple of VPS's that provide backup_mx)
> 2. stop dbmail
> 3. (make a backup, I have regular backups running at 2:00am so not a
> huge issue)
> 4. emerge -DNu dbmail (gentoo to upgrade to latest dbmail 3.1.7)
> 5. run mysql -p dbmail <
> /usr/share/doc/dbmail-3.1.7/sql/mysql/2_2-3_0.mysql
> 6. run mysql -p dbmail <
> /usr/share/doc/dbmail-3.1.7/sql/mysql/3_0_2-3_1_0.mysql
> 7. run dbmail -by
> 8. restart dbmail
> 9. restart postfix
looking good.
> My main question is, is it safe to execute steps 8 and 9 without waiting
> for step 7 to finish? I have done some testing on a backup server and
> dbmail -by has been running for over 24 hours (and is still going). I
> have restarted dbmail and postfix on that machine and it appears to
> work, noting that most old mail doesn't show sender, subject etc. which
> will no doubt reappear when dbmail -by completes. This is not a huge
> issue but it would be good if I could access new mail without having to
> wait 1/2/3??? days.
It's safe. As to the side-effects, I think you answered that yourself.
>
> I also have another question about imap ssl? I see that there are 2
> options in the [IMAP] section of dbmail.conf, port and tls_port is it
> possible to have both of these set so that I can use port 143 without
> encryption as well as having tls_port set to 993 to use ssl at the same
> time as using unencrypted imap on 143.
Yes. If you specify both ports and provide a valid certificate
(self-signed *is* valid) you can handle both unencrypted and encrypted
traffic.
However, in that case, connections on port 143 will require a STARTTLS
command by default before allowing authentication. On the master branch
soon to become 3.2.0 you will be able to set the 'login_disabled=no'
option to allow unencrypted authentication.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, github, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/[email protected]/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
