[vchkpw] Re: vpopmail-5.4.13

2006-01-17 Thread drew-vpopmail
I could not figure out why only MySQL can now be used for valias only, so I just created a patch to 5.4.13 to remove this check (I still use valias in the form of .qmail files). Patch attached. diff -uPr vpopmail-5.4.13.orig/configure vpopmail-5.4.13/configure --- vpopmail-5.4.13.orig/configure

Re: [vchkpw] VPOPMAIL Backup

2006-01-17 Thread Rick Macdougall
John Simpson wrote: On 2006-01-04, at 1229, Rick Macdougall wrote: Michl wrote: Hi all, i need to setup a configuration backup for all my vpopmail domains, vpopmail settings, and qmail settings. What are the files I need to store in my backup to get a quickly disaster recovery? For qmail

Re: [vchkpw] vpopmaild status?

2006-01-17 Thread Tom Collins
On Jan 16, 2006, at 11:30 PM, John Simpson wrote: i'm wondering about vpopmaild... i plan on writing a patch for qmail-smtpd which will make it connect to vpopmaild in order to handle the AUTH command (basically try to login and use the + or - response to approve or deny the AUTH command.) my

Re: [vchkpw] Re: vpopmail-5.4.13

2006-01-17 Thread Tom Collins
On Jan 17, 2006, at 1:30 AM, [EMAIL PROTECTED] wrote: I could not figure out why only MySQL can now be used for valias only, so I just created a patch to 5.4.13 to remove this check (I still use valias in the form of .qmail files). Patch attached. The valias option to configure should

Re: [vchkpw] Re: vpopmail-5.4.13

2006-01-17 Thread Tom Collins
On Jan 12, 2006, at 9:28 AM, Sandeep Agarwal wrote: Release-notes for 5.4.13 says this Tom Collins - configure.in: fix checks to limit enable-valias to MySQL only. but why postgres support is pulled out ?? That was an accident -- I forgot that postgres had valias code as well. It's back in

[vchkpw] Vpopmail 5.4.14 released (finally)

2006-01-17 Thread Tom Collins
http://vpopmail.sf.net/ 5.4.14 - released 17-Jan-06 This release brings in the vpopmail daemon (vpopmaild) from the 5.5 development series, and fixes a few bugs from 5.4.13. If you're running 5.4.13 and don't need vpopmaild, take a look at tracker #1360346 on SourceForge to get an important

Re: [vchkpw] Vpopmail 5.4.14 released (finally)

2006-01-17 Thread Steve Cole
On Tuesday 17 January 2006 14:50, Tom Collins wrote: This release brings in the vpopmail daemon (vpopmaild) from the 5.5 development series, and fixes a few bugs from 5.4.13. Bad news... -- cut libvpopmail.a(libvpopmail_a-vpalias.o): In function `valias_select_next':vpalias.c:(.text+0x0):

Re: [vchkpw] Vpopmail 5.4.14 released (finally)

2006-01-17 Thread Tom Collins
On Jan 17, 2006, at 12:40 PM, Steve Cole wrote: This release brings in the vpopmail daemon (vpopmaild) from the 5.5 development series, and fixes a few bugs from 5.4.13. Bad news... Can you email me your configuration options? In particular, I need to know which backend (cdb, mysql,

Re: [vchkpw] Vpopmail 5.4.14 released (finally)

2006-01-17 Thread Steve Cole
On Tuesday 17 January 2006 15:48, Tom Collins wrote: Bad news... Can you email me your configuration options? In particular, I need to know which backend (cdb, mysql, postgres) and whether you have --enable-valias selected. --enable-valias --enable-auth-module=mysql

Re: [vchkpw] Vpopmail 5.4.14 released (finally)

2006-01-17 Thread Joshua Megerman
On Jan 17, 2006, at 12:40 PM, Steve Cole wrote: This release brings in the vpopmail daemon (vpopmaild) from the 5.5 development series, and fixes a few bugs from 5.4.13. Bad news... Can you email me your configuration options? In particular, I need to know which backend (cdb, mysql,

Re: [vchkpw] Vpopmail 5.4.14 released (finally)

2006-01-17 Thread Tom Collins
On Jan 17, 2006, at 1:05 PM, Joshua Megerman wrote: It appears that you are linking both the vmysql valias_select* and the vpalias valias_select* object code into libvpopmail.a, resulting in the compile error. I'm not sure what changed, but obviously it's Not Good(tm) :( And I'm missing