Re: [vchkpw] Untie vpopmail from qmail
This has been gone over a few times in the past. Search the archives for the technical reasons. But every time this question comes up it's been a no. t - Original Message - From: Christopher Chan christop...@ias.com.hk To: vchkpw@inter7.com vchkpw@inter7.com Sent: Wed Aug 26 20:16:40 2009 Subject: [vchkpw] Untie vpopmail from qmail Hello all, Is this at all possible? Right now I use postfix and I only have a qmail queue just for vpopmail to install but qmail is otherwise not at all involved. cheers, Christopher !DSPAM:4a96238732716974711767!
[vchkpw] Re: Untie vpopmail from qmail
Christopher, Will you report your findings here, or at least links to the pertinent archive posts? I'm curious about this, but not enough so to do the searching. Tren Blackburn wrote: This has been gone over a few times in the past. Search the archives for the technical reasons. But every time this question comes up it's been a no. t - Original Message - From: Christopher Chan christop...@ias.com.hk To: vchkpw@inter7.com vchkpw@inter7.com Sent: Wed Aug 26 20:16:40 2009 Subject: [vchkpw] Untie vpopmail from qmail Hello all, Is this at all possible? Right now I use postfix and I only have a qmail queue just for vpopmail to install but qmail is otherwise not at all involved. cheers, Christopher -- -Eric 'shubes' !DSPAM:4a9678ca32711151996267!
Re: [vchkpw] Untie vpopmail from qmail
Tren Blackburn wrote: This has been gone over a few times in the past. Search the archives for the technical reasons. But every time this question comes up it's been a no. Guess who asked? :-D Anyway, qmail is public domain now so fixing up a package ain't an issue anymore. I will just drop this. /var/qmail/control ain't a bad place to put configuration files anyway. :-D t - Original Message - From: Christopher Chan christop...@ias.com.hk To: vchkpw@inter7.com vchkpw@inter7.com Sent: Wed Aug 26 20:16:40 2009 Subject: [vchkpw] Untie vpopmail from qmail Hello all, Is this at all possible? Right now I use postfix and I only have a qmail queue just for vpopmail to install but qmail is otherwise not at all involved. cheers, Christopher !DSPAM:4a968d0032711969777587!
Re: [vchkpw] Untie vpopmail from qmail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christopher Chan wrote: Hello all, Is this at all possible? Right now I use postfix and I only have a qmail queue just for vpopmail to install but qmail is otherwise not at all involved. We'd love to see vpopmail work with Postfix, but I just don't have enough experience with Postfix to do this. It would be nice for vpopmail to have a 'forward-end' module for working with different MTAs, but as I said, my Postfix experience is rather limited. Is there anyone with sufficient Postfix experience, and development experience, who is interested in working on this? - -- /* Matt Brookings m...@inter7.com GnuPG Key FAE0672C Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqWpLgACgkQIwet2/rgZyykCACfbAhFOPUZ2SqzWEq9g2nlrlge WlIAnilf8zJPQt2iaUfsJujxEjgsXwh1 =wGd5 -END PGP SIGNATURE-
[vchkpw] Re: Untie vpopmail from qmail
Christopher Chan wrote: Eric Shubert wrote: Christopher, Will you report your findings here, or at least links to the pertinent archive posts? I'm curious about this, but not enough so to do the searching. Which part are you curious about? postfix 'directly' hitting the vpopmail mail store and using the /var/qmail/control/* files for configuration or trying to untie vpopmail from qmail? Untying vpopmail from qmail. -- -Eric 'shubes' !DSPAM:4a96a74132711668415081!
Re: [vchkpw] vdelivermail fault with 5.4.28
On Tuesday 25 August 2009 04:23:48 pm Matt Brookings wrote: Steve Cole wrote: Moving to the new vpopmail (with the identical CFLAGS configure options for 5.4.23 that I've been using for a long time), I get: What CFLAGS and configure options are you using? ./configure --enable-valias --enable-auth-module=mysql hostname = zeus uname -m = x86_64 uname -r = 2.6.30.5 uname -s = Linux uname -v = #1 SMP Mon Aug 17 11:03:52 EDT 2009 CFLAGS=-Os -pipe -fomit-frame-pointer GCC 4.3.4 !DSPAM:4a96aaa532714587391783!
Re: [vchkpw] vdelivermail fault with 5.4.28
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Cole wrote: CFLAGS=-Os -pipe -fomit-frame-pointer Remove these CFLAGS and try again. Let me know how it goes. I can't reproduce this issue unfortunately. If you can, and would like to contact me off-list to give me access to the environment so I can debug it, that would be highly appreciated. - -- /* Matt Brookings m...@inter7.com GnuPG Key FAE0672C Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqWrDQACgkQIwet2/rgZyymBgCfXIQbyj3Jh49dQB+Lwke9YYD3 umkAnisiRXSzolKSY2a6/GthlPOv+ed3 =qdMf -END PGP SIGNATURE-
Re: [vchkpw] Untie vpopmail from qmail
Matt Brookings wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christopher Chan wrote: Hello all, Is this at all possible? Right now I use postfix and I only have a qmail queue just for vpopmail to install but qmail is otherwise not at all involved. We'd love to see vpopmail work with Postfix, but I just don't have enough experience with Postfix to do this. It would be nice for vpopmail to have a 'forward-end' module for working with different MTAs, but as I said, my Postfix experience is rather limited. Right now I can use either maildrop or dovecot's lda with postfix. No injecting into a qmail queue for final delivery into the vpopmail mail store. Are you saying you would like a vpopmail lda for postfix? Something that supports dot-qmail rather than whatever maildrop or dovecot provides? !DSPAM:4a971a9232713628818702!
Re: [vchkpw] Untie vpopmail from qmail
Matt Brookings wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christopher Chan wrote: Hello all, Is this at all possible? Right now I use postfix and I only have a qmail queue just for vpopmail to install but qmail is otherwise not at all involved. We'd love to see vpopmail work with Postfix, but I just don't have enough experience with Postfix to do this. It would be nice for vpopmail to have a 'forward-end' module for working with different MTAs, but as I said, my Postfix experience is rather limited. Is there anyone with sufficient Postfix experience, and development experience, who is interested in working on this? I've never used Postfix, and I haven't looked at how you modularized the back ends, but here is what I'd do... o Search through vpopmail code for anything that interacts directly with qmail.[1] Move the code into mta_qmail.[ch] or some such, and put it into a function.[2] Comment well! Replace the code in the original location with a function call. Test. o Take qmail.[ch] and comment out all the qmail specific code, leaving in the comments and any logic that fits in the MTA back-end creating mta_skeleton.[ch]. o Copy mta_skeleton.[ch] to mta_postfix.[ch] and fill out the functions as needed by Postfix. This is the only part that takes a Postfix expert. o Adjust the build system so you can select the MTA back end the same way you select the authentication back end. Nothing to it... but time. :) Rick p.s. Sorry I don't have time to look at it right now, but I have thought about the problem quite a bit. [1]. For the search, try replacing the include of qmail.h (or what ever it is called) with mta_qmail.h and only include the qmail headers in the MTA back end. You should now get compile errors everywhere you need to work. I think you will find most (all?) of the qmail related code in the areas that manage domains. [2]. You should be creating functions like mta_add_domain(), mta_del_domain() and mta_get_domain info(). Nice high level functions with as much of the code from libvpopmail grouped into the smallest number of functions possible. If you find a situation where a program like qmail is calling a function that resides in an authentication back end, you should move the function to vpopmail.c and change the name in the back end. Move the qmail related code to the MTA back end, and call the back end functions as needed from vpopmail.c. It should end up like this: qmail | | libvpopmail (in vpopmail.c) / \ /\ / \ /\ auth back mta back end end !DSPAM:4a97572e32711745671915!
