Re: [vchkpw] disable_external_relay [PATCH]
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]
Re: [vchkpw] disable_external_relay [PATCH]
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
Re: [vchkpw] disable_external_relay [PATCH]
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]
[vchkpw] vpopmail+ldap developer?
Hello. I've found several bugs in vldap.c module. Who should I contact to report the bugs... and the solutions :) Bye. - Oscar Retana M.
Re: [vchkpw] vpopmail+ldap developer?
On Friday, December 5, 2003, at 10:23 AM, Oscar Retana M. wrote: I've found several bugs in vldap.c module. Who should I contact to report the bugs... and the solutions :) Please post patches to SourceForge http://vpopmail.sf.net/. Make sure they're against the latest development version. As far as I know, we don't have an active maintainer for LDAP. Michael Bowe has looked at it a bit, but I don't think any of the current developers have an LDAP setup to test with. -- 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] strange stuff in log.
That's actually a qmail error, not vpopmail. It's caused by incorrect permissions in the queue. Fix: chown -R qmailq:qmail /var/qmail/queue/todo/ But more importabtly, find out what changed the permissions, and why to fix the problem for good - as it may just happen again. - Original Message - From: John Johnson To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, December 05, 2003 10:26 PM Subject: [vchkpw] strange stuff in log. Can anyone shed some light on this? It's in my qmail log file and the server is having mail problems but that's because we found the DNS server was not working... 2003-12-05 19:25:22.049714500 warning: unable to open todo/387402003-12-05 19:25:22.049725500 warning: unable to open todo/387422003-12-05 19:25:22.049730500 warning: unable to open todo/387442003-12-05 19:25:22.049735500 warning: unable to open todo/387462003-12-05 19:25:22.049739500 warning: unable to open todo/387482003-12-05 19:25:22.049744500 warning: unable to open todo/387492003-12-05 19:25:22.049748500 warning: unable to open todo/387512003-12-05 19:25:22.049753500 warning: unable to open todo/387532003-12-05 19:25:22.049757500 warning: unable to open todo/387552003-12-05 19:25:22.049910500 warning: unable to open todo/387582003-12-05 19:25:22.049915500 warning: unable to open todo/387602003-12-05 19:25:22.049920500 warning: unable to open todo/387622003-12-05 19:25:22.049924500 warning: unable to open todo/387642003-12-05 19:25:22.049929500 warning: unable to open todo/387662003-12-05 19:25:22.049933500 warning: unable to open todo/387682003-12-05 19:25:22.049938500 warning: unable to open todo/38770
Re: [vchkpw] vpopmail+ldap developer?
Oscar Retana M. wrote: Hello. I've found several bugs in vldap.c module. Who should I contact to report the bugs... and the solutions :) Bye. - Oscar Retana M. It would be nice to see an active developer for this part of vpopmail, would make a lot of things simpler for a company i work for, i do not have the time or skills to track down and find errors in the code. http://vpopmail.sourceforge.net/ to post your patches :) X-Istence
Re: [vchkpw] Problem with vchkpw, system accounts, and smtp-auth.
Paul Robinson [vchkpw] wrote: snip Hi, I was able to resolve this without the assistance of the list and am embarrassed to admit that somehow, despite setting many compile-type configuration options with vpopmail, I missed the --enable-passwd=y directive to the configure script. I'm a tad embarrassed, but perhaps having this in the archives will help someone else resolve their issues. (Ironically, I managed to migrate all my system accounts over to vpopmail before figuring out what the problem was.) Many thanks! Cheers, Paul Robinson gotclue.net No need to be emberrased, every once in a while even the most experienced will miss one thing. Personally i missed this flag as well, but i just as you also figured it out. :) X-Istence
[vchkpw] Vpopmail 5.3.29 - 5.3.30 vchkpw changes/SMTP AUTH Problem
Hello, I'm using qmail with the SMTP AUTH TLS patch and it has been working fine, until today. Today I upgraded from 5.3.29 to 5.3.30. Has anyone else noticed a problem with this? The only change I now about to vchkpw was the fixing of the roaming users support. Did this have negative affects on SMTP AUTH? My POP3 authorizations are working fine. This is what I see in my maillog: Dec 5 22:57:30 h1 vpopmail[18073]: vchkpw-smtp: vpopmail user not found [EMAIL PROTECTED]:24.8.51.x My tcpserver line looks like this (its run under supervise): tcpserver -v -x/usr/local/vpopmail/etc/tcp.smtp.cdb -u82 -g81 ip smtp /var/qmail/bin/qmail-smtpd fqdn /usr/local/vpopmail/bin/vchkpw /usr/bin/true 21 Any ideas would be appreciated. Thanks, Brad Davis
Re: [vchkpw] strange stuff in log.
well funny thing is I didn't delete from the queue... -John - Original Message - From: X-Istence [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, December 05, 2003 9:46 PM Subject: Re: [vchkpw] strange stuff in log. John Johnson wrote: Can anyone shed some light on this? It's in my qmail log file and the server is having mail problems but that's because we found the DNS server was not working... 2003-12-05 19:25:22.049714500 warning: unable to open todo/38740 2003-12-05 19:25:22.049725500 warning: unable to open todo/38742 2003-12-05 19:25:22.049730500 warning: unable to open todo/38744 2003-12-05 19:25:22.049735500 warning: unable to open todo/38746 2003-12-05 19:25:22.049739500 warning: unable to open todo/38748 2003-12-05 19:25:22.049744500 warning: unable to open todo/38749 2003-12-05 19:25:22.049748500 warning: unable to open todo/38751 2003-12-05 19:25:22.049753500 warning: unable to open todo/38753 2003-12-05 19:25:22.049757500 warning: unable to open todo/38755 2003-12-05 19:25:22.049910500 warning: unable to open todo/38758 2003-12-05 19:25:22.049915500 warning: unable to open todo/38760 2003-12-05 19:25:22.049920500 warning: unable to open todo/38762 2003-12-05 19:25:22.049924500 warning: unable to open todo/38764 2003-12-05 19:25:22.049929500 warning: unable to open todo/38766 2003-12-05 19:25:22.049933500 warning: unable to open todo/38768 2003-12-05 19:25:22.049938500 warning: unable to open todo/38770 Yeah, someone deleted part of the qmail queue, real smart i have to say. (NOT) Anyways, since you have allready screwed over your queue, find queue-repair, its a special utility to repair queue's, and use it to repair your queue. And then restart qmail, those error messages should be gone. It is not smart to delete from the qmail queue. X
[vchkpw] RE: Vpopmail 5.3.29 - 5.3.30 vchkpw changes/SMTP AUTH Problem
Whoops, my fault. I forgot to go back and: chmod 4755 ~vpopmail/bin/vchkpw chown root:wheel ~vpopmail/bin/vchkpw :) Thanks, Brad -Original Message- From: Brad Davis To: '[EMAIL PROTECTED]' Sent: 12/5/2003 10:13 PM Subject: Vpopmail 5.3.29 - 5.3.30 vchkpw changes/SMTP AUTH Problem Hello, I'm using qmail with the SMTP AUTH TLS patch and it has been working fine, until today. Today I upgraded from 5.3.29 to 5.3.30. Has anyone else noticed a problem with this? The only change I now about to vchkpw was the fixing of the roaming users support. Did this have negative affects on SMTP AUTH? My POP3 authorizations are working fine. This is what I see in my maillog: Dec 5 22:57:30 h1 vpopmail[18073]: vchkpw-smtp: vpopmail user not found [EMAIL PROTECTED]:24.8.51.x My tcpserver line looks like this (its run under supervise): tcpserver -v -x/usr/local/vpopmail/etc/tcp.smtp.cdb -u82 -g81 ip smtp /var/qmail/bin/qmail-smtpd fqdn /usr/local/vpopmail/bin/vchkpw /usr/bin/true 21 Any ideas would be appreciated. Thanks, Brad Davis
[vchkpw] strange stuff in log.
Can anyone shed some light on this? It's in my qmail log file and the server is having mail problems but that's because we found the DNS server was not working... 2003-12-05 19:25:22.049714500 warning: unable to open todo/387402003-12-05 19:25:22.049725500 warning: unable to open todo/387422003-12-05 19:25:22.049730500 warning: unable to open todo/387442003-12-05 19:25:22.049735500 warning: unable to open todo/387462003-12-05 19:25:22.049739500 warning: unable to open todo/387482003-12-05 19:25:22.049744500 warning: unable to open todo/387492003-12-05 19:25:22.049748500 warning: unable to open todo/387512003-12-05 19:25:22.049753500 warning: unable to open todo/387532003-12-05 19:25:22.049757500 warning: unable to open todo/387552003-12-05 19:25:22.049910500 warning: unable to open todo/387582003-12-05 19:25:22.049915500 warning: unable to open todo/387602003-12-05 19:25:22.049920500 warning: unable to open todo/387622003-12-05 19:25:22.049924500 warning: unable to open todo/387642003-12-05 19:25:22.049929500 warning: unable to open todo/387662003-12-05 19:25:22.049933500 warning: unable to open todo/387682003-12-05 19:25:22.049938500 warning: unable to open todo/38770
Re: [vchkpw] strange stuff in log.
John Johnson wrote: Can anyone shed some light on this? It's in my qmail log file and the server is having mail problems but that's because we found the DNS server was not working... 2003-12-05 19:25:22.049714500 warning: unable to open todo/38740 2003-12-05 19:25:22.049725500 warning: unable to open todo/38742 2003-12-05 19:25:22.049730500 warning: unable to open todo/38744 2003-12-05 19:25:22.049735500 warning: unable to open todo/38746 2003-12-05 19:25:22.049739500 warning: unable to open todo/38748 2003-12-05 19:25:22.049744500 warning: unable to open todo/38749 2003-12-05 19:25:22.049748500 warning: unable to open todo/38751 2003-12-05 19:25:22.049753500 warning: unable to open todo/38753 2003-12-05 19:25:22.049757500 warning: unable to open todo/38755 2003-12-05 19:25:22.049910500 warning: unable to open todo/38758 2003-12-05 19:25:22.049915500 warning: unable to open todo/38760 2003-12-05 19:25:22.049920500 warning: unable to open todo/38762 2003-12-05 19:25:22.049924500 warning: unable to open todo/38764 2003-12-05 19:25:22.049929500 warning: unable to open todo/38766 2003-12-05 19:25:22.049933500 warning: unable to open todo/38768 2003-12-05 19:25:22.049938500 warning: unable to open todo/38770 Yeah, someone deleted part of the qmail queue, real smart i have to say. (NOT) Anyways, since you have allready screwed over your queue, find queue-repair, its a special utility to repair queue's, and use it to repair your queue. And then restart qmail, those error messages should be gone. It is not smart to delete from the qmail queue. X
