[vchkpw] Problem with quota update
Hello List, I'm using vpopmail-5.4.10, netqmail-1.05. I have a problem with updating quota. All users have been created with: vadduser [EMAIL PROTECTED] -q 5242880 -c 'comment' password When an mail is delivered to [EMAIL PROTECTED], the usages changes, I've figured out that there is a maildirsize file in the Maildir. Ok.. But when [EMAIL PROTECTED] gets his mail (not leaving mails on server), the maildirsize is not being updated, seems that qmail-pop3d is not updating the maildirsize??? qmail-pop3d ist startet with tcpserver: cat /service/qmail-pop3d/run #!/bin/sh exec /usr/local/bin/softlimit -d 800 -s 800 -l 800 \ /usr/local/bin/tcpserver -v -R -H -l 0 0 110 /var/qmail/bin/qmail-popup \ levy.vl5.de /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 2>&1 Could somebody help me solving this problem? Thank you, Andrej.
Re: [vchkpw] Problem with quota update
Andrej escribió: > I'm using vpopmail-5.4.10, netqmail-1.05. > > I have a problem with updating quota. All users have been created with: > > vadduser [EMAIL PROTECTED] -q 5242880 -c 'comment' password > > When an mail is delivered to [EMAIL PROTECTED], the usages changes, I've > figured out that there is a maildirsize file in the Maildir. Ok.. > > But when [EMAIL PROTECTED] gets his mail (not leaving mails on server), > the maildirsize is not being updated, seems that qmail-pop3d is not > updating the maildirsize??? [...] > Could somebody help me solving this problem? You should apply maildir++ patch to your qmail. http://shupp.org/patches/qmail-maildir++-universal.patch Regards, Raúl Galicia
Re: [vchkpw] how to do simple vpopmail delivery with filtering
Thanks for this, I was in middle of implementing something like this
when I read the post and realized it would work. It did raise a
question for me though. If I'm using the valias with mysql, how
would I enable those accounts to be check for viruses since
vdelivermail would need to be called to have it forward it according
to the mysql table? I can't use a .qmail- file that sends it
to the script which then sends it to vdelivermail for the reason you
had mentioned.
On Apr 7, 2005 12:41 AM, Kurt Bigler <[EMAIL PROTECTED]> wrote:
> on 4/5/05 5:41 PM, Kurt Bigler <[EMAIL PROTECTED]> wrote:
>
> > on 4/5/05 6:28 AM, Kyle Wheeler <[EMAIL PROTECTED]> wrote:
> >
> >> | preline yourfilter | maildir /path/to/vpopdomains/`echo $USER | tr A-Z
> >> a-z`/`echo $EXT | tr A-Z a-z`/Maildir/
> >
> > Thanks, that's great.
> >
> >>> In the mean time, what is the best (simplest, most reliable) way to
> >>> achieve this simplistic delivery functionality?
> >>
> >> I think "maildir" (or "safecat") is what you want to use. If you think
> >> the environment manipulation is a bit much, I agree, but them's the
> >> breaks, at the moment.
> >
> > Ok, but that's not too bad. It just bugs me to have to install yet another
> > package, just to do what vpopmail already knows how to do.
> >
> > But thanks, that's what I needed to know!
> >
> > But I have a question to the vpopmail developers:
> >
> > If I were to implement this, as a option to vdelivermail, say:
> >
> > -d Deliver only. Do not preline and skip all .qmail processing
> >
> > would you find this to be something worth integrating? I'm not sure that
> > I'd have time now, but it seems worth asking the question.
>
> I actually implemented this in my copy of vdelivermail.c. It was actually
> easier than I thought, and there were fewer issues, apparently, although I'm
> not intimately familiar enough to know that I haven't missed something.
>
> Here's what I did:
>
> I tentatively reclaimed the unused there-for-compatibility command-line
> argument 1. If that argument equals '-d', intended to mean "Deliver Only"
> (but could also mean Disable .qmail processing), then processing proceeds as
> if the .qmail file did not exist, which I guess is just what Kyle Wheeler
> was suggesting. That appears to be all there is do it.
>
> This change allows you do basic filtering in your .qmail files without
> needing any of:
>
> procmail
> maildrop
> maildir/safecat
>
> In my book this is a very good thing. It not only avoids the need for
> dependencies on extra packages, but offers all the advantages that
> vdelivermail already provides, including quota checking. As README.quotas
> says:
>
> > NOTE: Non-system domain quotas are only enforcable when vdelivermail is the
> > local delivery agent. If you pipe your mail into anything else, like
> > maildrop, then the non-system domain quota will be ignored.
>
> So with this change, you can now have the following line in your user/.qmail
> file:
>
> | myfilter | vdelivermail -d bounce-no-mailbox
>
> and it will not result in infinite vdelivermail recursion. And so you can
> have a pure-vpopmail solution for your QmailAdmin-enabled Spam Detection
> option.
>
> Here are the changes to vdelivermail.c in vpopmail-5.4.10 needed to
> implement this:
>
> ==
> --- vdelivermail.orig.c Wed Apr 6 05:07:36 2005
> +++ vdelivermail.c Wed Apr 6 05:15:06 2005
> @@ -52,6 +52,7 @@
> struct vqpasswd *vpw;
> off_t message_size = 0;
> char bounce[AUTH_SIZE];
> +char option[AUTH_SIZE];/*kkb*/
> int CurrentQuotaSizeFd;
>
> #ifdef QMAIL_EXT
> @@ -177,6 +178,11 @@
> vexit(111);
> }
>
> + /*kkb begin*/
> + /* get the obsolete/option argument */
> +strncpy(option, argv[1], sizeof(option));
> + /*kkb end*/
> +
> /* get the last parameter in the .qmail-default file */
> strncpy(bounce, argv[2], sizeof(bounce));
>
> @@ -733,6 +739,14 @@
> int deliver_err;
>
> chdir(dir);
> +
> + /*kkb begin*/
> +if ( strcmp(option, "-d") == 0 ) {
> +
> +/* feature disabled, so just return */
> +return(-1);
> + }
> + /*kkb end*/
>
> /* format the file name */
> if ( (fs = fopen(".qmail","r")) == NULL ) {
> ==
>
> It was probably eaiser for me to do that than it would have been to download
> and make procmail, maildrop, or safecat!
>
> If there's not something wrong with this that I'm missing, I'd love to see
> this (or something similar) get integrated into vpopmail.
>
> -Kurt
>
>
Re: [vchkpw] vhostadmin development release
On Tue, 8 Mar 2005, Ken Jones wrote: Since the vpopmail daemon runs under tcpserver the PHP interface can run on a seperate machine, as well as solving the PHP permissions problem. I'm curious, if I want to watch the jabber between vhostadmin and vpopmaild what's the proper way to add "recordio" in a vpopmaild run script? Thanks, Charles The current development version may be downloaded at: http://www.inter7.com/?page=vhostadmin Or via CVS: export CVSROOT=:pserver:[EMAIL PROTECTED]:/home/cvs cvs login (login with empty password) cvs co vhostadmin We have established a mailing list for development and use of vhostadmin. To subscribe, send a blank e-mail message to [EMAIL PROTECTED] Ken Jones inter7.com
Re: [vchkpw] how to do simple vpopmail delivery with filtering
on 4/8/05 9:31 AM, James Whitt <[EMAIL PROTECTED]> wrote: > Thanks for this, I was in middle of implementing something like this > when I read the post and realized it would work. It did raise a > question for me though. If I'm using the valias with mysql, how > would I enable those accounts to be check for viruses since > vdelivermail would need to be called to have it forward it according > to the mysql table? I've never used valias, and I can't speak to that feature, but I'm kind of assuming the following logic applies regardless. So bear with this... > I can't use a .qmail- file that sends it > to the script which then sends it to vdelivermail for the reason you > had mentioned. Hmm. Well Tom says its not good to do that (to call vdelivermail anywhere besides in .qmail-default), but prior to hearing him say that, I was calling vdelivermail from .qmail- files all over the place. This is how I prototyped my filtering awaiting a better way to do it. I saw it as problematic because QmailAdmin didn't know what to do with it, mainly, but also because it would have bo be done per-alias and thus doesn't guarantee consistent behavior for a particular user destination. But it strikes me that if a .qmail- file contains for example exactly the same thing as .qmail-default, this would not hurt system behavior at all. Qmail looks for a .qmail- file first and if it finds one it does not look at .qmail-default. So there is no issue of .qmail-default recursion in that case. The recursion problem only comes up in the ".qmail" files (which are really vpopmail files, not seen by QMail) inside user directories. These files are called *from* vdelivermail. In any case if you can put your filter hook inside the user directory in the file called ".qmail" you get a much cleaner solution which remains compatible with whatever aliases you use elsewhere to point to that user, and does not require any filtering at the alias level. I'd think that would be true whether you use .qmail-alias or valias, because both mechanisms work at a level that occurs prior to what happens inside the user directory. > On Apr 7, 2005 12:41 AM, Kurt Bigler <[EMAIL PROTECTED]> wrote: >>> If I were to implement this, as a option to vdelivermail, say: >>> -d Deliver only. Do not preline and skip all .qmail processing >>> would you find this to be something worth integrating? I'm not sure that >>> I'd have time now, but it seems worth asking the question. >> >> I actually implemented this in my copy of vdelivermail.c. It was actually >> easier than I thought, and there were fewer issues, apparently, although I'm >> not intimately familiar enough to know that I haven't missed something. >> >> Here's what I did: >> I tentatively reclaimed the unused there-for-compatibility command-line >> argument 1. If that argument equals '-d', intended to mean "Deliver Only" >> (but could also mean Disable .qmail processing), then processing proceeds as >> if the .qmail file did not exist, which I guess is just what Kyle Wheeler >> was suggesting. That appears to be all there is do it. >> >> This change allows you do basic filtering in your .qmail files without >> needing any of: >> procmail >> maildrop >> maildir/safecat >> >> In my book this is a very good thing. It not only avoids the need for >> dependencies on extra packages, but offers all the advantages that >> vdelivermail already provides, including quota checking. As README.quotas >> says: >>> NOTE: Non-system domain quotas are only enforcable when vdelivermail is the >>> local delivery agent. If you pipe your mail into anything else, like >>> maildrop, then the non-system domain quota will be ignored. >> So with this change, you can now have the following line in your user/.qmail >> file: >> >> | myfilter | vdelivermail -d bounce-no-mailbox >> >> and it will not result in infinite vdelivermail recursion. And so you can >> have a pure-vpopmail solution for your QmailAdmin-enabled Spam Detection >> option.
Re: [vchkpw] how to do simple vpopmail delivery with filtering
On Apr 8, 2005, at 6:31 PM, Kurt Bigler wrote: But it strikes me that if a .qmail- file contains for example exactly the same thing as .qmail-default, this would not hurt system behavior at all. Qmail looks for a .qmail- file first and if it finds one it does not look at .qmail-default. So there is no issue of .qmail-default recursion in that case. The recursion problem only comes up in the ".qmail" files (which are really vpopmail files, not seen by QMail) inside user directories. These files are called *from* vdelivermail. This is true. I only mention it, because in the past there have been people who thought that vdelivermail '' /home/vpopmail/domain.com/user/Maildir Would simply deliver the message to that Maildir. It will only do that if the message doesn't match any valid user. If I can get vdelivermail to set the environment variables properly, you guys should be able to use the safecat (or maildir?) programs in your .qmail files. Are safecat and/or maildir quota-aware? -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ You don't need a laptop to troubleshoot high-speed Internet: sniffter.com
Re: [vchkpw] how to do simple vpopmail delivery with filtering
on 4/8/05 10:38 PM, Tom Collins <[EMAIL PROTECTED]> wrote: > On Apr 8, 2005, at 6:31 PM, Kurt Bigler wrote: >> But it strikes me that if a .qmail- file contains for example >> exactly >> the same thing as .qmail-default, this would not hurt system behavior >> at >> all. Qmail looks for a .qmail- file first and if it finds one >> it >> does not look at .qmail-default. So there is no issue of >> .qmail-default >> recursion in that case. The recursion problem only comes up in the >> ".qmail" >> files (which are really vpopmail files, not seen by QMail) inside user >> directories. These files are called *from* vdelivermail. > > This is true. > > I only mention it, because in the past there have been people who > thought that > > vdelivermail '' /home/vpopmail/domain.com/user/Maildir > > Would simply deliver the message to that Maildir. It will only do that > if the message doesn't match any valid user. > > If I can get vdelivermail to set the environment variables properly, > you guys should be able to use the safecat (or maildir?) programs in > your .qmail files. > > Are safecat and/or maildir quota-aware? I don't know. But have you looked at my vdelivermail.c patch? Don't you think it would be cool to have this functionality available without requiring another package? There's a bunch of features in vdelivermail.c and as it develops further no one is really keeping track of what they might lose by going with an outside-of-vpopmail solution. This makes me want to stick inside the vpopmail code, which I trust. It also guarantees uniformity of treatment for my filtered and unfiltered mail delivery. You can't beat the simplicity of it. -Kurt
Re: [vchkpw] how to do simple vpopmail delivery with filtering
On Apr 8, 2005, at 10:44 PM, Kurt Bigler wrote: I don't know. But have you looked at my vdelivermail.c patch? Don't you think it would be cool to have this functionality available without requiring another package? There's a bunch of features in vdelivermail.c and as it develops further no one is really keeping track of what they might lose by going with an outside-of-vpopmail solution. This makes me want to stick inside the vpopmail code, which I trust. It also guarantees uniformity of treatment for my filtered and unfiltered mail delivery. You can't beat the simplicity of it. I've put it in my queue and I'll consider it. I want to explore other options, perhaps finding a cleaner solution. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ You don't need a laptop to troubleshoot high-speed Internet: sniffter.com
