Re: [vchkpw] dumb question - courier/vchkpw/mysql
On Wednesday 11 August 2004 03:20 pm, Paul Theodoropoulos wrote: > okay, hopefully this isn't too stupid a question. > > i'm needing to upgrade courier-imap. my vpopmail has been running off mysql > backend forever. when i configure courier, should i still use > --with-authvchkpw, or does my use of mysql mean it would be more direct to > just use --with-authmysql? (i'm aware courier will normally compile every > damned authentication method on the planet and its aunt, but i normally > disable all but the one i need). I believe the authvchkpw, cuz then it links against vpopmail and uses its. I'm not sure exactly how the mysql backend works, I'm sure you could hack it together to authenticate vpopmail mysql users, but I'm not sure how it works (for instance, pure-ftpd you tell it what sql queries to use to get information it needs, etc) -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 847.492.0470 int'l kitchen @ #qmail #gentoo on EFnet ++ scriptkitchen.com/qmail
[vchkpw] dumb question - courier/vchkpw/mysql
okay, hopefully this isn't too stupid a question. i'm needing to upgrade courier-imap. my vpopmail has been running off mysql backend forever. when i configure courier, should i still use --with-authvchkpw, or does my use of mysql mean it would be more direct to just use --with-authmysql? (i'm aware courier will normally compile every damned authentication method on the planet and its aunt, but i normally disable all but the one i need). or am i misunderstanding the mysql backend? Paul Theodoropoulos http://www.anastrophe.com http://www.smileglobal.com
Re: [vchkpw] dumb question! (QmailAdmin 1.2.x does require vpopmail 5.4.x)
On Apr 15, 2004, at 6:57 PM, Paul Theodoropoulos wrote: well, the potential show-stopper is the switch from aliases and forwarding to just forwarding in the new vpopmail. i use mysql, along with mysql valiases, QmailAdmin 1.2.1 supports managing MySQL-based valiases. QmailAdmin 1.0.25 and later includes contrib/alias2forward.pl, a utility for converting Maildir delivery in .qmail-alias files to email delivery. Vpopmail 5.4.1 includes dotqmail2valias for converting .qmail-alias files to MySQL valias table entries. so what happens to those 'embedded' aliases once i upgrade? automatically converted to properly functioning forwards? i suspect not.that's what makes it kind of a tough migration. They will continue to work (or not work) as they do now. Upgrading won't make the situation any worse than it already is. The latest QmailAdmin understands the Maildir-style aliases fine -- it just doesn't create them. -- 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] dumb question! (QmailAdmin 1.2.x does require vpopmail 5.4.x)
At 06:12 PM 4/15/2004, you wrote: On Apr 15, 2004, at 1:56 PM, Paul Theodoropoulos wrote: in lieu of upgrading my vpopmail installation from 5.3.18 to current (because of the relatively steep number of backend changes done that will require a tedious migration effort), i'm curious just how tightly coupled the current qmailadmin is to the current vpopmail - that is, if i upgrade only qmailadmin, while leaving vpopmail alone, am i asking for even more headaches, or fewer? From the QmailAdmin INSTALL file: QmailAdmin 1.2.0 and later requires Vpopmail 5.4.0 or later. Upgrading from 5.3.18 to 5.4.3 shouldn't result in a tedious migration effort. If you use MySQL, you'll need to create a file with the user/password settings (as opposed to editing vmysql.h). The "defaultdomain" has moved from a configure option to an external file. There really aren't a lot of other changes that I can recall... well, the potential show-stopper is the switch from aliases and forwarding to just forwarding in the new vpopmail. i use mysql, along with mysql valiases, so what happens to those 'embedded' aliases once i upgrade? automatically converted to properly functioning forwards? i suspect not.that's what makes it kind of a tough migration. Paul Theodoropoulos http://www.anastrophe.com
Re: [vchkpw] dumb question! (QmailAdmin 1.2.x does require vpopmail 5.4.x)
On Apr 15, 2004, at 1:56 PM, Paul Theodoropoulos wrote: in lieu of upgrading my vpopmail installation from 5.3.18 to current (because of the relatively steep number of backend changes done that will require a tedious migration effort), i'm curious just how tightly coupled the current qmailadmin is to the current vpopmail - that is, if i upgrade only qmailadmin, while leaving vpopmail alone, am i asking for even more headaches, or fewer? From the QmailAdmin INSTALL file: QmailAdmin 1.2.0 and later requires Vpopmail 5.4.0 or later. Upgrading from 5.3.18 to 5.4.3 shouldn't result in a tedious migration effort. If you use MySQL, you'll need to create a file with the user/password settings (as opposed to editing vmysql.h). The "defaultdomain" has moved from a configure option to an external file. There really aren't a lot of other changes that I can recall... -- 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/
[vchkpw] dumb question!
in lieu of upgrading my vpopmail installation from 5.3.18 to current (because of the relatively steep number of backend changes done that will require a tedious migration effort), i'm curious just how tightly coupled the current qmailadmin is to the current vpopmail - that is, if i upgrade only qmailadmin, while leaving vpopmail alone, am i asking for even more headaches, or fewer? Paul Theodoropoulos http://www.anastrophe.com
