Re: [vchkpw] Re: vpopmail FHS compliance
proftpd-1.3.2-0.4.rc3.fc11.i586.rpm (info) (download) proftpd-ldap-1.3.2-0.4.rc3.fc11.i586.rpm (info) (download) proftpd-mysql-1.3.2-0.4.rc3.fc11.i586.rpm (info) (download) proftpd-postgresql-1.3.2-0.4.rc3.fc11.i586.rpm (info) (download) Again, I'm not sure how this makes it much easier for people packaging. Even if you went with the module system, you'd have to compile each module seperately. The packages above, even at the very least, provide a new module. The same could be done by ./configure --enable-auth-module=x make. Matt, The trick here is that by separating out the back-end authentication schemes into modules, you can provide a single source build for package maintainers, which will generate multiple component packages for the whole setup. Then they don't have to maintain separately configured source trees and builds for each authentication module, but can do a single build that can be configured at runtime to use any available (i.e., installed) module. The user then can install just the module(s) that they want and configure them at will without having to uninstall and then install the new package. If you were to provide authentication packages for vpopmail, they'd replace libvpopmail and the binaries. For the 5.5 tree, you can link against the shared object files if you choose to as well, meaning packages would only need to replace libvpopmail.so, or even just a symlink to a different library. Again, the authentication modules would be removed from libvpopmail.so, and libvpopmail.so would load the appropriate library (e.g. libvpopmail_authtype.so) based on the vpopmail configuration. Modules are not out of the question, but I'm not shooting for them in the near future. vpopmail as a project just doesn't need them very badly right now. I think that depends on the direction that you want to take vpopmail in. If you're just aiming to update the code, fix bugs, and add needed functionality, then you're probably right. If you're looking to expand the scope of vpopmail usage and deployments (which binary packages will inevitably do as users who don't want to custom-compile things start making use of it), then modularizing the authentication systems is probably the second most important thing to do, after fixing any bugs that might be lurking in the code right now, especially in the back-ends. Also, by creating a modular vpopmail-backend API, you could even break the authentication components out of the vpopmail code tree so that other people could easily maintain and even add new back-end support. Again, I don't know what your goal is, so that will certainly influence how you want to prioritize things. If someone wants to write a patch against the 5.5 tree, I'll look into it and if the code is done well, I will consider adding it, but it was not in my plan for 5.5. Fair enough. I can't remember if you've done it or not, but if you haven't you might want to consider posting a to-do/wish list/roadmap for vpopmail development so that people can assist with and/or comment on where things are going. Thanks for working to make vpopmail better! Josh Joshua Megerman SJGames MIB #5273 - OGRE AI Testing Division You can't win; You can't break even; You can't even quit the game. - Layman's translation of the Laws of Thermodynamics j...@honorablemenschen.com !DSPAM:49c1187a32689657416453!
Re: [vchkpw] Deleting primary domain; keeping alias domains
Good morning, On 18/03/09 at 9:31 AM -0500, Matt Brookings m...@inter7.com wrote: Charlie Garrison wrote: Is there a proper way to delete a domain which is currently configured as the primary domain for an account? And I want one of the current domain aliases to become the primary domain. I can't find any comprehensive documentation for vdeldomain. Maybe it will do what I want; I don't have a test system to try it on though. An alias is just that, an alias. It is not an actual domain. If you delete the primary, the alias will not function because there is no primary domain data for it to alias. I guessed that, which is why I was asking how to delete the primary domain. I want one of the domain aliases to become the primary domain. Is there any way to do that short of completely recreating the setup for that domain/directory? The primary domain is no longer in use (has expired) and I would like to completely remove all references to it. My thought was to 'mv' the domain directory to the name of the domain alias, and manually edit the qmail/users/assign file accordingly. But I don't know if there are other locations where the primary domain name is stored that would also need to be updated. (I'm ignoring rcpthosts, etc for now since they seem to be easy changes.) Thanks, Charlie -- Charlie Garrison garri...@zeta.org.au PO Box 141, Windsor, NSW 2756, Australia O ascii ribbon campaign - stop html mail - www.asciiribbon.org http://www.ietf.org/rfc/rfc1855.txt !DSPAM:49c1189632686147620501!
Re: [vchkpw] Deleting primary domain; keeping alias domains
Here is how you could make it work with the mv Backup all your data. Remove the domain and alias create a new domain and all users for that domain cp or mv all that mgs into the new domain. It should be fine for you. Just my 2 cents. Remo From: Charlie Garrison garri...@zeta.org.au Reply-To: vchkpw@inter7.com Date: Thu, 19 Mar 2009 02:51:46 +1100 To: vchkpw@inter7.com Subject: Re: [vchkpw] Deleting primary domain; keeping alias domains Good morning, On 18/03/09 at 9:31 AM -0500, Matt Brookings m...@inter7.com wrote: Charlie Garrison wrote: Is there a proper way to delete a domain which is currently configured as the primary domain for an account? And I want one of the current domain aliases to become the primary domain. I can't find any comprehensive documentation for vdeldomain. Maybe it will do what I want; I don't have a test system to try it on though. An alias is just that, an alias. It is not an actual domain. If you delete the primary, the alias will not function because there is no primary domain data for it to alias. I guessed that, which is why I was asking how to delete the primary domain. I want one of the domain aliases to become the primary domain. Is there any way to do that short of completely recreating the setup for that domain/directory? The primary domain is no longer in use (has expired) and I would like to completely remove all references to it. My thought was to 'mv' the domain directory to the name of the domain alias, and manually edit the qmail/users/assign file accordingly. But I don't know if there are other locations where the primary domain name is stored that would also need to be updated. (I'm ignoring rcpthosts, etc for now since they seem to be easy changes.) Thanks, Charlie -- Charlie Garrison garri...@zeta.org.au PO Box 141, Windsor, NSW 2756, Australia O ascii ribbon campaign - stop html mail - www.asciiribbon.org http://www.ietf.org/rfc/rfc1855.txt !DSPAM:49c1203032681502410438!
Re: [vchkpw] Re: vpopmail FHS compliance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joshua Megerman wrote: The trick here is that by separating out the back-end authentication schemes into modules, you can provide a single source build for package maintainers, which will generate multiple component packages for the whole setup. Then they don't have to maintain separately configured source trees and builds for each authentication module, but can do a single build that can be configured at runtime to use any available (i.e., installed) module. The user then can install just the module(s) that they want and configure them at will without having to uninstall and then install the new package. I see. That makes a bit more sense. I don't maintain any binary package distributions, so I'm not really familiar with the process. My assumptions about it were incorrect I guess :) Fair enough. I can't remember if you've done it or not, but if you haven't you might want to consider posting a to-do/wish list/roadmap for vpopmail development so that people can assist with and/or comment on where things are going. Thanks for working to make vpopmail better! I'll probably look into what it will take to move the authentication backends into modules for the 5.5 branch. Thanks for your input. - -- /* Matt Brookings m...@inter7.com GnuPG Key D9414F70 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 iEYEARECAAYFAknBIrAACgkQ6QgvSNlBT3D/BACfWi1UUu9Mc0L6KjanRqS4kx/B NlQAoKD3/VcrThiVtf6Dvf9ifeR6vfGn =C6Er -END PGP SIGNATURE-
Re: [vchkpw] Re: vpopmail FHS compliance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Itamar Reis Peixoto wrote: Josh thanks for explaining the things for me, my english is not good making vpopmail support loadable module support will bring vpopmail into linux distros (fedora, opensuse, mandriva) and probably others and make the vpopmail userbase grow. I appreciate your input. I'm just not very familiar with binary distribution maintenance. I will be looking into this further. Thanks! - -- /* Matt Brookings m...@inter7.com GnuPG Key D9414F70 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 iEYEARECAAYFAknBIwAACgkQ6QgvSNlBT3B0rwCgpjypmND3h9aDEmareRWcwHCN tfoAniZdGJs0pvzUNtf6AeQ4My+zs+7L =jfMG -END PGP SIGNATURE-
Re: [vchkpw] Deleting primary domain; keeping alias domains
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joshua Megerman wrote: environment. When in doubt, DON'T DO THIS. Now, if you just want to stop receiving email for the primary domain and not delete it completely, take your server out of the MX entry, point the domain A record somewhere that doesn't accept mail, and/or add the domain to qmail's badmailto file (assuming you have that patch installed). While there are several ways to rename a domain, which is essentially what is being done here, the best question to ask one's self before beginning this very manual process, is if you NEED to, and if you have the experience with your backend database selection, and with qmail. The only time you really NEED to do this is if the domain is hosted on a remote site now, and the users of this system need to be able to email the remote system. If your users of this domain own both domains, and simply want the new domain to 'be their primary', just tell them it's done, and to use the new domain name and leave everything as it is. I totally agree - in my case I was hosting a subdomain of a domain that the company wasn't renewing the registration on and I really didn't want to be hosting a domain we didn't own anymore. Plus like I said it was small and still in testing (the decision to not renew the domain (and migrate the process to the other one) was made after the initial setup was completed with the original domain) I figured the worst case scenario was to delete the whole thing and start from scratch :) The instructions above look correct by the way :) Thanks! Josh Joshua Megerman SJGames MIB #5273 - OGRE AI Testing Division You can't win; You can't break even; You can't even quit the game. - Layman's translation of the Laws of Thermodynamics j...@honorablemenschen.com !DSPAM:49c1313232684641599795!
Re: [vchkpw] Re: vpopmail FHS compliance
Josh thanks for explaining the things for me, my english is not good You're welcome. making vpopmail support loadable module support will bring vpopmail into linux distros (fedora, opensuse, mandriva) and probably others and make the vpopmail userbase grow. Well, that's a rather simplified statement. After all, since vpopmail is currently tied to qmail, you also have to get qmail into the linux distros, and while much easier now that qmail is Public Domain, it's still not as simple as that given the current state of qmail and patches. But it is a step in that direction... Josh Joshua Megerman SJGames MIB #5273 - OGRE AI Testing Division You can't win; You can't break even; You can't even quit the game. - Layman's translation of the Laws of Thermodynamics j...@honorablemenschen.com !DSPAM:49c131df32681438719974!
Re: [vchkpw] Re: vpopmail FHS compliance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joshua Megerman wrote: The trick here is that by separating out the back-end authentication schemes into modules, you can provide a single source build for package maintainers, which will generate multiple component packages for the whole setup. Then they don't have to maintain separately configured source trees and builds for each authentication module, but can do a single build that can be configured at runtime to use any available (i.e., installed) module. The user then can install just the module(s) that they want and configure them at will without having to uninstall and then install the new package. I see. That makes a bit more sense. I don't maintain any binary package distributions, so I'm not really familiar with the process. My assumptions about it were incorrect I guess :) No problem - I don't do any package maintenance myself either, but it's always frustrated me that vpopmail could only support one back-end at a time, and that it was allmost all configured at compile-time... Fair enough. I can't remember if you've done it or not, but if you haven't you might want to consider posting a to-do/wish list/roadmap for vpopmail development so that people can assist with and/or comment on where things are going. Thanks for working to make vpopmail better! I'll probably look into what it will take to move the authentication backends into modules for the 5.5 branch. Thanks for your input. You're welcome - I don't have a lot of time for coding these days, but I've invested enough time in qmail/vpopmail that I want to see them succeed :) Josh Joshua Megerman SJGames MIB #5273 - OGRE AI Testing Division You can't win; You can't break even; You can't even quit the game. - Layman's translation of the Laws of Thermodynamics j...@honorablemenschen.com !DSPAM:49c132a332681600362347!
Re: [vchkpw] Re: vpopmail FHS compliance
that's a great , but qmail is no more maintaned (no new features) will be a good ideia to make vpopmail more compatible with postfix and maybe others MTA's Well, that's a rather simplified statement. After all, since vpopmail is currently tied to qmail, you also have to get qmail into the linux distros, and while much easier now that qmail is Public Domain, it's still not as simple as that given the current state of qmail and patches. But it is a step in that direction... Josh Itamar Reis Peixoto e-mail/msn: ita...@ispbrasil.com.br sip: ita...@ispbrasil.com.br skype: itamarjp icq: 81053601 +55 11 4063 5033 +55 34 3221 8599 !DSPAM:49c133e932681336914356!
Re: [vchkpw] Re: vpopmail FHS compliance
that's a great , but qmail is no more maintaned (no new features) will be a good ideia to make vpopmail more compatible with postfix and maybe others MTA's Ad that, my friend, is a horse of a totally different color. To the best of my knowledge there is no plan to make vpopmail work generically with MTAs other than qmail (Matt, please correct me if I'm wrong), as it currently is integrated rather tightly with how qmail does things. While I'm not disagreeing that expanding vpopmail's compatibility with other MTAs would expand it's acceptance, I also don't really see it happening without a complete internal rewrite to how vpopmail does things. Maybe something to roadmap for vpopmail 6? In any case, I wouldn't hold my breath :) Josh Joshua Megerman SJGames MIB #5273 - OGRE AI Testing Division You can't win; You can't break even; You can't even quit the game. - Layman's translation of the Laws of Thermodynamics j...@honorablemenschen.com !DSPAM:49c13c2332681437819685!
Re: [vchkpw] Re: vpopmail FHS compliance
Itamar Reis Peixoto wrote: that's a great , but qmail is no more maintaned (no new features) will be a good ideia to make vpopmail more compatible with postfix and maybe others MTA's Qmail is now in the public domain. You are free to add any new features you want. Regards, Rick !DSPAM:49c13c5f32681609681472!
