Re: [vchkpw] disable_external_relay [PATCH]
Dear Tonino,
Thanks a lot for the info. In my case the password is stored in MySQL. A
further hunt provided me the following:
The following options are bit flags in the gid int field (pw_gid) with the
int values stored.
-u ( set no dialup flag ) -- 64
-d ( set no password changing flag ) -- 1
-p ( set no pop access flag ) -- 2
-s ( set no smtp access flag ) -- 2048
-w ( set no web mail access flag ) -- 4
-i ( set no imap access flag ) -- 8
-b ( set bounce mail flag )-- 16
-r ( set no external relay flag ) -- 32
-a ( grant qmailadmin administrator privileges)-- 4096
-0 ( set V_USER0 flag )-- 128
-1 ( set V_USER1 flag )-- 256
-2 ( set V_USER2 flag )-- 512
-3 ( set V_USER3 flag )-- 1024
For Multiple settings the flags' values are added.
Devendra Singh
At 05/12/03 14:38 (), tonix (Antonio Nati) wrote:
vmoduser store this flag within the user record (either in .cdb or MysQl
or LDAP, depending on your configuration).
It's in the gid field.
Tonino
At 05/12/2003 05/12/2003 +0530, Devendra Singh wrote:
Dear Tonino,
Earlier when I had put the disable_smtp into .qmailadmin-limits, it
still allowed to relay the users. When I did use the vmoduser to set the
disable_smtp flag, it worked. But, where did the vmoduser store this flag
info. I could not locate it.
May some expert out there listening, may guide us.
Devendra Singh
At 05/12/03 13:48 (), tonix (Antonio Nati) wrote:
Devendra,
I'm still with an old version, and my domain limits are in
.qmailadmin-limits, within the domain directory.
I don't know if this is still valid for new version. Give a look at your
Changelog and README files (andpost the result).
Ciao,
Tonino
At 05/12/2003 05/12/2003 +0530, Devendra Singh wrote:
Dear Tonino / Tom,
In between the whole expert discussion the user level curious question
BTW, where is this user's limits info stored in case of non-mysql
limits? got lost.
Please, let us know.
Devendra Singh
At 04/12/03 14:32 (), tonix (Antonio Nati) wrote:
Tom,
thanks for your clear explanation.
However, don't you think that kind of things should be discussed in
the general list instead of development list?
I feel that development list should deal with implementation, how
to develop, how to improve code, while functionalities should be
discussed with end-users (or production users), that are interested in
functionalities, and don't care about implementation.
I'm really amazed when I discover a changed feature and see that it's
been done by developers without talking with end-users.
Ciao,
Tonino
At 03/12/2003 03/12/2003 -0700, you wrote:
On Wednesday, December 3, 2003, at 10:05 AM, tonix (Antonio Nati) wrote:
Tom,
sorry if I may be out of logic, just a fast look at the patch.
Here's how it works.
pw_gid is the user's limits.
if the user has V_OVERRIDE set, that's all they get.
otherwise, the domain limits are IN ADDITION to the user's limits.
For example:
If domain limit says no IMAP and user limit says no SMTP; user
doesn't have access to IMAP or SMTP.
Change domain limit from no IMAP to no POP. Now user limit becomes
no POP or SMTP.
We discussed this on the development list. Perhaps we need to
explain it better in the documentation.
Is it correct to keep using user flags if override is off?
Yes.
+if ((! (pw-pw_gid V_OVERRIDE))
if user not overriding domain limits
+ (vget_limits (domain, limits) == 0)) {
+pw-pw_flags = pw-pw_gid | vlimits_get_flag_mask (limits);
using mixed limits from user and domain.
Correct.
Would it be more direct to use only domain limits in such a case?
No. If you do it that way, you can't impose additional limits on a
single user in the domain (or, for example, add qmailadmin admin access).
+} else pw-pw_flags = pw-pw_gid;
else use user limits.
Correct. If V_OVERRIDE is set, or the limit lookup fails, it just
uses the user limits.
At 03/12/2003 03/12/2003 -0700, you wrote:
Here's the patch to fix the domain limits problem. It's in CVS
now, and will be in the next release (which I'll make by the end of
the week). Hopefully the email gateways won't totally screw the file up...
[snip]
Thanks for including an entire copy of the patch in your response.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.528 / Virus Database: 324 - Release Date: 16/10/03
[EMAIL PROTECTED]Interazioni di Antonio Nati
http://www.interazioni.it [EMAIL PROTECTED]
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.548 / Virus Database: 341 - Release Date: 05/12/03
---
Outgoing mail is certified
Re: [vchkpw] roaming user
As you told me, I have upgraded to vpopmail-5.3.30 But I still have the problem and get the message : sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) When I want to send an email with SMTP. As if vpopmail don't added my IP into the tcp.smtp.cdb database file. and that's the case, there isn't my IP in this file. Anyone have a solution for that ? Because I have this problem on 2 servers. Le 7 déc. 03, à 11:24, Michael Bowe a écrit : - Original Message - From: Arnaud BECKER [EMAIL PROTECTED] I have installed on 2 linux (debian and mandrake) Qmail + vpopmail + Courier-Imap based on this very well done document : http://sylvestre.ledru.info/howto/howto_qmail_vpopmail.php I have a big problem. The roaming user is not working. When I want to send an email, it answer that I'm not authorized to send mail through that smtp server. As if tcpserver isn't wrapping the POP3 and IMAP connections to authentificate connections and add them to the tcp.smtp.cdb What is strange is that if I stop the qmail service and I restart it, it works but only for the people which are connecting to the server just at this time. I see that site recommends vpopmail-5.2.1 I dont think this is a very good idea, as this version contains a number of bugs, including a big one that causes problems with authenticating in courier-imap. I would recommend that you upgrade to the current stable vpopmail-5.2.2, or even the current development vpopmail-5.3.30 Note that if you upgrade your vpopmail, you will also then need to rebuild any other apps that use the vpopmail functions (eg qmailadmin, courier-imap) I have recently written some information regarding vpopmail roaming users. Perhaps take a look and see if it helps you solve your problem : http://www.pipeline.com.au/staff/mbowe/isp/webmail-server.htm#VPOPMAIL Michael.
Re: [vchkpw] roaming user
I don't know, but I had the same problem with the version 5.2.1 Le 8 déc. 03, à 10:56, Jacob Mathew a écrit : hello. does vpopmail-5.3.30 has got any problems in supporting roaming users regds Jacob - Original Message - From: Arnaud BECKER [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, December 08, 2003 3:13 PM Subject: Re: [vchkpw] roaming user As you told me, I have upgraded to vpopmail-5.3.30 But I still have the problem and get the message : sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) When I want to send an email with SMTP. As if vpopmail don't added my IP into the tcp.smtp.cdb database file. and that's the case, there isn't my IP in this file. Anyone have a solution for that ? Because I have this problem on 2 servers. Le 7 déc. 03, à 11:24, Michael Bowe a écrit : - Original Message - From: Arnaud BECKER [EMAIL PROTECTED] I have installed on 2 linux (debian and mandrake) Qmail + vpopmail + Courier-Imap based on this very well done document : http://sylvestre.ledru.info/howto/howto_qmail_vpopmail.php I have a big problem. The roaming user is not working. When I want to send an email, it answer that I'm not authorized to send mail through that smtp server. As if tcpserver isn't wrapping the POP3 and IMAP connections to authentificate connections and add them to the tcp.smtp.cdb What is strange is that if I stop the qmail service and I restart it, it works but only for the people which are connecting to the server just at this time. I see that site recommends vpopmail-5.2.1 I dont think this is a very good idea, as this version contains a number of bugs, including a big one that causes problems with authenticating in courier-imap. I would recommend that you upgrade to the current stable vpopmail-5.2.2, or even the current development vpopmail-5.3.30 Note that if you upgrade your vpopmail, you will also then need to rebuild any other apps that use the vpopmail functions (eg qmailadmin, courier-imap) I have recently written some information regarding vpopmail roaming users. Perhaps take a look and see if it helps you solve your problem : http://www.pipeline.com.au/staff/mbowe/isp/webmail-server.htm#VPOPMAIL Michael.
[vchkpw] Roaming user support in vpopmail 5.3.30
Hello all does vpopmail-5.3.30 has got any problems in supporting roaming users regds Jacob
Re: [vchkpw] Roaming user support in vpopmail 5.3.30
- Original Message - From: [EMAIL PROTECTED] Hello all does vpopmail-5.3.30 has got any problems in supporting roaming users The problems that were present in 5.3.29 have been resolved. There are no known issues with the roaming user code in 5.3.30 Michael
[vchkpw] vpopmail.h question
I need vpopmail to always create directories as chmod 777. Yes, I know this is a huge security issue, but I need it done anyway. I know I need to change one of the following variables, but no matter what I try (yes, 777..), it doesn't create the directories as 777. #define VPOPMAIL_UMASK 0077 #define VPOPMAIL_DIR_MODE488 #define VPOPMAIL_QMAIL_MODE S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH Any help would be appreciated. -Robertson
Re: [vchkpw] vpopmail.h question
On Monday, December 8, 2003, at 10:19 AM, [EMAIL PROTECTED] wrote: I need vpopmail to always create directories as chmod 777. Yes, I know this is a huge security issue, but I need it done anyway. I know I need to change one of the following variables, but no matter what I try (yes, 777..), it doesn't create the directories as 777. #define VPOPMAIL_UMASK 0077 #define VPOPMAIL_DIR_MODE488 #define VPOPMAIL_QMAIL_MODE S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH Any help would be appreciated. What you want is a UMASK of 0 to get permissions set to 0777. VPOPMAIL_QMAIL_MODE can simply be set to 0777. VPOPMAIL_DIR_MODE 488 is the same as 0750. You'll want it to be 0777 to have directories created with rwxrwxrwx permissions. -- 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] vpopmail.h question
Didn't work :( drwx--3 vpopmail vchkpw 20 Dec 8 13:22 test I edited the vars, recompiled, reinstalled. Note this user was added via qmailadmin, which as far as I know just does calls to vadduser/vadddomain/etc. -Robertson - Original Message - From: Tom Collins [EMAIL PROTECTED] To: vpopmail list [EMAIL PROTECTED] Sent: Monday, December 08, 2003 12:39 PM Subject: Re: [vchkpw] vpopmail.h question On Monday, December 8, 2003, at 10:19 AM, [EMAIL PROTECTED] wrote: I need vpopmail to always create directories as chmod 777. Yes, I know this is a huge security issue, but I need it done anyway. I know I need to change one of the following variables, but no matter what I try (yes, 777..), it doesn't create the directories as 777. #define VPOPMAIL_UMASK 0077 #define VPOPMAIL_DIR_MODE488 #define VPOPMAIL_QMAIL_MODE S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH Any help would be appreciated. What you want is a UMASK of 0 to get permissions set to 0777. VPOPMAIL_QMAIL_MODE can simply be set to 0777. VPOPMAIL_DIR_MODE 488 is the same as 0750. You'll want it to be 0777 to have directories created with rwxrwxrwx permissions. -- 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] vpopmail.h question
On Monday, December 8, 2003, at 11:24 AM, [EMAIL PROTECTED] wrote: Didn't work :( drwx--3 vpopmail vchkpw 20 Dec 8 13:22 test I edited the vars, recompiled, reinstalled. Note this user was added via qmailadmin, which as far as I know just does calls to vadduser/vadddomain/etc. Current qmailadmin is hardcoded to use 0077 (grep qmailadmin.c for umask to see where to change it). I've changed it to VPOPMAIL_UMASK in CVS and it will be in the upcoming 1.0.30 (or 1.2.0-pre1) release. -- 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] Roaming user support
Could anyone help me please with my problems with the roaming user support. please please I don't know what to do to make it work well. I don't know where is the problem or error. Le 8 déc. 03, à 11:57, Michael Bowe a écrit : - Original Message - From: [EMAIL PROTECTED] Hello all does vpopmail-5.3.30 has got any problems in supporting roaming users The problems that were present in 5.3.29 have been resolved. There are no known issues with the roaming user code in 5.3.30 Michael
Re: [vchkpw] Roaming user support
how did you set up the ./configure? ./configure --enable-roaming-users=yes ? ( I think that is the flag) what verision of Vpopmail are you using? the one from below? Arnaud BECKER wrote: Could anyone help me please with my problems with the roaming user support. please please I don't know what to do to make it work well. I don't know where is the problem or error. Le 8 déc. 03, à 11:57, Michael Bowe a écrit : - Original Message - From: [EMAIL PROTECTED] Hello all does vpopmail-5.3.30 has got any problems in supporting roaming users The problems that were present in 5.3.29 have been resolved. There are no known issues with the roaming user code in 5.3.30 Michael .
Re: [vchkpw] vpopmail.h question
After that change, now when logging into ANY domains qmailadmin, I get: Only one person can log in as system postmaster at one time. Someone else has logged in. Please only have one login at a time. -Robertson - Original Message - From: Tom Collins [EMAIL PROTECTED] To: vpopmail list [EMAIL PROTECTED] Sent: Monday, December 08, 2003 1:56 PM Subject: Re: [vchkpw] vpopmail.h question On Monday, December 8, 2003, at 11:24 AM, [EMAIL PROTECTED] wrote: Didn't work :( drwx--3 vpopmail vchkpw 20 Dec 8 13:22 test I edited the vars, recompiled, reinstalled. Note this user was added via qmailadmin, which as far as I know just does calls to vadduser/vadddomain/etc. Current qmailadmin is hardcoded to use 0077 (grep qmailadmin.c for umask to see where to change it). I've changed it to VPOPMAIL_UMASK in CVS and it will be in the upcoming 1.0.30 (or 1.2.0-pre1) release. -- 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] Roaming user support
Yes, I've used : --enable-roaming-users=y I've put something like that : /configure --enable-roaming-users=y --enable-logging=y --enable-defaultquota=150 --enable-ip-alias-domains=y --enable-mysql=y --enable-clear-passwd=n --enable-libdir=/usr/include/mysql/ I was using the 5.2.1, but I thought that an upgrade would solve the problem, but it's not ! And now I have the version 5.3.30 any idea ? Le 8 déc. 03, à 23:26, martin a écrit : how did you set up the ./configure? ./configure --enable-roaming-users=yes ? ( I think that is the flag) what version of Vpopmail are you using? the one from below? Arnaud BECKER wrote: Could anyone help me please with my problems with the roaming user support. please please I don't know what to do to make it work well. I don't know where is the problem or error. Le 8 déc. 03, à 11:57, Michael Bowe a écrit : - Original Message - From: [EMAIL PROTECTED] Hello all does vpopmail-5.3.30 has got any problems in supporting roaming users The problems that were present in 5.3.29 have been resolved. There are no known issues with the roaming user code in 5.3.30 Michael .
Re: [vchkpw] vpopmail.h question
On Monday, December 8, 2003, at 03:24 PM, [EMAIL PROTECTED] wrote: After that change, now when logging into ANY domains qmailadmin, I get: Only one person can log in as system postmaster at one time. Someone else has logged in. Please only have one login at a time. Look in ~vpopmail/domains/domain.com/postmaster/Maildir for a filename that ends in .qw. If QmailAdmin can't write a new file there (or delete the old one), then you won't be able to log in. Is you VPOPMAIL_UMASK set to 0? Do you have old .qw files left over from when the permissions were wrong? -- 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] vpopmail.h question
Yes, and I've deleted it. When you try to log back in, you can log in, but when you try to actually do anything, you get back to that error. I also see qmailadmin is creating the files as chmod 0: --1 vpopmail vchkpw 47 Dec 8 17:41 1070923318.qw -Robertson - Original Message - From: Tom Collins [EMAIL PROTECTED] To: vpopmail list [EMAIL PROTECTED] Sent: Monday, December 08, 2003 5:39 PM Subject: Re: [vchkpw] vpopmail.h question On Monday, December 8, 2003, at 03:24 PM, [EMAIL PROTECTED] wrote: After that change, now when logging into ANY domains qmailadmin, I get: Only one person can log in as system postmaster at one time. Someone else has logged in. Please only have one login at a time. Look in ~vpopmail/domains/domain.com/postmaster/Maildir for a filename that ends in .qw. If QmailAdmin can't write a new file there (or delete the old one), then you won't be able to log in. Is you VPOPMAIL_UMASK set to 0? Do you have old .qw files left over from when the permissions were wrong? -- 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] vpopmail.h question
Nevermind, I figured it out. Thanks for your help, much appreciated. -Robertson - Original Message - From: [EMAIL PROTECTED] To: vpopmail list [EMAIL PROTECTED] Sent: Monday, December 08, 2003 5:42 PM Subject: Re: [vchkpw] vpopmail.h question Yes, and I've deleted it. When you try to log back in, you can log in, but when you try to actually do anything, you get back to that error. I also see qmailadmin is creating the files as chmod 0: --1 vpopmail vchkpw 47 Dec 8 17:41 1070923318.qw -Robertson - Original Message - From: Tom Collins [EMAIL PROTECTED] To: vpopmail list [EMAIL PROTECTED] Sent: Monday, December 08, 2003 5:39 PM Subject: Re: [vchkpw] vpopmail.h question On Monday, December 8, 2003, at 03:24 PM, [EMAIL PROTECTED] wrote: After that change, now when logging into ANY domains qmailadmin, I get: Only one person can log in as system postmaster at one time. Someone else has logged in. Please only have one login at a time. Look in ~vpopmail/domains/domain.com/postmaster/Maildir for a filename that ends in .qw. If QmailAdmin can't write a new file there (or delete the old one), then you won't be able to log in. Is you VPOPMAIL_UMASK set to 0? Do you have old .qw files left over from when the permissions were wrong? -- 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] Documentation bug/omission?
I've just upgraded from plain old qmail to qmail/vpopmail. Everything seemed to be going fine until for no apparent reason, POP3 logins from every mail domain were denied. A little hunting down led me to discover /var/qmail/users/assign had been utterly trashed with the cdb representation of the entirity of /etc/passwd. It seems that either qmail or RedHat 9's default installer sets up a job in /etc/cron.hourly/qmail that updates users/assign with any new users that may have been added. In the context of vpopmail, trashing users/assign like this is A Bad Thing. I've not seen this particular gotcha mentioned in any docs anywhere. Is there a more appropriate list I should maybe mention this to?
[vchkpw] vpopbull broke in 5.2.2?
Hello, Is vpopbull broke in 5.2.2? When I run it, it simply silently exits, even when using -V (verbose). I'm running it like this: ./vpopbull -V -c -f /path/to/file domain.com Running version 5.2.2 with MySQL enabled. Regards, Joe Boyce --- InterStar, Inc. - Shasta.com Internet Phone: +1 (530) 224-6866 x105 Email: [EMAIL PROTECTED]
