Re: [vchkpw] vpopmail user/group
Christopher Chan wrote: Have you created the vpopmail user and vchkpw group? If not you must. Yes, I will create they when installing the package in my destination host. This is the why I need to get these values into the package when building. The build host isn't my dest host. That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts with postfix on Redhat distros. What is the problem? Just create the group and user with different values. It doesn't matter what the number is, it just has to exist when your run ./configure.
Re: [vchkpw] vpopmail user/group
Rick Widmer wrote: Christopher Chan wrote: Have you created the vpopmail user and vchkpw group? If not you must. Yes, I will create they when installing the package in my destination host. This is the why I need to get these values into the package when building. The build host isn't my dest host. That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts with postfix on Redhat distros. What is the problem? Just create the group and user with different values. It doesn't matter what the number is, it just has to exist when your run ./configure. Oh, the vpopmail uid and gid is not hardcoded into the binaries?
Re: [vchkpw] vpopmail user/group
Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Have you created the vpopmail user and vchkpw group? If not you must. Yes, I will create they when installing the package in my destination host. This is the why I need to get these values into the package when building. The build host isn't my dest host. That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts with postfix on Redhat distros. What is the problem? Just create the group and user with different values. It doesn't matter what the number is, it just has to exist when your run ./configure. Oh, the vpopmail uid and gid is not hardcoded into the binaries? The uid and gid are hard coded into the bianaries by ./configure.
Re: [vchkpw] vpopmail or qmail problem?
John Simpson ([EMAIL PROTECTED]) wrote: > for messages sent to "bob-clamav@", qmail-local looks for the > following files in the domain's directory: > > .qmail-bob-clamav > .qmail-bob-default > .qmail-default > .qmail Thanks, I thought I was going nuts, but thats how I understood it would process them too. [snip] > i would need to see > the UN-EDITED contents, ownerships, and permissions of the users/ > assign, .qmail-bob-clamav, .qmail-bob-default, and .qmail-default > files, along with the actual headers (again not edited, hiding domain > names doesn't serve any purpose) of a message which was incorrectly > delivered. Thanks for your assistance with this, i'll list those details below. jedi padawan.org # cat /var/qmail/users/assign +andycoates.com-:andycoates.com:89:89:/var/vpopmail/domains/andycoates.com:-:: +padawan.org-:padawan.org:89:89:/var/vpopmail/domains/padawan.org:-:: . jedi padawan.org # ls -l /var/qmail/users/assign -rw-r--r-- 1 root root 151 Oct 3 09:39 /var/qmail/users/assign The domain is padawan.org: jedi padawan.org # pwd /var/vpopmail/domains/padawan.org "bob" is "kindred" in my actual setup, as show below: -rw--- 1 vpopmail vpopmail 34 Oct 2 13:08 .dir-control -rw-r--r-- 1 vpopmail vpopmail 20 Jun 28 2006 .qmail-andy -rw--- 1 vpopmail vpopmail 43 Nov 13 2006 .qmail-default -rw--- 1 vpopmail vpopmail 43 Sep 27 15:49 .qmail-kindred-clamav -rw--- 1 vpopmail vpopmail 21 Sep 24 10:15 .qmail-kindred-default --wx--S--- 1 vpopmail vpopmail0 Oct 2 13:07 .vpasswd.lock drwx-- 3 vpopmail vpopmail 96 Oct 2 13:09 kindred drwx-- 3 vpopmail vpopmail 72 Feb 10 2006 postmaster -rw--- 1 vpopmail vpopmail 105 Oct 2 13:08 vpasswd -rw--- 1 vpopmail vpopmail 2175 Oct 2 13:08 vpasswd.cdb .dir-control and the vpasswd* files appeared after I turned mysql (thinking it was to do with vlias). jedi padawan.org # cat .qmail-kindred-clamav | /var/vpopmail/bin/vdelivermail '' delete jedi padawan.org # cat .qmail-kindred-default &[EMAIL PROTECTED] jedi padawan.org # cat .qmail-default | /var/vpopmail/bin/vdelivermail '' delete This is the result of: jedi padawan.org # echo testing | mail [EMAIL PROTECTED] qmail-send log: 2007-10-03 09:45:52.617451500 new msg 13863 2007-10-03 09:45:52.617783500 info msg 13863: bytes 224 from <[EMAIL PROTECTED]> qp 11452 uid 0 2007-10-03 09:45:52.719201500 starting delivery 542: msg 13863 to local [EMAIL PROTECTED] 2007-10-03 09:45:52.719231500 status: local 1/10 remote 0/20 2007-10-03 09:45:52.808711500 delivery 542: success: did_0+0+1/ 2007-10-03 09:45:52.809486500 status: local 0/10 remote 0/20 2007-10-03 09:45:52.809681500 end msg 13863 Headers from that email: Return-Path: <[EMAIL PROTECTED]> Delivered-To: kindred padawan.org Received: (qmail 11452 invoked by uid 0); 3 Oct 2007 08:45:52 - Date: 3 Oct 2007 08:45:52 - Message-ID: <[EMAIL PROTECTED]> From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] The only thing I deleted above was the @ on the Delivered-To line, as thats the address i'm trying not to get spammed and don't want any web crawlers picking it up. Thanks again for any help, much appreciated. Andy.
Re: [vchkpw] vpopmail user/group
Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Have you created the vpopmail user and vchkpw group? If not you must. Yes, I will create they when installing the package in my destination host. This is the why I need to get these values into the package when building. The build host isn't my dest host. That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts with postfix on Redhat distros. What is the problem? Just create the group and user with different values. It doesn't matter what the number is, it just has to exist when your run ./configure. Oh, the vpopmail uid and gid is not hardcoded into the binaries? The uid and gid are hard coded into the bianaries by ./configure. I cannot then use them on another host where they are different then.
Re: [vchkpw] vpopmail user/group
Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Have you created the vpopmail user and vchkpw group? If not you must. Yes, I will create they when installing the package in my destination host. This is the why I need to get these values into the package when building. The build host isn't my dest host. That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts with postfix on Redhat distros. What is the problem? Just create the group and user with different values. It doesn't matter what the number is, it just has to exist when your run ./configure. Oh, the vpopmail uid and gid is not hardcoded into the binaries? The uid and gid are hard coded into the bianaries by ./configure. I cannot then use them on another host where they are different then. No.
Re: [vchkpw] vpopmail user/group
Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Have you created the vpopmail user and vchkpw group? If not you must. Yes, I will create they when installing the package in my destination host. This is the why I need to get these values into the package when building. The build host isn't my dest host. That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts with postfix on Redhat distros. What is the problem? Just create the group and user with different values. It doesn't matter what the number is, it just has to exist when your run ./configure. Oh, the vpopmail uid and gid is not hardcoded into the binaries? The uid and gid are hard coded into the bianaries by ./configure. I cannot then use them on another host where they are different then. A better answer would be: No, not if they are different.
Re: [vchkpw] vpopmail user/group
Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Have you created the vpopmail user and vchkpw group? If not you must. Yes, I will create they when installing the package in my destination host. This is the why I need to get these values into the package when building. The build host isn't my dest host. That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts with postfix on Redhat distros. What is the problem? Just create the group and user with different values. It doesn't matter what the number is, it just has to exist when your run ./configure. Oh, the vpopmail uid and gid is not hardcoded into the binaries? The uid and gid are hard coded into the bianaries by ./configure. I cannot then use them on another host where they are different then. No. Well, that was the whole point of OP's post and why I said it was a tough nut to crack. The OP wants to build a package that will be used on other hosts...
Re: [vchkpw] vpopmail user/group
Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Have you created the vpopmail user and vchkpw group? If not you must. Yes, I will create they when installing the package in my destination host. This is the why I need to get these values into the package when building. The build host isn't my dest host. That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts with postfix on Redhat distros. What is the problem? Just create the group and user with different values. It doesn't matter what the number is, it just has to exist when your run ./configure. Oh, the vpopmail uid and gid is not hardcoded into the binaries? The uid and gid are hard coded into the bianaries by ./configure. I cannot then use them on another host where they are different then. No. Well, that was the whole point of OP's post and why I said it was a tough nut to crack. The OP wants to build a package that will be used on other hosts... Then use the same numbers for the uid and gid values for all qmail and vpopmail users on all systems.
Re: [vchkpw] vpopmail user/group
As I said: **I do not have root access** (the build service doesn't allow to build a package as root) what means that I can't add users or groups to the system too... I modified the "configure" and "Makefile" to do not exit if the user / group test fails and included "vpopmail.dir", "vpopmail.uid" and "vpopmail.gid" to the source. It worked, but in the next releases I'll need to do again.. I appreciate Your help. Regards. 2007/10/3, Rick Widmer <[EMAIL PROTECTED]>: > > > Christopher Chan wrote: > > Rick Widmer wrote: > >> > >> > >> Christopher Chan wrote: > >>> Rick Widmer wrote: > > > Christopher Chan wrote: > > Rick Widmer wrote: > >> > >> > >> Christopher Chan wrote: > >>> > > Have you created the vpopmail user and vchkpw group? If not > > you must. > > Yes, I will create they when installing the package in my > destination > host. This is the why I need to get these values into the > package when > building. The build host isn't my dest host. > > >>> > >>> That is a tough nut to crack. IIRC, vpopmail default uid/gid > >>> conflicts with postfix on Redhat distros. > >> > >> What is the problem? Just create the group and user with > >> different values. It doesn't matter what the number is, it just > >> has to exist when your run ./configure. > > > > Oh, the vpopmail uid and gid is not hardcoded into the binaries? > > > The uid and gid are hard coded into the bianaries by ./configure. > >>> > >>> I cannot then use them on another host where they are different then. > >>> > >>> > >> No. > > > > Well, that was the whole point of OP's post and why I said it was a > > tough nut to crack. The OP wants to build a package that will be used on > > other hosts... > > > > Then use the same numbers for the uid and gid values for all qmail and > vpopmail users on all systems. > -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems"
Re: [vchkpw] vpopmail user/group
Christopher Chan wrote: >>> Have you created the vpopmail user and vchkpw group? If not you must. >> >> Yes, I will create they when installing the package in my destination >> host. This is the why I need to get these values into the package when >> building. The build host isn't my dest host. >> > > That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts > with postfix on Redhat distros. In vpopmail.spec... "Conflicts: postfix" :) -jc
Re: [vchkpw] vpopmail or qmail problem?
On Oct 3, 2007, at 1:53 AM, Andy wrote: jedi padawan.org # cat .qmail-kindred-clamav | /var/vpopmail/bin/vdelivermail '' delete There's your mistake. What's happening is qmail-local hands the message off to vdelivermail (because you told it to), which looks for an account kindred-clamav (which it does not find), then an account named kindred (which it does) and then delivers to kindred. domain.com/.qmail-alias files are only read/processed by qmail- local. vdelivermail only looks at accounts (in whatever backend you're using) and possibly valias entries in a database. Rick, can you put this somewhere in the documentation: VDELIVERMAIL SHOULD ONLY APPEAR IN YOUR .qmail-default FILE. IF YOU PUT IT ELSEWHERE, IT WILL NOT DO WHAT YOU EXPECT IT TO DO. Solution: echo "#" > .qmail-kindred-clamav Or to bounce the email: echo "|/var/qmail/bin/bouncesaying 'Invalid account'" > .qmail- kindred-clamav -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/
Re: [vchkpw] vpopmail or qmail problem?
Tom Collins wrote: On Oct 3, 2007, at 1:53 AM, Andy wrote: jedi padawan.org # cat .qmail-kindred-clamav | /var/vpopmail/bin/vdelivermail '' delete There's your mistake. What's happening is qmail-local hands the message off to vdelivermail (because you told it to), which looks for an account kindred-clamav (which it does not find), then an account named kindred (which it does) and then delivers to kindred. domain.com/.qmail-alias files are only read/processed by qmail-local. vdelivermail only looks at accounts (in whatever backend you're using) and possibly valias entries in a database. Rick, can you put this somewhere in the documentation: VDELIVERMAIL SHOULD ONLY APPEAR IN YOUR .qmail-default FILE. IF YOU PUT IT ELSEWHERE, IT WILL NOT DO WHAT YOU EXPECT IT TO DO. Solution: echo "#" > .qmail-kindred-clamav Or to bounce the email: echo "|/var/qmail/bin/bouncesaying 'Invalid account'" > .qmail-kindred-clamav already done... from README.vdelivermail In summary... the .qmail-default of every virtual domain MUST contain ONLY a single line that executes vdelivermail. The ONLY place you should EVER call vdelivermail is from the .qmail-default file of a vpopmail based virtual domain. Updated documentation should probably be added to the list for version 6. Rick
Re: [vchkpw] vpopmail user/group
aledr wrote: As I said: **I do not have root access** (the build service doesn't allow to build a package as root) what means that I can't add users or groups to the system too... I modified the "configure" and "Makefile" to do not exit if the user / group test fails and included "vpopmail.dir", "vpopmail.uid" and "vpopmail.gid" to the source. It worked, but in the next releases I'll need to do again.. How do you intend to start vpopmail? port 110 is a privileged port, therefor it needs to have some root relation to actually start :) ...and if you just want to build it there to move adn run it on asystme you do have root on, then why not do it all there in teh first place. I appreciate Your help. Regards. 2007/10/3, Rick Widmer <[EMAIL PROTECTED]>: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Have you created the vpopmail user and vchkpw group? If not you must. Yes, I will create they when installing the package in my destination host. This is the why I need to get these values into the package when building. The build host isn't my dest host. That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts with postfix on Redhat distros. What is the problem? Just create the group and user with different values. It doesn't matter what the number is, it just has to exist when your run ./configure. Oh, the vpopmail uid and gid is not hardcoded into the binaries? The uid and gid are hard coded into the bianaries by ./configure. I cannot then use them on another host where they are different then. No. Well, that was the whole point of OP's post and why I said it was a tough nut to crack. The OP wants to build a package that will be used on other hosts... Then use the same numbers for the uid and gid values for all qmail and vpopmail users on all systems. -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems"
Re: [vchkpw] vpopmail user/group
2007/10/3, Quey <[EMAIL PROTECTED]>: > aledr wrote: > > As I said: **I do not have root access** (the build service doesn't > > allow to build a package as root) what means that I can't add users or > > groups to the system too... > > > > I modified the "configure" and "Makefile" to do not exit if the user / > > group test fails and included "vpopmail.dir", "vpopmail.uid" and > > "vpopmail.gid" to the source. It worked, but in the next releases I'll > > need to do again.. > > > > > > > How do you intend to start vpopmail? > port 110 is a privileged port, therefor it needs to have some root > relation to actually start :) > ...and if you just want to build it there to move adn run it on asystme > you do have root on, then why not do it all there in teh first place. According to your questions, I'll start in a higher point: How do I intend to install the RPM??? I will install It on my systems where I'm root. But I'm using a build service to build the package (build.opensuse.org) where I do not have root access to build the package. :D > > > I appreciate Your help. > > Regards. > > > > 2007/10/3, Rick Widmer <[EMAIL PROTECTED]>: > > > >> Christopher Chan wrote: > >> > >>> Rick Widmer wrote: > >>> > Christopher Chan wrote: > > > Rick Widmer wrote: > > > >> Christopher Chan wrote: > >> > >>> Rick Widmer wrote: > >>> > Christopher Chan wrote: > > >>> Have you created the vpopmail user and vchkpw group? If not > >>> you must. > >>> > >> Yes, I will create they when installing the package in my > >> destination > >> host. This is the why I need to get these values into the > >> package when > >> building. The build host isn't my dest host. > >> > >> > > That is a tough nut to crack. IIRC, vpopmail default uid/gid > > conflicts with postfix on Redhat distros. > > > What is the problem? Just create the group and user with > different values. It doesn't matter what the number is, it just > has to exist when your run ./configure. > > >>> Oh, the vpopmail uid and gid is not hardcoded into the binaries? > >>> > >>> > >> The uid and gid are hard coded into the bianaries by ./configure. > >> > > I cannot then use them on another host where they are different then. > > > > > > > No. > > >>> Well, that was the whole point of OP's post and why I said it was a > >>> tough nut to crack. The OP wants to build a package that will be used on > >>> other hosts... > >>> > >>> > >> Then use the same numbers for the uid and gid values for all qmail and > >> vpopmail users on all systems. > >> -- > >> > > [ ]'s > > Aledr - Alexandre > > "OpenSource Solutions for SmallBusiness Problems" > > > > > -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems"
Re: [vchkpw] vpopmail user/group
On Wed, 3 Oct 2007, Rick Widmer wrote: > > Oh, the vpopmail uid and gid is not hardcoded into the binaries? > > > The uid and gid are hard coded into the bianaries by ./configure. I've always wondered about this .. why is it done this way? Why not resolve the vpopmail login/group name into a UID/GID at runtime? James
Re: [vchkpw] vpopmail user/group
Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Rick Widmer wrote: Christopher Chan wrote: Have you created the vpopmail user and vchkpw group? If not you must. Yes, I will create they when installing the package in my destination host. This is the why I need to get these values into the package when building. The build host isn't my dest host. That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts with postfix on Redhat distros. What is the problem? Just create the group and user with different values. It doesn't matter what the number is, it just has to exist when your run ./configure. Oh, the vpopmail uid and gid is not hardcoded into the binaries? The uid and gid are hard coded into the bianaries by ./configure. I cannot then use them on another host where they are different then. No. Well, that was the whole point of OP's post and why I said it was a tough nut to crack. The OP wants to build a package that will be used on other hosts... Then use the same numbers for the uid and gid values for all qmail and vpopmail users on all systems. Ah, but what can I do if those systems are not mine? I have been planning on make a package for Centos users and to have it included on one of the Centos repositories.
Re: [vchkpw] vpopmail user/group
Japheth J.C. Cleaver wrote: Christopher Chan wrote: Have you created the vpopmail user and vchkpw group? If not you must. Yes, I will create they when installing the package in my destination host. This is the why I need to get these values into the package when building. The build host isn't my dest host. That is a tough nut to crack. IIRC, vpopmail default uid/gid conflicts with postfix on Redhat distros. In vpopmail.spec... "Conflicts: postfix" :) I know you are joking but I use postfix with vpopmail. The thing that irks me is that Redhat chose to use the vpopmail uid/gid for postfix when other distributions like Debian had already used them as standard for vpopmail IIRC.
Re: [vchkpw] vpopmail or qmail problem?
Tom Collins ([EMAIL PROTECTED]) wrote: > On Oct 3, 2007, at 1:53 AM, Andy wrote: > >jedi padawan.org # cat .qmail-kindred-clamav > >| /var/vpopmail/bin/vdelivermail '' delete > > There's your mistake. > > What's happening is qmail-local hands the message off to vdelivermail > (because you told it to), which looks for an account kindred-clamav > (which it does not find), then an account named kindred (which it > does) and then delivers to kindred. Awesome, thanks for spotting this for me. I didn't know how vdelivermail worked, and since my default option was to delete mail I figured the same syntax would work for my situation, so I just copied the .qmail-default file. No more spam! Thank you! Andy.
