Re: [vchkpw] upgrading 5.3.30 to 5.4.x
On Fri, 9 Jul 2004, Tom Collins wrote: > The method of passing the CRAM-MD5 challenge and response from > qmail-smtpd to vchkpw has varied in different releases of the SMTP AUTH > patch to qmail-smtpd and the code if vchkpw. Just a quick note, perhaps this should be in the CHANGELOG or something. The new TLS/auth patch has a build target called "tmprsadh". As far as I can tell, this target was not in the old patch. If you do not specifically do a "make tmprsadh", you'll find that your TLS connections take forever to setup; so long that it may appear that something is broken. It's not, it's just some insanely slow encryption process going on. Once you make the target above, you get these additional files in /var/qmail/control: -rw-rw 1 vpopmail qmail 245 Jul 13 01:56 dh1024.pem -rw-rw 1 vpopmail qmail 156 Jul 13 01:51 dh512.pem -rw-rw 1 vpopmail qmail 493 Jul 13 01:51 rsa512.pem While I don't understand enough about TLS/SSL to explain it, having these files speeds things up quite a bit. Charles
Re: [vchkpw] upgrading 5.3.30 to 5.4.x
On Fri, 9 Jul 2004, Tom Collins wrote: > Someone, somewhere determined the proper order (based on documentation, > perhaps related to the chkpasswd(?) program used on non-vpopmail > systems) and the latest (0.42) SMTP AUTH patch and the code in vpopmail > 5.4.0 were both fixed. Excellent. Sounds fair enough. > You should be able to apply your super-patch-pack, then unpatch (patch > -r?) your original SMTP AUTH patch and then apply the latest patch. I looked at what I was doing (this is an old install) and found that Bill Shupp's mega-patch plus chkusr is really all I need. So I started over with netqmail and the latest patchsets. So far all is well under 5.3.30 with the updated qmail, so I'll be giving the upgrade a shot soon. > Hard to say. We started using an external file > (~vpopmail/etc/vpopmail.mysql) to store MySQL settings instead of > having them hard-coded in vmysql.h. Looks like I already had that. > If you've read through the ChangeLog entries, you should have seen any > critical issues. We started supporting valiases in MySQL fully in > vpopmail and qmailadmin (so you can replace aliases, forwards and > autoresponders in .qmail-alias files with MySQL table entries). Looked at each release from 5.3.30 - 5.4.6 and didn't see anything big beyond the smtp-auth issue. Until my db issues are sorted out I'll be declining on the valias stuff. :) I have to give PGSQL a shot sometime as well. It looks like people have been cleaning that up a bit. Thanks, Charles > -- > Tom Collins - [EMAIL PROTECTED] > QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ > Info on the Sniffter hand-held Network Tester: http://sniffter.com/ > >
Re: [vchkpw] upgrading 5.3.30 to 5.4.x
On Jul 9, 2004, at 12:08 PM, Charles Sprickman wrote: Out of curiousity, what has changed? My current super-patch-pack for qmail was quite difficult to put together, so I'm a litle hesitant to try and get the newer smtp-auth patches into that mess. Is there any way to continue with the old patch? What exactly has changed on the vpopmail side that breaks the old patch? The method of passing the CRAM-MD5 challenge and response from qmail-smtpd to vchkpw has varied in different releases of the SMTP AUTH patch to qmail-smtpd and the code if vchkpw. Someone, somewhere determined the proper order (based on documentation, perhaps related to the chkpasswd(?) program used on non-vpopmail systems) and the latest (0.42) SMTP AUTH patch and the code in vpopmail 5.4.0 were both fixed. You should be able to apply your super-patch-pack, then unpatch (patch -r?) your original SMTP AUTH patch and then apply the latest patch. And is there anything else I should be aware of when upgrading? Like I said, I didn't see anything major in the changelogs, but I'd still like to get some feedback from anyone who's made the jump to 5.4.x from 5.3.30. Hard to say. We started using an external file (~vpopmail/etc/vpopmail.mysql) to store MySQL settings instead of having them hard-coded in vmysql.h. If you've read through the ChangeLog entries, you should have seen any critical issues. We started supporting valiases in MySQL fully in vpopmail and qmailadmin (so you can replace aliases, forwards and autoresponders in .qmail-alias files with MySQL table entries). -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
Re: [vchkpw] upgrading 5.3.30 to 5.4.x
Charles Sprickman wrote: Hi, I've been looking through the release notes on all post 5.3.30 releases and so far I don't see any big "gotchas" except for this: http://marc.theaimsgroup.com/?t=10747937905&r=1&w=2 Out of curiousity, what has changed? My current super-patch-pack for qmail was quite difficult to put together, so I'm a litle hesitant to try and get the newer smtp-auth patches into that mess. Is there any way to continue with the old patch? What exactly has changed on the vpopmail side that breaks the old patch? And is there anything else I should be aware of when upgrading? Like I said, I didn't see anything major in the changelogs, but I'd still like to get some feedback from anyone who's made the jump to 5.4.x from 5.3.30. Hi, I have done three machines recently from 5.3.20 to 5.4.5 and I experienced no problems. Two machines used cdb and one used MySQL. I did it all based on Bill Shupp's patches, so I had no worries about my own patches. Regards, Rick
