[vchkpw] quota warn message is broken in vpopmail with maildrop support enable

2008-10-13 Thread Alessio Cecchi
Hi,

I'm made many test before write this e-mail, but I think that when I enable 
maildrop support in vpopmail (--enable-maildrop) and I place 
an /etc/maildroprc (like src/vpopmail-5.4.26/maildrop/maildroprc.v2) the 
warning about "quota warn message" not working.

I'm working in a test environment configured as follow:

shupp.org's toaster

vpopmail 5.4.26 build with this options:
./configure --enable-mysql-limits 
--enable-auth-module=mysql 
--enable-logging=v 
--enable-maildrop

/etc/maildroprc is this 
http://vpopmail.cvs.sourceforge.net/viewvc/vpopmail/vpopmail/maildrop/maildroprc.v2?revision=1.3&view=markup
but I also tried with others without success.

When a mailbox reach 90% or more the message ~vpopmail/domains/.quotawarn.msg 
is copied only if maildrop for these user is disable (vmoduser -x 
[EMAIL PROTECTED]), when maildrop support is enable the messagge is not copied 
to 
the user mailbox.

Yes, I delete the file "quotawarn" in the user Maildir every time.

Can be easily corrected this problem?

Maybe just enough to anticipate the process that check the quota, and copy the 
file, and after running maildrop with maildroprc, but I do not know if I'm 
making a wrong assumption.

Thanks
-- 
Alessio Cecchi is:
@ ILS -> http://www.linux.it/~alessice/
Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/
@ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it
@ LOLUG -> neo-Socio http://www.lolug.net

!DSPAM:48f333e832312229217102!



Re: [vchkpw] quota warn message is broken in vpopmail with maildrop support enable

2008-10-13 Thread Alessio Cecchi
Il Monday 13 October 2008 13:50:27 Jukka Kurkela ha scritto:
> From README.quotas:
>
>     MAILDROP
>
>     If you use maildrop for filtering, compile it with maildirquota support
>     if you want to use it with vpopmail 5.1.1 and above with quotas.
>
> did you compile maildrop with maildirquota supporta?

Yes, in fact "over quota" works:

It was created by maildrop configure 2.0.4, which was
generated by GNU Autoconf 2.59.  Invocation command line was

  $ ./configure --enable-syslog=1 --enable-maildirquota --prefix=/usr

Ciao
-- 
Alessio Cecchi is:
@ ILS -> http://www.linux.it/~alessice/
Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/
@ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it
@ LOLUG -> neo-Socio http://www.lolug.net

!DSPAM:48f33f1732319257115799!



[vchkpw] Username length in vchkpw/vpopmail

2008-10-13 Thread Antti Kanes

Hi,

it seems that (at least with version 5.4.17) the username length with  
mysql authentication has been limited to 32 characters and the domain  
part to 64 characters;
vpopmail.pw_name char(32), vpopmail.pw_domain(64), valias.alias  
char(32), valias.domain char(64).
The SMTP RFC allows for a local-name part of an email address to be 64  
characters and domain to be 255 characters long.


Has this been addressed in later versions of vpopmail, and can it  
safely be fixed by altering these table fields to have corresponding  
longer lengths?

ie. does it break something in vchkpw (or qmailadmin)?
Found some references on the list mentioning limits in vpopmail.h:

#define MAX_PW_NAME 32
#define MAX_PW_DOMAIN   64

Are these still valid and therefore require changes to the code and  
recompilation in order to conform with the RFC?


Cheers,
  Antti Kanes, Innoventum

!DSPAM:48f32b1532314550744776!



Re: [vchkpw] quota warn message is broken in vpopmail with maildrop support enable

2008-10-13 Thread Jukka Kurkela
On Mon, 13 Oct 2008 13:41:25 +0200, Alessio Cecchi <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I'm made many test before write this e-mail, but I think that when I
enable
> 
> maildrop support in vpopmail (--enable-maildrop) and I place 
> an /etc/maildroprc (like src/vpopmail-5.4.26/maildrop/maildroprc.v2) the 
> warning about "quota warn message" not working.
> 
> I'm working in a test environment configured as follow:
> 
> shupp.org's toaster
> 
> vpopmail 5.4.26 build with this options:
> ./configure --enable-mysql-limits 
> --enable-auth-module=mysql 
> --enable-logging=v 
> --enable-maildrop
> 
> /etc/maildroprc is this 
>
http://vpopmail.cvs.sourceforge.net/viewvc/vpopmail/vpopmail/maildrop/maildroprc.v2?revision=1.3&view=markup
> but I also tried with others without success.
> 
> When a mailbox reach 90% or more the message
> ~vpopmail/domains/.quotawarn.msg 
> is copied only if maildrop for these user is disable (vmoduser -x 
> [EMAIL PROTECTED]), when maildrop support is enable the messagge is not
copied
> to 
> the user mailbox.
> 
> Yes, I delete the file "quotawarn" in the user Maildir every time.
> 
> Can be easily corrected this problem?
> 
> Maybe just enough to anticipate the process that check the quota, and
copy
> the 
> file, and after running maildrop with maildroprc, but I do not know if
I'm 
> making a wrong assumption.
> 
> Thanks
>

>From README.quotas:

MAILDROP

If you use maildrop for filtering, compile it with maildirquota support
if you want to use it with vpopmail 5.1.1 and above with quotas.

did you compile maildrop with maildirquota supporta?

regards,
Jukka Kurkela

!DSPAM:48f335ef32311761212767!



Re: [vchkpw] Username length in vchkpw/vpopmail

2008-10-13 Thread Alessio Cecchi
Il Monday 13 October 2008 13:03:45 Antti Kanes ha scritto:
> Hi,
>
> it seems that (at least with version 5.4.17) the username length with  
> mysql authentication has been limited to 32 characters and the domain  
> part to 64 characters;
> vpopmail.pw_name char(32), vpopmail.pw_domain(64), valias.alias  
> char(32), valias.domain char(64).
> The SMTP RFC allows for a local-name part of an email address to be 64  
> characters and domain to be 255 characters long.
>
> Has this been addressed in later versions of vpopmail, and can it  
> safely be fixed by altering these table fields to have corresponding  
> longer lengths?
> ie. does it break something in vchkpw (or qmailadmin)?
> Found some references on the list mentioning limits in vpopmail.h:
>
> #define MAX_PW_NAME         32
> #define MAX_PW_DOMAIN       64
>
> Are these still valid and therefore require changes to the code and  
> recompilation in order to conform with the RFC?

This problem is solved.
Upgrade to 5.4.18 and/or read the UPGRADE file of 5.4.18.

Ciao
-- 
Alessio Cecchi is:
@ ILS -> http://www.linux.it/~alessice/
Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/
@ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it
@ LOLUG -> neo-Socio http://www.lolug.net

!DSPAM:48f32cc432311148314093!