[vchkpw] [SPAM] Auto-Re: [vchkpw] [SPAM] Emailed Invoice - 782867

[zhaopin]

尊敬的同学：您好！

您的求职简历已经收到，我们会尽快进行阅评，之后再决定是否与您面谈！


  中信泰富（中国）投资有限公司
 人力资源部

!DSPAM:59e8863641491084871729!

Re: [vchkpw] [SPAM] Password strength bug

[Drew Wells]

On 09/21/2015 03:02 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/21/2015 08:55 AM, Drew Wells wrote:

I think that permitting a null password, if policy does not admit it, is a 
security hole.
Prefer you you add another explicit call to be called for no password checking 
(at all).

Regards,

Tonino



This is going to be the patch I use here, does anyone want this patch ?

Wouldn't it actually be easier to remove the password parameter from vadduser() 
and then
vadduser.c can add a user (without a password) and then optionally set a 
password using
vauth_setpw() ?  This is exactly what it should do at the moment for adding a 
user with a crypted
password, the user is added, then the crypted password is set using 
vauth_setpw().

Because vadduser() previously supported an empty password ("\0"), the change to 
check for this and
skip the password strength testing won't be changing its functionality.  The 
password strength check
was not meant to prevent blank passwords, so the fact that it broke the ability 
to set one would be
a bug, and skipping the call to the password strength checker would be a bug 
fix.  vadduser should
not, however, be called with a NULL password.

That was exactly what my original patch on the 15th Sept. did and the 
patch is attached to my original message.  I have not attached my NULL 
password changes patch.  I'll revert the patch I use here to my original 
one.


While looking at all this I have noticed that vmoduser.c allows the 
setting of a "clear_text_password" (-C) but does not do any 
password_strength() testing, is this also a bug ?  Lastly, there does 
not seem to be a way of setting "no password" on an account once it has 
been created, is this correct ?


Do you have any idea what needs to be done with regard to some of the 
backends being able to accept a NULL gecos ?


!DSPAM:5600119641556874115760!

Re: [vchkpw] [SPAM] Password strength bug

[Matt Brookings]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/21/2015 08:55 AM, Drew Wells wrote:
>> I think that permitting a null password, if policy does not admit it, is a 
>> security hole. 
>> Prefer you you add another explicit call to be called for no password 
>> checking (at all).
>> 
>> Regards,
>> 
>> Tonino
>> 
>> 
>>> 
>>> This is going to be the patch I use here, does anyone want this patch ?
>> 
> Wouldn't it actually be easier to remove the password parameter from 
> vadduser() and then
> vadduser.c can add a user (without a password) and then optionally set a 
> password using
> vauth_setpw() ?  This is exactly what it should do at the moment for adding a 
> user with a crypted
> password, the user is added, then the crypted password is set using 
> vauth_setpw().

Because vadduser() previously supported an empty password ("\0"), the change to 
check for this and
skip the password strength testing won't be changing its functionality.  The 
password strength check
was not meant to prevent blank passwords, so the fact that it broke the ability 
to set one would be
a bug, and skipping the call to the password strength checker would be a bug 
fix.  vadduser should
not, however, be called with a NULL password.
- -- 
/*
Matt BrookingsGnuPG Key 62817373
Software developer Systems technician
Inter7 Internet Technologies, Inc. (815)776-9465
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWAA4BAAoJEOjQVexigXNzO1EH/iZtAFYiimKNefgU2mgzAwDf
N639Vq/zN6yDtImnBa9lVW37YZQ9IQ1jCNuQZCk91oUQbagMTP37Q3L+HRsGxcHt
tYEmKjvJXFiqNSuBZfmdFdbr8ENz4mvS0GI3VsE02fXUpMLSXAnIUfv+cnN5bCxD
cEs9aEcNQTntcZzKiUWYW+62MpX3BDbZarOpnHmQznihzorn5wcT12gSQo3QGjxp
ZM5LF9UBXOSuus5hFZHxLPQKhcZCvYSS0SpM+hyjLE4JB2nKEiDAVzZ7kqNi6ZV2
K2ocqLDRg1qpXIFGeB2yqobdXSVLEcb9takRE1xAe+v2Ya3YBK09fyBqewfo2qU=
=B/v4
-END PGP SIGNATURE-

Re: [vchkpw] [SPAM] Password strength bug

[Drew Wells]

On 09/21/2015 02:26 PM, Tonix - Antonio Nati wrote:

Il 21/09/2015 14:59, Drew Wells ha scritto:

On 09/17/2015 12:28 PM, Tonix - Antonio Nati wrote:

Il 17/09/2015 13:18, Drew Wells ha scritto:

On 09/15/2015 03:27 PM, Tonix - Antonio Nati wrote:

Il 15/09/2015 15:03, Drew Wells ha scritto:

On 09/15/2015 11:00 AM, Tonix - Antonio Nati wrote:

Il 15/09/2015 11:03, Drew Wells ha scritto:
In vpopmail-5.5.0 there seems to be a bug in vpopmail.c where 
the password strength is checked even if a password isn't used 
(such as when -e is used to add the encrypted password).  Patch 
attached.







I do not understand the problem.

Of course password strenght is checked every time, and if it 
founds a null/empty password it gives error back if password 
must have a minimum lenght.


Your patch instead permit to have null password even if strenght 
policy would not allow it.


Regards,

Tonino
The problem is is that vadduser.c can call vadduser() (in 
vpopmail.c) without a password.  It does this in the situation 
where vadduser.c has had the options "-e" or "-n" passed to it, 
so if this is the case the password can't be checked againts the 
password strength rules. The underlying function vadduser() needs 
to be able to add a user with no password.




I realize additional controls are done before calling vadduser(); 
but I personally would prefer an explicit parameter added to 
vadduser for avoiding password check (it may be a further 
parameter having default = "check").
It would make developers more protected against unwanted security 
bugs.


Regards,

Tonino

I agree that it would be better to explicitly indicate to 
vadduser() that no password is wanted.  I even looked quicky at 
setting the password to NULL to indicate no password, but both this 
and an explicit parameter would need changes to all the backends, 
so have left it as is for now.


It could be done in two ways:

  * considering most od c compilers are c++ compilers, and that
means we can add an implicit parameter (, nocheck_pwd = 0)
  * duplicate the function for this usage, and call the duplicated
function from avdduser when needed.

Regards,

Tonino

I have looked at the backends and it turns out that some of the 
backends can handle a NULL gecos, so expanding on this I have changed 
all the backends to be able to handle a NULL gecos (in which case 
they now all use the user as a gecos) and also handle a NULL 
password.  So vadduser.c can pass a NULL password to vadduser(), 
vadduser() can then check the password_strength() when the password 
is not NULL.


I think that permitting a null password, if policy does not admit it, 
is a security hole.
Prefer you you add another explicit call to be called for no password 
checking (at all).


Regards,

Tonino




This is going to be the patch I use here, does anyone want this patch ?


Wouldn't it actually be easier to remove the password parameter from 
vadduser() and then vadduser.c can add a user (without a password) and 
then optionally set a password using vauth_setpw() ?  This is exactly 
what it should do at the moment for adding a user with a crypted 
password, the user is added, then the crypted password is set using 
vauth_setpw().



!DSPAM:56000c6d41552022747047!

Re: [vchkpw] [SPAM] Password strength bug

[Tonix - Antonio Nati]

Il 21/09/2015 14:59, Drew Wells ha scritto:

On 09/17/2015 12:28 PM, Tonix - Antonio Nati wrote:

Il 17/09/2015 13:18, Drew Wells ha scritto:

On 09/15/2015 03:27 PM, Tonix - Antonio Nati wrote:

Il 15/09/2015 15:03, Drew Wells ha scritto:

On 09/15/2015 11:00 AM, Tonix - Antonio Nati wrote:

Il 15/09/2015 11:03, Drew Wells ha scritto:
In vpopmail-5.5.0 there seems to be a bug in vpopmail.c where 
the password strength is checked even if a password isn't used 
(such as when -e is used to add the encrypted password).  Patch 
attached.







I do not understand the problem.

Of course password strenght is checked every time, and if it 
founds a null/empty password it gives error back if password must 
have a minimum lenght.


Your patch instead permit to have null password even if strenght 
policy would not allow it.


Regards,

Tonino
The problem is is that vadduser.c can call vadduser() (in 
vpopmail.c) without a password.  It does this in the situation 
where vadduser.c has had the options "-e" or "-n" passed to it, so 
if this is the case the password can't be checked againts the 
password strength rules.  The underlying function vadduser() needs 
to be able to add a user with no password.




I realize additional controls are done before calling vadduser(); 
but I personally would prefer an explicit parameter added to 
vadduser for avoiding password check (it may be a further parameter 
having default = "check").

It would make developers more protected against unwanted security bugs.

Regards,

Tonino

I agree that it would be better to explicitly indicate to vadduser() 
that no password is wanted.  I even looked quicky at setting the 
password to NULL to indicate no password, but both this and an 
explicit parameter would need changes to all the backends, so have 
left it as is for now.


It could be done in two ways:

  * considering most od c compilers are c++ compilers, and that means
we can add an implicit parameter (, nocheck_pwd = 0)
  * duplicate the function for this usage, and call the duplicated
function from avdduser when needed.

Regards,

Tonino

I have looked at the backends and it turns out that some of the 
backends can handle a NULL gecos, so expanding on this I have changed 
all the backends to be able to handle a NULL gecos (in which case they 
now all use the user as a gecos) and also handle a NULL password.  So 
vadduser.c can pass a NULL password to vadduser(), vadduser() can then 
check the password_strength() when the password is not NULL.


I think that permitting a null password, if policy does not admit it, is 
a security hole.
Prefer you you add another explicit call to be called for no password 
checking (at all).


Regards,

Tonino




This is going to be the patch I use here, does anyone want this patch ?
 



--

Inter@zioniInterazioni di Antonio Nati
   http://www.interazioni.it  to...@interazioni.it




!DSPAM:5600059741551931516382!

Re: [vchkpw] [SPAM] Password strength bug

[Drew Wells]

On 09/17/2015 12:28 PM, Tonix - Antonio Nati wrote:

Il 17/09/2015 13:18, Drew Wells ha scritto:

On 09/15/2015 03:27 PM, Tonix - Antonio Nati wrote:

Il 15/09/2015 15:03, Drew Wells ha scritto:

On 09/15/2015 11:00 AM, Tonix - Antonio Nati wrote:

Il 15/09/2015 11:03, Drew Wells ha scritto:
In vpopmail-5.5.0 there seems to be a bug in vpopmail.c where the 
password strength is checked even if a password isn't used (such 
as when -e is used to add the encrypted password).  Patch attached.







I do not understand the problem.

Of course password strenght is checked every time, and if it 
founds a null/empty password it gives error back if password must 
have a minimum lenght.


Your patch instead permit to have null password even if strenght 
policy would not allow it.


Regards,

Tonino
The problem is is that vadduser.c can call vadduser() (in 
vpopmail.c) without a password.  It does this in the situation 
where vadduser.c has had the options "-e" or "-n" passed to it, so 
if this is the case the password can't be checked againts the 
password strength rules.  The underlying function vadduser() needs 
to be able to add a user with no password.




I realize additional controls are done before calling vadduser(); 
but I personally would prefer an explicit parameter added to 
vadduser for avoiding password check (it may be a further parameter 
having default = "check").

It would make developers more protected against unwanted security bugs.

Regards,

Tonino

I agree that it would be better to explicitly indicate to vadduser() 
that no password is wanted.  I even looked quicky at setting the 
password to NULL to indicate no password, but both this and an 
explicit parameter would need changes to all the backends, so have 
left it as is for now.


It could be done in two ways:

  * considering most od c compilers are c++ compilers, and that means
we can add an implicit parameter (, nocheck_pwd = 0)
  * duplicate the function for this usage, and call the duplicated
function from avdduser when needed.

Regards,

Tonino

I have looked at the backends and it turns out that some of the backends 
can handle a NULL gecos, so expanding on this I have changed all the 
backends to be able to handle a NULL gecos (in which case they now all 
use the user as a gecos) and also handle a NULL password.  So vadduser.c 
can pass a NULL password to vadduser(), vadduser() can then check the 
password_strength() when the password is not NULL.


This is going to be the patch I use here, does anyone want this patch ?


!DSPAM:552d41551245420391!

Re: [vchkpw] [SPAM] valias remove alias

[Matt Brookings]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/18/2015 09:30 AM, Drew Wells wrote:
> On 09/18/2015 03:23 PM, Matt Brookings wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>> 
>> Applies perfectly!  Thanks!
>> 
>> On 09/18/2015 09:21 AM, Drew Wells wrote:
>>> On 09/18/2015 02:47 PM, Matt Brookings wrote:
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
 
 Drew, I know you've put a lot of effort into these patches, but they do 
 not succeed
 against the 5.5.0 trunk.  Patches should be made against the most recent 
 revision, which
 can be checked out via Subversion from Sourceforge.
 
 On 09/18/2015 08:11 AM, Drew Wells wrote:
> On 09/17/2015 04:55 PM, Matt Brookings wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>> 
>> On 09/17/2015 10:52 AM, Drew Wells wrote:
> I basically did a diff from 5.4.29 to 5.4.33 and implemented that 
> diff to 5.5.0,
> some of it had already been done to 5.5.0 and alot of it centered 
> around the
> snprintf tidy up's and the string_list implementation. The attached 
> patch does
> not include any of the changes I recently sent to the mailing list, 
> just the
> changes from 5.4.[29->33].
>>> This patch was generated from the 5.5.0 .tar.bz2, I had a look at SVN 
>>> trunk and from
>>> what I could see, it was 5.4.34.
>> The trunk on Sourceforge is the current 5.5.0.  The 5.4 series only 
>> appears in the
>> tags and branches area now.  I'll look over this patch and get it 
>> applied.  Thanks for
>> putting it together!
>> 
> And lastly for now, someone has done a lot of work in tidying up/making 
> safe all the
> calls to snprintf(), the attached patch completes this work (I think).  
> This patch comes
> after the 5.4.[29->33] patch I did.
> 
> 
>>> Ok, have have downloaded a snapshot .zip file from Sourceforge 
>>> (vpopmail-code-1034.zip) and 
>>> applied the changes to that and attached the patch.  This is the 
>>> 5.4.[29-33] changes patch,
>>> I'll do the snprintf() one later.  Let me know if you need me to do 
>>> anything else with it.
>> 
> Not a problem do excuse my use of the 5.5.0 tar, I'll use SVN trunk from now 
> on.  Here is the 
> snprintf() patch for vpopmail-code-1034.zip.

No problem.  Thanks for your work!
- -- 
/*
Matt BrookingsGnuPG Key 62817373
Software developer Systems technician
Inter7 Internet Technologies, Inc. (815)776-9465
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJV/CJIAAoJEOjQVexigXNzUEQH+wV4Si57TawcIHdnggKhZpav
6Swf4CUPZIfLrM6chNkIrTnR2seb0W3qCIqmMdbo3nzUIfLzMw3ZOikCBKF6hoWq
zQUij+eXwTLWe8JbT4/c3fACBmq4BspJj7q4kIAeypu4hqdjDpxAxVvNmoYh3FCQ
CC3LX0E3PbPHp7mKgzXRQtVrnB9ePxTgu9ZR529BUpI4dwz2FXx+FgmcC/hvBFad
mOBh5vYgVfql0rGWmw/TkWLRNxJzR4ffHIYg7h1jJ6QSMrn/Px4pdGNmOzGIf+tV
asoUPWUIKLL1MlPeV/jviTw0Or7es6ZGbsd+pZl6TEkhowySGB72oexrVTDQXF4=
=ZHVf
-END PGP SIGNATURE-

Re: [vchkpw] [SPAM] valias remove alias

[Drew Wells]

On 09/18/2015 03:23 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Applies perfectly!  Thanks!

On 09/18/2015 09:21 AM, Drew Wells wrote:

On 09/18/2015 02:47 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1

Drew, I know you've put a lot of effort into these patches, but they do not 
succeed against
the 5.5.0 trunk.  Patches should be made against the most recent revision, 
which can be checked
out via Subversion from Sourceforge.

On 09/18/2015 08:11 AM, Drew Wells wrote:

On 09/17/2015 04:55 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1

On 09/17/2015 10:52 AM, Drew Wells wrote:

I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff to 
5.5.0, some
of it had already been done to 5.5.0 and alot of it centered around the 
snprintf tidy
up's and the string_list implementation. The attached patch does not include 
any of
the changes I recently sent to the mailing list, just the changes from 
5.4.[29->33].

This patch was generated from the 5.5.0 .tar.bz2, I had a look at SVN trunk and 
from what
I could see, it was 5.4.34.

The trunk on Sourceforge is the current 5.5.0.  The 5.4 series only appears in 
the tags
and branches area now.  I'll look over this patch and get it applied.  Thanks 
for putting
it together!


And lastly for now, someone has done a lot of work in tidying up/making safe 
all the calls
to snprintf(), the attached patch completes this work (I think).  This patch 
comes after the
5.4.[29->33] patch I did.



Ok, have have downloaded a snapshot .zip file from Sourceforge 
(vpopmail-code-1034.zip) and
applied the changes to that and attached the patch.  This is the 5.4.[29-33] 
changes patch, I'll
do the snprintf() one later.  Let me know if you need me to do anything else 
with it.


Not a problem do excuse my use of the 5.5.0 tar, I'll use SVN trunk from 
now on.  Here is the snprintf() patch for vpopmail-code-1034.zip.



!DSPAM:55fc201141551341917110!
diff -uPr vpopmail-code-1034-trunk.orig/vpopmaild.c 
vpopmail-code-1034-trunk/vpopmaild.c
--- vpopmail-code-1034-trunk.orig/vpopmaild.c   2015-09-18 15:00:27.747095095 
+0100
+++ vpopmail-code-1034-trunk/vpopmaild.c2015-09-18 15:24:04.655095039 
+0100
@@ -429,7 +429,7 @@
 return(-2);
   } 
 
-//  snprintf(WriteBuf,sizeof(WriteBuf), RET_OK_MORE);
+//  snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK_MORE);
 //  wait_write();
 
   AuthVpw.pw_name = strdup(tmpvpw->pw_name);
@@ -460,7 +460,7 @@
 logged_in = 1;
 
   if(output_type < 2 ) {
-snprintf(WriteBuf,sizeof(WriteBuf), RET_OK_MORE);
+snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK_MORE);
 wait_write();
 
 snprintf(WriteBuf,sizeof(WriteBuf), "vpopmail_dir_bin %s" RET_CRLF, 
VPOPMAIL_DIR_BIN);
@@ -485,10 +485,10 @@
 
 send_user_info(&AuthVpw);
 
-snprintf(WriteBuf, sizeof(WriteBuf), "." RET_CRLF);
+snprintf(WriteBuf, sizeof(WriteBuf), "%s", "." RET_CRLF);
   }
   else
-snprintf(WriteBuf,sizeof(WriteBuf), RET_OK);
+snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK);
 
   return(0);
 }
@@ -525,7 +525,7 @@
 return(-1);
   }
 
-  snprintf(WriteBuf,sizeof(WriteBuf), RET_OK);
+  snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK);
   if ((ret=vadduser(TmpUser, TmpDomain, password, TmpUser, USE_POP )) < 0 ) {
 snprintf(WriteBuf,sizeof(WriteBuf),RET_ERR "0.305 %s" RET_CRLF, 
verror(ret));
 return(-1);
@@ -564,7 +564,7 @@
 return(-1);
   }
 
-  snprintf(WriteBuf,sizeof(WriteBuf), RET_OK);
+  snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK);
   return(0);
 }
 
@@ -626,7 +626,7 @@
   }
   
 
-  snprintf(WriteBuf,sizeof(WriteBuf), RET_OK);
+  snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK);
   wait_write();
 
   while(fgets(ReadBuf,sizeof(ReadBuf),stdin)!=NULL ) {
@@ -751,7 +751,7 @@
   if ( (ret=vauth_setpw( tmpvpw, TmpDomain )) != 0 ) {
 snprintf(WriteBuf,sizeof(WriteBuf),RET_ERR "0.507 %s" RET_CRLF, 
verror(ret)); 
   } else {
-snprintf(WriteBuf,sizeof(WriteBuf), RET_OK);
+snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK);
   }
 
   return(0);
@@ -787,11 +787,11 @@
 return(-1);
   } 
 
-  snprintf(WriteBuf,sizeof(WriteBuf), RET_OK_MORE);
+  snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK_MORE);
   wait_write();
 
   send_user_info(tmpvpw);
-  snprintf(WriteBuf, sizeof(WriteBuf), "." RET_CRLF);
+  snprintf(WriteBuf, sizeof(WriteBuf), "%s", "." RET_CRLF);
   return(0);
 
 }
@@ -826,120 +826,79 @@
 
   } else {
 
-if ( tmpvpw->pw_gid & NO_PASSWD_CHNG ) {
-  snprintf(WriteBuf, sizeof(WriteBuf), "no_password_change 1" RET_CRLF);
-} else {
-  snprintf(WriteBuf, sizeof(WriteBuf), "no_password_change 0" RET_CRLF);
-}
+snprintf(WriteBuf, sizeof(WriteBuf), "no_password_change %d" RET_CRLF,
+  tmpvpw->pw_gid & NO_PASSWD_CHNG ? 1 : 0);
 wait_write();
 
-if ( tmpvpw->pw_gid & NO_POP ) {
-  snprintf(WriteBuf, sizeof(WriteBuf), "no_pop 1" RET_CRLF);
-} else {
-  snprintf(WriteBuf, sizeof(W

Re: [vchkpw] [SPAM] valias remove alias

[Matt Brookings]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Applies perfectly!  Thanks!

On 09/18/2015 09:21 AM, Drew Wells wrote:
> On 09/18/2015 02:47 PM, Matt Brookings wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>> 
>> Drew, I know you've put a lot of effort into these patches, but they do not 
>> succeed against
>> the 5.5.0 trunk.  Patches should be made against the most recent revision, 
>> which can be checked
>> out via Subversion from Sourceforge.
>> 
>> On 09/18/2015 08:11 AM, Drew Wells wrote:
>>> On 09/17/2015 04:55 PM, Matt Brookings wrote:
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
 
 On 09/17/2015 10:52 AM, Drew Wells wrote:
>>> I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff 
>>> to 5.5.0, some
>>> of it had already been done to 5.5.0 and alot of it centered around the 
>>> snprintf tidy
>>> up's and the string_list implementation. The attached patch does not 
>>> include any of
>>> the changes I recently sent to the mailing list, just the changes from 
>>> 5.4.[29->33].
> This patch was generated from the 5.5.0 .tar.bz2, I had a look at SVN 
> trunk and from what
> I could see, it was 5.4.34.
 The trunk on Sourceforge is the current 5.5.0.  The 5.4 series only 
 appears in the tags
 and branches area now.  I'll look over this patch and get it applied.  
 Thanks for putting
 it together!
 
>>> And lastly for now, someone has done a lot of work in tidying up/making 
>>> safe all the calls
>>> to snprintf(), the attached patch completes this work (I think).  This 
>>> patch comes after the 
>>> 5.4.[29->33] patch I did.
>>> 
>>> 
>> 
> Ok, have have downloaded a snapshot .zip file from Sourceforge 
> (vpopmail-code-1034.zip) and
> applied the changes to that and attached the patch.  This is the 5.4.[29-33] 
> changes patch, I'll
> do the snprintf() one later.  Let me know if you need me to do anything else 
> with it.


- -- 
/*
Matt BrookingsGnuPG Key 62817373
Software developer Systems technician
Inter7 Internet Technologies, Inc. (815)776-9465
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJV/B5kAAoJEOjQVexigXNzlWwH/1o/g8l2Uu6CrUiiLn7PimWj
SXu5BMt3d2SdHeZGHTkUEEVlauuHPVwL2tkFmi5bffz9334ZwjqMWqneofBjZiie
E8LLnl6KV0CV1CXCOavJ7eDooVUKZBbaTD+zIUoKsfwWP52qyyed5a8z1JUZ30tN
uBnodHxkJegawZ4c0YewE0q/sY9X066MoPOx/Iwq93tIeS4ueJs8InAEC6XuIBVY
Y99AhK0tWmi/3EgxpS+ng/wUChjmzbY2M94/Tqw+OJ9/FOQW2Zqw/aWV/VetKlPS
q8zdHKG9dPhVgrXhn09WaOYOVzw5tuihhUWUuxiJr1mxZud6PdMTPdjcFOkopCs=
=LO8b
-END PGP SIGNATURE-

Re: [vchkpw] [SPAM] valias remove alias

[Drew Wells]

On 09/18/2015 02:47 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Drew, I know you've put a lot of effort into these patches, but they do not 
succeed against the
5.5.0 trunk.  Patches should be made against the most recent revision, which 
can be checked out via
Subversion from Sourceforge.

On 09/18/2015 08:11 AM, Drew Wells wrote:

On 09/17/2015 04:55 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1

On 09/17/2015 10:52 AM, Drew Wells wrote:

I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff to 
5.5.0, some of
it had already been done to 5.5.0 and alot of it centered around the snprintf 
tidy up's
and the string_list implementation. The attached patch does not include any of 
the
changes I recently sent to the mailing list, just the changes from 5.4.[29->33].

This patch was generated from the 5.5.0 .tar.bz2, I had a look at SVN trunk and 
from what I
could see, it was 5.4.34.

The trunk on Sourceforge is the current 5.5.0.  The 5.4 series only appears in 
the tags and
branches area now.  I'll look over this patch and get it applied.  Thanks for 
putting it
together!


And lastly for now, someone has done a lot of work in tidying up/making safe 
all the calls to
snprintf(), the attached patch completes this work (I think).  This patch comes 
after the
5.4.[29->33] patch I did.




Ok, have have downloaded a snapshot .zip file from Sourceforge 
(vpopmail-code-1034.zip) and applied the changes to that and attached 
the patch.  This is the 5.4.[29-33] changes patch, I'll do the 
snprintf() one later.  Let me know if you need me to do anything else 
with it.



!DSPAM:55fc1de841551347274186!
diff -uPr vpopmail-code-1034-trunk.orig/backends/mysql/vmysql.c 
vpopmail-code-1034-trunk/backends/mysql/vmysql.c
--- vpopmail-code-1034-trunk.orig/backends/mysql/vmysql.c   2010-10-26 
18:15:36.0 +0100
+++ vpopmail-code-1034-trunk/backends/mysql/vmysql.c2015-09-18 
15:00:09.810096680 +0100
@@ -1785,10 +1785,10 @@
 limits->maxforwards = atoi(row[2]);
 limits->maxautoresponders = atoi(row[3]);
 limits->maxmailinglists = atoi(row[4]);
-limits->diskquota = atoi(row[5]);
-limits->maxmsgcount = atoi(row[6]);
-limits->defaultquota = atoi(row[7]);
-limits->defaultmaxmsgcount = atoi(row[8]);
+limits->diskquota = strtoll(row[5], NULL, 10);
+limits->maxmsgcount = strtoll(row[6], NULL, 10);
+limits->defaultquota = strtoll(row[7], NULL, 10);
+limits->defaultmaxmsgcount = strtoll(row[8], NULL, 10);
 limits->disable_pop = atoi(row[9]);
 limits->disable_imap = atoi(row[10]);
 limits->disable_dialup = atoi(row[11]);
@@ -1808,8 +1808,8 @@
 limits->perm_maillist_users = perm & VLIMIT_DISABLE_ALL;
 perm >>= VLIMIT_DISABLE_BITS;
 limits->perm_maillist_moderators = perm & VLIMIT_DISABLE_ALL;
-limits->perm_quota = atoi(row[23]);
-limits->perm_defaultquota = atoi(row[24]);
+limits->perm_quota = strtoll(row[23], NULL, 10);
+limits->perm_defaultquota = strtoll(row[24], NULL, 10);
 }
 mysql_free_result(res_read);
 
@@ -1830,7 +1830,7 @@
 "diskquota = %d, maxmsgcount = %d, defaultquota = %d, 
defaultmaxmsgcount = %d, "
 "disable_pop = %d, disable_imap = %d, disable_dialup = %d, "
 "disable_passwordchanging = %d, disable_webmail = %d, disable_relay = 
%d, "
-"disable_smtp = %d, disable_spamassassin = %d, delete_spam = %d, 
perm_account = %d, "
+"disable_smtp = %d, disable_spamassassin = %d, delete_spam = %d, 
disable_maildrop = %d, perm_account = %d, "
 "perm_alias = %d, perm_forward = %d, perm_autoresponder = %d, 
perm_maillist = %d, "
 "perm_quota = %d, perm_defaultquota = %d "
 "ON DUPLICATE KEY UPDATE "
@@ -1847,7 +1847,7 @@
 limits->diskquota, limits->maxmsgcount, limits->defaultquota, 
limits->defaultmaxmsgcount,
 limits->disable_pop, limits->disable_imap, limits->disable_dialup,
 limits->disable_passwordchanging, limits->disable_webmail, 
limits->disable_relay,
-limits->disable_smtp, limits->disable_spamassassin, 
limits->delete_spam, limits->perm_account,
+limits->disable_smtp, limits->disable_spamassassin, 
limits->delete_spam, limits->disable_maildrop, limits->perm_account,
 limits->perm_alias, limits->perm_forward, limits->perm_autoresponder,
 (limits->perm_maillist |
 (limits->perm_maillist_users << VLIMIT_DISABLE_BITS) |
diff -uPr vpopmail-code-1034-trunk.orig/backends/mysql/vmysql.h.in 
vpopmail-code-1034-trunk/backends/mysql/vmysql.h.in
--- vpopmail-code-1034-trunk.orig/backends/mysql/vmysql.h.in2010-10-26 
18:15:36.0 +0100
+++ vpopmail-code-1034-trunk/backends/mysql/vmysql.h.in 2015-09-18 
15:00:09.810096680 +0100
@@ -268,10 +268,10 @@
   maxforwards  INT(10) NOT NULL DEFAULT -1, \
   maxautoresponders

Re: [vchkpw] [SPAM] valias remove alias

[Matt Brookings]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Drew, I know you've put a lot of effort into these patches, but they do not 
succeed against the
5.5.0 trunk.  Patches should be made against the most recent revision, which 
can be checked out via
Subversion from Sourceforge.

On 09/18/2015 08:11 AM, Drew Wells wrote:
> On 09/17/2015 04:55 PM, Matt Brookings wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>> 
>> On 09/17/2015 10:52 AM, Drew Wells wrote:
> I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff to 
> 5.5.0, some of
> it had already been done to 5.5.0 and alot of it centered around the 
> snprintf tidy up's
> and the string_list implementation. The attached patch does not include 
> any of the
> changes I recently sent to the mailing list, just the changes from 
> 5.4.[29->33].
>>> This patch was generated from the 5.5.0 .tar.bz2, I had a look at SVN trunk 
>>> and from what I
>>> could see, it was 5.4.34.
>> The trunk on Sourceforge is the current 5.5.0.  The 5.4 series only appears 
>> in the tags and
>> branches area now.  I'll look over this patch and get it applied.  Thanks 
>> for putting it
>> together!
>> 
> And lastly for now, someone has done a lot of work in tidying up/making safe 
> all the calls to 
> snprintf(), the attached patch completes this work (I think).  This patch 
> comes after the
> 5.4.[29->33] patch I did.
> 
> 


- -- 
/*
Matt BrookingsGnuPG Key 62817373
Software developer Systems technician
Inter7 Internet Technologies, Inc. (815)776-9465
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJV/BXnAAoJEOjQVexigXNzPxkH/jKWMcIwdkpN9xy8OhYHQGuF
+FwowoDJSsEpkJU6flSSWjYvpC0/NJeejzWLWHW0bq7m0ulobpq4z4x4Q7lUlxId
nu7a4+v29qgDw3ccuyIpx+DmgF2DEqi7t/QZlTNeCJ4YzsMBkcUrJI8twoF+RTX/
/8aifV4/+J69V5GrKAMePRIRIaZicVd0NNgLrnaG096r8r7n02jH5G2PTPF0s6Vh
AVaSehh7sxTCBlm8sH08orxLRqRsLakvy3zlxogeLnipJxWLxgQQdkAL8GcfvPIz
LPlXovqegvNtEGrmsAwIP6mXansd0qqC0vTDpUz4ikHXso7ntKHRieHrT4lrevE=
=tzfn
-END PGP SIGNATURE-

Re: [vchkpw] [SPAM] valias remove alias

[Drew Wells]

On 09/17/2015 04:55 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/17/2015 10:52 AM, Drew Wells wrote:

I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff to 
5.5.0, some of it
had already been done to 5.5.0 and alot of it centered around the snprintf tidy 
up's and the
string_list implementation. The attached patch does not include any of the 
changes I
recently sent to the mailing list, just the changes from 5.4.[29->33].

This patch was generated from the 5.5.0 .tar.bz2, I had a look at SVN trunk and 
from what I could
see, it was 5.4.34.

The trunk on Sourceforge is the current 5.5.0.  The 5.4 series only appears in 
the tags and branches
area now.  I'll look over this patch and get it applied.  Thanks for putting it 
together!

And lastly for now, someone has done a lot of work in tidying up/making 
safe all the calls to snprintf(), the attached patch completes this work 
(I think).  This patch comes after the 5.4.[29->33] patch I did.



!DSPAM:55fc0d7341552094314991!
diff -uPr vpopmail-5.5.0.orig/vpopmaild.c vpopmail-5.5.0/vpopmaild.c
--- vpopmail-5.5.0.orig/vpopmaild.c 2015-09-18 13:58:22.048093642 +0100
+++ vpopmail-5.5.0/vpopmaild.c  2015-09-18 14:08:11.117095122 +0100
@@ -429,7 +429,7 @@
 return(-2);
   } 
 
-//  snprintf(WriteBuf,sizeof(WriteBuf), RET_OK_MORE);
+//  snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK_MORE);
 //  wait_write();
 
   AuthVpw.pw_name = strdup(tmpvpw->pw_name);
@@ -460,7 +460,7 @@
 logged_in = 1;
 
   if(output_type < 2 ) {
-snprintf(WriteBuf,sizeof(WriteBuf), RET_OK_MORE);
+snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK_MORE);
 wait_write();
 
 snprintf(WriteBuf,sizeof(WriteBuf), "vpopmail_dir_bin %s" RET_CRLF, 
VPOPMAIL_DIR_BIN);
@@ -485,10 +485,10 @@
 
 send_user_info(&AuthVpw);
 
-snprintf(WriteBuf, sizeof(WriteBuf), "." RET_CRLF);
+snprintf(WriteBuf, sizeof(WriteBuf), "%s", "." RET_CRLF);
   }
   else
-snprintf(WriteBuf,sizeof(WriteBuf), RET_OK);
+snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK);
 
   return(0);
 }
@@ -525,7 +525,7 @@
 return(-1);
   }
 
-  snprintf(WriteBuf,sizeof(WriteBuf), RET_OK);
+  snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK);
   if ((ret=vadduser(TmpUser, TmpDomain, password, TmpUser, USE_POP )) < 0 ) {
 snprintf(WriteBuf,sizeof(WriteBuf),RET_ERR "0.305 %s" RET_CRLF, 
verror(ret));
 return(-1);
@@ -564,7 +564,7 @@
 return(-1);
   }
 
-  snprintf(WriteBuf,sizeof(WriteBuf), RET_OK);
+  snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK);
   return(0);
 }
 
@@ -626,7 +626,7 @@
   }
   
 
-  snprintf(WriteBuf,sizeof(WriteBuf), RET_OK);
+  snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK);
   wait_write();
 
   while(fgets(ReadBuf,sizeof(ReadBuf),stdin)!=NULL ) {
@@ -751,7 +751,7 @@
   if ( (ret=vauth_setpw( tmpvpw, TmpDomain )) != 0 ) {
 snprintf(WriteBuf,sizeof(WriteBuf),RET_ERR "0.507 %s" RET_CRLF, 
verror(ret)); 
   } else {
-snprintf(WriteBuf,sizeof(WriteBuf), RET_OK);
+snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK);
   }
 
   return(0);
@@ -787,11 +787,11 @@
 return(-1);
   } 
 
-  snprintf(WriteBuf,sizeof(WriteBuf), RET_OK_MORE);
+  snprintf(WriteBuf,sizeof(WriteBuf), "%s", RET_OK_MORE);
   wait_write();
 
   send_user_info(tmpvpw);
-  snprintf(WriteBuf, sizeof(WriteBuf), "." RET_CRLF);
+  snprintf(WriteBuf, sizeof(WriteBuf), "%s", "." RET_CRLF);
   return(0);
 
 }
@@ -826,120 +826,79 @@
 
   } else {
 
-if ( tmpvpw->pw_gid & NO_PASSWD_CHNG ) {
-  snprintf(WriteBuf, sizeof(WriteBuf), "no_password_change 1" RET_CRLF);
-} else {
-  snprintf(WriteBuf, sizeof(WriteBuf), "no_password_change 0" RET_CRLF);
-}
+snprintf(WriteBuf, sizeof(WriteBuf), "no_password_change %d" RET_CRLF,
+  tmpvpw->pw_gid & NO_PASSWD_CHNG ? 1 : 0);
 wait_write();
 
-if ( tmpvpw->pw_gid & NO_POP ) {
-  snprintf(WriteBuf, sizeof(WriteBuf), "no_pop 1" RET_CRLF);
-} else {
-  snprintf(WriteBuf, sizeof(WriteBuf), "no_pop 0" RET_CRLF);
-}
+snprintf(WriteBuf, sizeof(WriteBuf), "no_pop %d" RET_CRLF,
+  tmpvpw->pw_gid & NO_POP ? 1 : 0);
 wait_write();
 
-if ( tmpvpw->pw_gid & NO_WEBMAIL ) {
-  snprintf(WriteBuf, sizeof(WriteBuf), "no_webmail 1" RET_CRLF);
-} else {
-  snprintf(WriteBuf, sizeof(WriteBuf), "no_webmail 0" RET_CRLF);
-}
+snprintf(WriteBuf, sizeof(WriteBuf), "no_webmail %d" RET_CRLF,
+  tmpvpw->pw_gid & NO_WEBMAIL ? 1 : 0);
 wait_write();
 
-if ( tmpvpw->pw_gid & NO_IMAP ) {
-  snprintf(WriteBuf, sizeof(WriteBuf), "no_imap 1" RET_CRLF);
-} else {
-  snprintf(WriteBuf, sizeof(WriteBuf), "no_imap 0" RET_CRLF);
-}
+snprintf(WriteBuf, sizeof(WriteBuf), "no_imap %d" RET_CRLF,
+  tmpvpw->pw_gid & NO_IMAP ? 1 : 0);
 wait_write();
 
-if ( tmpvpw->pw_gid & BOUNCE_MAIL ) {
-  snprintf(WriteBuf, sizeof(WriteBuf), "bounce_mail 1" RET_CRLF);
-} else {
-  snprintf(WriteBuf, sizeof(WriteBuf), "bounce

Re: [vchkpw] [SPAM] valias remove alias

[Drew Wells]

On 09/17/2015 04:55 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/17/2015 10:52 AM, Drew Wells wrote:

I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff to 
5.5.0, some of it
had already been done to 5.5.0 and alot of it centered around the snprintf tidy 
up's and the
string_list implementation. The attached patch does not include any of the 
changes I
recently sent to the mailing list, just the changes from 5.4.[29->33].

This patch was generated from the 5.5.0 .tar.bz2, I had a look at SVN trunk and 
from what I could
see, it was 5.4.34.

The trunk on Sourceforge is the current 5.5.0.  The 5.4 series only appears in 
the tags and branches
area now.  I'll look over this patch and get it applied.  Thanks for putting it 
together!

I've just noticed a tiny problem with the previous patch I sent, so here 
is an updated version, this version also includes the missing '#include 
"pwstr.h"' in vadduser.c which causes a segfault on my dev environment 
so thought I should just include it.
The tiny problem was "string_list *aliases" instead of "string_list 
aliases" in vadddomain() in vpopmail.c.



!DSPAM:55fbf97841551215118515!
diff -uPr vpopmail-5.5.0.orig/backends/mysql/vmysql.c 
vpopmail-5.5.0/backends/mysql/vmysql.c
--- vpopmail-5.5.0.orig/backends/mysql/vmysql.c 2010-11-05 18:37:23.0 
+
+++ vpopmail-5.5.0/backends/mysql/vmysql.c  2015-09-18 12:36:07.561092988 
+0100
@@ -1785,10 +1785,10 @@
 limits->maxforwards = atoi(row[2]);
 limits->maxautoresponders = atoi(row[3]);
 limits->maxmailinglists = atoi(row[4]);
-limits->diskquota = atoi(row[5]);
-limits->maxmsgcount = atoi(row[6]);
-limits->defaultquota = atoi(row[7]);
-limits->defaultmaxmsgcount = atoi(row[8]);
+limits->diskquota = strtoll(row[5], NULL, 10);
+limits->maxmsgcount = strtoll(row[6], NULL, 10);
+limits->defaultquota = strtoll(row[7], NULL, 10);
+limits->defaultmaxmsgcount = strtoll(row[8], NULL, 10);
 limits->disable_pop = atoi(row[9]);
 limits->disable_imap = atoi(row[10]);
 limits->disable_dialup = atoi(row[11]);
@@ -1808,8 +1808,8 @@
 limits->perm_maillist_users = perm & VLIMIT_DISABLE_ALL;
 perm >>= VLIMIT_DISABLE_BITS;
 limits->perm_maillist_moderators = perm & VLIMIT_DISABLE_ALL;
-limits->perm_quota = atoi(row[23]);
-limits->perm_defaultquota = atoi(row[24]);
+limits->perm_quota = strtoll(row[23], NULL, 10);
+limits->perm_defaultquota = strtoll(row[24], NULL, 10);
 }
 mysql_free_result(res_read);
 
@@ -1830,7 +1830,7 @@
 "diskquota = %d, maxmsgcount = %d, defaultquota = %d, 
defaultmaxmsgcount = %d, "
 "disable_pop = %d, disable_imap = %d, disable_dialup = %d, "
 "disable_passwordchanging = %d, disable_webmail = %d, disable_relay = 
%d, "
-"disable_smtp = %d, disable_spamassassin = %d, delete_spam = %d, 
perm_account = %d, "
+"disable_smtp = %d, disable_spamassassin = %d, delete_spam = %d, 
disable_maildrop = %d, perm_account = %d, "
 "perm_alias = %d, perm_forward = %d, perm_autoresponder = %d, 
perm_maillist = %d, "
 "perm_quota = %d, perm_defaultquota = %d "
 "ON DUPLICATE KEY UPDATE "
@@ -1847,7 +1847,7 @@
 limits->diskquota, limits->maxmsgcount, limits->defaultquota, 
limits->defaultmaxmsgcount,
 limits->disable_pop, limits->disable_imap, limits->disable_dialup,
 limits->disable_passwordchanging, limits->disable_webmail, 
limits->disable_relay,
-limits->disable_smtp, limits->disable_spamassassin, 
limits->delete_spam, limits->perm_account,
+limits->disable_smtp, limits->disable_spamassassin, 
limits->delete_spam, limits->disable_maildrop, limits->perm_account,
 limits->perm_alias, limits->perm_forward, limits->perm_autoresponder,
 (limits->perm_maillist |
 (limits->perm_maillist_users << VLIMIT_DISABLE_BITS) |
diff -uPr vpopmail-5.5.0.orig/backends/mysql/vmysql.h.in 
vpopmail-5.5.0/backends/mysql/vmysql.h.in
--- vpopmail-5.5.0.orig/backends/mysql/vmysql.h.in  2010-11-05 
18:37:23.0 +
+++ vpopmail-5.5.0/backends/mysql/vmysql.h.in   2015-09-18 12:36:07.561092988 
+0100
@@ -268,10 +268,10 @@
   maxforwards  INT(10) NOT NULL DEFAULT -1, \
   maxautorespondersINT(10) NOT NULL DEFAULT -1, \
   maxmailinglists  INT(10) NOT NULL DEFAULT -1, \
-  diskquotaINT(12) NOT NULL DEFAULT 0, \
-  maxmsgcount  INT(12) NOT NULL DEFAULT 0, \
-  defaultquota INT(12) NOT NULL DEFAULT 0, \
-  defaultmaxmsgcount   INT(12) NOT NULL DEFAULT 0, \
+  diskquotaBIGINT UNSIGNED NOT NULL DEFAULT 0, \
+  maxmsgcount  BIGINT UNSIGNED NOT NULL DEFAULT 0, \
+  defaultquota BIGINT UNSIGNED NOT NULL DEFAULT 0, \
+  defaultmaxmsgcoun

Re: [vchkpw] [SPAM] valias remove alias

[Drew Wells]

On 09/17/2015 04:55 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/17/2015 10:52 AM, Drew Wells wrote:

I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff to 
5.5.0, some of it
had already been done to 5.5.0 and alot of it centered around the snprintf tidy 
up's and the
string_list implementation. The attached patch does not include any of the 
changes I
recently sent to the mailing list, just the changes from 5.4.[29->33].

This patch was generated from the 5.5.0 .tar.bz2, I had a look at SVN trunk and 
from what I could
see, it was 5.4.34.

The trunk on Sourceforge is the current 5.5.0.  The 5.4 series only appears in 
the tags and branches
area now.  I'll look over this patch and get it applied.  Thanks for putting it 
together!

Not a problem at all.  As you probably saw there are a few patches I 
sent to the list that cover a couple of other issues with the 5.5.0.tar.bz2.


!DSPAM:55fae2d441556321250516!

Re: [vchkpw] [SPAM] valias remove alias

[Matt Brookings]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/17/2015 10:52 AM, Drew Wells wrote:
>>> I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff to 
>>> 5.5.0, some of it
>>> had already been done to 5.5.0 and alot of it centered around the snprintf 
>>> tidy up's and the 
>>> string_list implementation. The attached patch does not include any of the 
>>> changes I
>>> recently sent to the mailing list, just the changes from 5.4.[29->33].
>> 
> This patch was generated from the 5.5.0 .tar.bz2, I had a look at SVN trunk 
> and from what I could
> see, it was 5.4.34.

The trunk on Sourceforge is the current 5.5.0.  The 5.4 series only appears in 
the tags and branches
area now.  I'll look over this patch and get it applied.  Thanks for putting it 
together!
- -- 
/*
Matt BrookingsGnuPG Key 62817373
Software developer Systems technician
Inter7 Internet Technologies, Inc. (815)776-9465
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJV+uJcAAoJEOjQVexigXNzXowIALkzVHSRgVq3Ojq1Pv32jdI4
vRaX0jDhbhNzDTCPex5tcwLB71olOm2LYzV/GKBoXudeZYz/SjppccCk43FRhZnj
h76PKiI1484e4kRD1JYkgjP85YKh0I5if2eeL28zm7fDb8qwNG3Djs2xyH9m5+wN
nlPfEtF+e1Pi5PBa8WDFHilF+P6XlV5kwxsuXmZV8JD8EogyplMAs1ksteA6tmJH
vXEAB4xJfstVB6l27mxq1VVNqyE0KUN4inCuxVuuS/nUxJI576V6B/kUQ+DyVANj
ce4gD45L7YzWs4PAwnEcdseai82Jag4J6UaRIhLwTYEwridI1D9GnA7ZSHOmoK8=
=Pl67
-END PGP SIGNATURE-

Re: [vchkpw] [SPAM] valias remove alias

[Drew Wells]

On 09/17/2015 04:04 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Was this patch generated with the SVN trunk (5.5.0)?

On 09/17/2015 09:57 AM, Drew Wells wrote:

On 09/17/2015 03:37 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1

On 09/17/2015 06:23 AM, Drew Wells wrote:

I have created a patch for vpopmail-5.5.0 which incoporates all the changes 
from 5.4.29 to
5.4.33, does anyone want this patch or has work in vpopmail-5.5.0 stalled ?

Drew, I'd be happy to take a look at this.  What changes did you add?


I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff to 
5.5.0, some of it had
already been done to 5.5.0 and alot of it centered around the snprintf tidy 
up's and the
string_list implementation. The attached patch does not include any of the 
changes I recently
sent to the mailing list, just the changes from 5.4.[29->33].


This patch was generated from the 5.5.0 .tar.bz2, I had a look at SVN 
trunk and from what I could see, it was 5.4.34.


!DSPAM:55fae1c241551761131543!

Re: [vchkpw] [SPAM] valias remove alias

[Matt Brookings]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Was this patch generated with the SVN trunk (5.5.0)?

On 09/17/2015 09:57 AM, Drew Wells wrote:
> On 09/17/2015 03:37 PM, Matt Brookings wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>> 
>> On 09/17/2015 06:23 AM, Drew Wells wrote:
>>> I have created a patch for vpopmail-5.5.0 which incoporates all the changes 
>>> from 5.4.29 to 
>>> 5.4.33, does anyone want this patch or has work in vpopmail-5.5.0 stalled ?
>> Drew, I'd be happy to take a look at this.  What changes did you add?
>> 
> I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff to 
> 5.5.0, some of it had 
> already been done to 5.5.0 and alot of it centered around the snprintf tidy 
> up's and the
> string_list implementation. The attached patch does not include any of the 
> changes I recently
> sent to the mailing list, just the changes from 5.4.[29->33].

- -- 
/*
Matt BrookingsGnuPG Key 62817373
Software developer Systems technician
Inter7 Internet Technologies, Inc. (815)776-9465
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJV+tZ9AAoJEOjQVexigXNzbnYH/2CBtOVqqKBntlGUYQNMzf46
PEyxaODsZjaBmyJKBSL7lU30UzEanbWTbo1XSCj7lx+YRB7v9e90SMDVSbYXbaDh
I2WGhqD+dHVOBbi7b+WtLPAeixPnFOS5EMcWggL+OK9xbF55WsFDQhz7b3wNJGmR
4klK0mEG6a22l2cScAjH7afXzRJpy/Vz6RpBvW+1wGz8R0nRPw6VDpiiiPbqLSpr
S4uDboSTdo2Ah6dFXQDns2Au/JYYB+Ip33f+rYaTyNjL4dUq9Emg/hZNFyy11KgU
0ldCRPX+h1EKtNoh65FAxRWF8tlCYufjw1M9E30neO48dwDVV5AyDRALKxdOjvA=
=6IBz
-END PGP SIGNATURE-

Re: [vchkpw] [SPAM] valias remove alias

[Drew Wells]

On 09/17/2015 03:37 PM, Matt Brookings wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/17/2015 06:23 AM, Drew Wells wrote:

I have created a patch for vpopmail-5.5.0 which incoporates all the changes 
from 5.4.29 to
5.4.33, does anyone want this patch or has work in vpopmail-5.5.0 stalled ?

Drew, I'd be happy to take a look at this.  What changes did you add?

I basically did a diff from 5.4.29 to 5.4.33 and implemented that diff 
to 5.5.0, some of it had already been done to 5.5.0 and alot of it 
centered around the snprintf tidy up's and the string_list implementation.
The attached patch does not include any of the changes I recently sent 
to the mailing list, just the changes from 5.4.[29->33].



!DSPAM:55fad4d841551123915585!
diff -uPr vpopmail-5.5.0.orig/backends/mysql/vmysql.c 
vpopmail-5.5.0/backends/mysql/vmysql.c
--- vpopmail-5.5.0.orig/backends/mysql/vmysql.c 2010-11-05 18:37:23.0 
+
+++ vpopmail-5.5.0/backends/mysql/vmysql.c  2015-09-17 11:41:02.724095923 
+0100
@@ -1785,10 +1785,10 @@
 limits->maxforwards = atoi(row[2]);
 limits->maxautoresponders = atoi(row[3]);
 limits->maxmailinglists = atoi(row[4]);
-limits->diskquota = atoi(row[5]);
-limits->maxmsgcount = atoi(row[6]);
-limits->defaultquota = atoi(row[7]);
-limits->defaultmaxmsgcount = atoi(row[8]);
+limits->diskquota = strtoll(row[5], NULL, 10);
+limits->maxmsgcount = strtoll(row[6], NULL, 10);
+limits->defaultquota = strtoll(row[7], NULL, 10);
+limits->defaultmaxmsgcount = strtoll(row[8], NULL, 10);
 limits->disable_pop = atoi(row[9]);
 limits->disable_imap = atoi(row[10]);
 limits->disable_dialup = atoi(row[11]);
@@ -1808,8 +1808,8 @@
 limits->perm_maillist_users = perm & VLIMIT_DISABLE_ALL;
 perm >>= VLIMIT_DISABLE_BITS;
 limits->perm_maillist_moderators = perm & VLIMIT_DISABLE_ALL;
-limits->perm_quota = atoi(row[23]);
-limits->perm_defaultquota = atoi(row[24]);
+limits->perm_quota = strtoll(row[23], NULL, 10);
+limits->perm_defaultquota = strtoll(row[24], NULL, 10);
 }
 mysql_free_result(res_read);
 
@@ -1830,7 +1830,7 @@
 "diskquota = %d, maxmsgcount = %d, defaultquota = %d, 
defaultmaxmsgcount = %d, "
 "disable_pop = %d, disable_imap = %d, disable_dialup = %d, "
 "disable_passwordchanging = %d, disable_webmail = %d, disable_relay = 
%d, "
-"disable_smtp = %d, disable_spamassassin = %d, delete_spam = %d, 
perm_account = %d, "
+"disable_smtp = %d, disable_spamassassin = %d, delete_spam = %d, 
disable_maildrop = %d, perm_account = %d, "
 "perm_alias = %d, perm_forward = %d, perm_autoresponder = %d, 
perm_maillist = %d, "
 "perm_quota = %d, perm_defaultquota = %d "
 "ON DUPLICATE KEY UPDATE "
@@ -1847,7 +1847,7 @@
 limits->diskquota, limits->maxmsgcount, limits->defaultquota, 
limits->defaultmaxmsgcount,
 limits->disable_pop, limits->disable_imap, limits->disable_dialup,
 limits->disable_passwordchanging, limits->disable_webmail, 
limits->disable_relay,
-limits->disable_smtp, limits->disable_spamassassin, 
limits->delete_spam, limits->perm_account,
+limits->disable_smtp, limits->disable_spamassassin, 
limits->delete_spam, limits->disable_maildrop, limits->perm_account,
 limits->perm_alias, limits->perm_forward, limits->perm_autoresponder,
 (limits->perm_maillist |
 (limits->perm_maillist_users << VLIMIT_DISABLE_BITS) |
diff -uPr vpopmail-5.5.0.orig/backends/mysql/vmysql.h.in 
vpopmail-5.5.0/backends/mysql/vmysql.h.in
--- vpopmail-5.5.0.orig/backends/mysql/vmysql.h.in  2010-11-05 
18:37:23.0 +
+++ vpopmail-5.5.0/backends/mysql/vmysql.h.in   2015-09-17 11:41:02.725095861 
+0100
@@ -268,10 +268,10 @@
   maxforwards  INT(10) NOT NULL DEFAULT -1, \
   maxautorespondersINT(10) NOT NULL DEFAULT -1, \
   maxmailinglists  INT(10) NOT NULL DEFAULT -1, \
-  diskquotaINT(12) NOT NULL DEFAULT 0, \
-  maxmsgcount  INT(12) NOT NULL DEFAULT 0, \
-  defaultquota INT(12) NOT NULL DEFAULT 0, \
-  defaultmaxmsgcount   INT(12) NOT NULL DEFAULT 0, \
+  diskquotaBIGINT UNSIGNED NOT NULL DEFAULT 0, \
+  maxmsgcount  BIGINT UNSIGNED NOT NULL DEFAULT 0, \
+  defaultquota BIGINT UNSIGNED NOT NULL DEFAULT 0, \
+  defaultmaxmsgcount   BIGINT UNSIGNED NOT NULL DEFAULT 0, \
   disable_pop  TINYINT(1) NOT NULL DEFAULT 0, \
   disable_imap TINYINT(1) NOT NULL DEFAULT 0, \
   disable_dialup   TINYINT(1) NOT NULL DEFAULT 0, \
diff -uPr vpopmail-5.5.0.orig/backfill.c vpopmail-5.5.0/backfill.c
--- vpopmail-5.5.0.orig/backfill.c  2010-11-05 18:37:22.0 +
+++ vpopmail-5.5.0/backfill.c   2015-09-17 11:41:02.7250

Re: [vchkpw] [SPAM] valias remove alias

[Matt Brookings]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/17/2015 06:23 AM, Drew Wells wrote:
> I have created a patch for vpopmail-5.5.0 which incoporates all the changes 
> from 5.4.29 to
> 5.4.33, does anyone want this patch or has work in vpopmail-5.5.0 stalled ?

Drew, I'd be happy to take a look at this.  What changes did you add?
- -- 
/*
Matt BrookingsGnuPG Key 62817373
Software developer Systems technician
Inter7 Internet Technologies, Inc. (815)776-9465
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJV+tA3AAoJEOjQVexigXNzpoAIAJHChv9aNWE5TGdYIRVExQxs
cKyi14LUwIMupA3HX4GNTTBy9bMF6HVgWxMqRA3WOq3KzRGhwi2fT9J1lQseaC5X
U4Fd5qQ8eeiYcl8yakT+ZPjwDRSLbkNX98akynm1QDT92/YNgaZ55F6aE2uH2IVg
8rMDw96OohaJJHGCt9XZouTEuQZgTZKunWoKYMgpqvH5NdCvDxP2SgeOu7uRLPoM
e5w1Gqc2p9xP0VxgmqMPEl5Yp8uTQXfUjQrbw2Soe55OnnJXtxoJ3gCrPxdwAgLj
pHxZXJjon+681cYOJr+xX6grUuPuZIlV1y3WRzvgo8m1sD/VFq8WN/roWNYV0EA=
=LSon
-END PGP SIGNATURE-

Re: [vchkpw] [SPAM] Password strength bug

[Tonix - Antonio Nati]

Il 17/09/2015 13:18, Drew Wells ha scritto:

On 09/15/2015 03:27 PM, Tonix - Antonio Nati wrote:

Il 15/09/2015 15:03, Drew Wells ha scritto:

On 09/15/2015 11:00 AM, Tonix - Antonio Nati wrote:

Il 15/09/2015 11:03, Drew Wells ha scritto:
In vpopmail-5.5.0 there seems to be a bug in vpopmail.c where the 
password strength is checked even if a password isn't used (such 
as when -e is used to add the encrypted password).  Patch attached.







I do not understand the problem.

Of course password strenght is checked every time, and if it founds 
a null/empty password it gives error back if password must have a 
minimum lenght.


Your patch instead permit to have null password even if strenght 
policy would not allow it.


Regards,

Tonino
The problem is is that vadduser.c can call vadduser() (in 
vpopmail.c) without a password.  It does this in the situation where 
vadduser.c has had the options "-e" or "-n" passed to it, so if this 
is the case the password can't be checked againts the password 
strength rules.  The underlying function vadduser() needs to be able 
to add a user with no password.




I realize additional controls are done before calling vadduser(); but 
I personally would prefer an explicit parameter added to vadduser for 
avoiding password check (it may be a further parameter having default 
= "check").

It would make developers more protected against unwanted security bugs.

Regards,

Tonino

I agree that it would be better to explicitly indicate to vadduser() 
that no password is wanted.  I even looked quicky at setting the 
password to NULL to indicate no password, but both this and an 
explicit parameter would need changes to all the backends, so have 
left it as is for now.


It could be done in two ways:

 * considering most od c compilers are c++ compilers, and that means we
   can add an implicit parameter (, nocheck_pwd = 0)
 * duplicate the function for this usage, and call the duplicated
   function from avdduser when needed.

Regards,

Tonino


 



--

Inter@zioniInterazioni di Antonio Nati
   http://www.interazioni.it  to...@interazioni.it




!DSPAM:55faa3e241551872413518!

Re: [vchkpw] [SPAM] valias remove alias

[Drew Wells]

On 09/15/2015 02:26 PM, Alessio Cecchi wrote:

Il 15/09/2015 15:10, Drew Wells ha scritto:

On 09/15/2015 11:06 AM, Alessio Cecchi wrote:


Il 15/09/2015 11:22, Drew Wells ha scritto:

In vpopmail-5.5.0 (and I think all 5.4.x)


Hi Drew,

I suggest to install (and debug) vpopmail-5.4.33 that is more stable,
reliable (and recent) than 5.5.0. Whan I try to use 5.5.0 I found many
bug and problems tha new features.

Why you need vpopmail-5.5.0 ?

I have been using vpopmail-5.4.x (currently vpopmail-5.4.33) for years
and have always added this patch, so in an attempt get 5.5.0 towards
stable I thought I'd send this patch.  This patch is also applicable to
the 5.4.x branch.
The reason I want to use 5.5.0 is the shared library support which means
I don't need to recompile netqmail and dovecot (and others) each time I
make changes to vpopmail.
I've not found that many bugs with vpopmail-5.5.0 to be honest.


I remember some problems with vpopmaild (that I'm using for password 
change via webmail), with large quota size, and a missing flag in 
MySQL limits for disable_maildrop.


Vpomail-5.5.0 was started from 5.4.28 so change from 5.4.29 to 5.4.33 
are missing (please correct me if I'm wrong).


If you have others useful patch for vpopmail-5.4 you are welcome :-)

Thanks

I have created a patch for vpopmail-5.5.0 which incoporates all the 
changes from 5.4.29 to 5.4.33, does anyone want this patch or has work 
in vpopmail-5.5.0 stalled ?


!DSPAM:55faa2a041552051216344!

Re: [vchkpw] [SPAM] Password strength bug

[Drew Wells]

On 09/15/2015 03:27 PM, Tonix - Antonio Nati wrote:

Il 15/09/2015 15:03, Drew Wells ha scritto:

On 09/15/2015 11:00 AM, Tonix - Antonio Nati wrote:

Il 15/09/2015 11:03, Drew Wells ha scritto:
In vpopmail-5.5.0 there seems to be a bug in vpopmail.c where the 
password strength is checked even if a password isn't used (such as 
when -e is used to add the encrypted password).  Patch attached.







I do not understand the problem.

Of course password strenght is checked every time, and if it founds 
a null/empty password it gives error back if password must have a 
minimum lenght.


Your patch instead permit to have null password even if strenght 
policy would not allow it.


Regards,

Tonino
The problem is is that vadduser.c can call vadduser() (in vpopmail.c) 
without a password.  It does this in the situation where vadduser.c 
has had the options "-e" or "-n" passed to it, so if this is the case 
the password can't be checked againts the password strength rules.  
The underlying function vadduser() needs to be able to add a user 
with no password.




I realize additional controls are done before calling vadduser(); but 
I personally would prefer an explicit parameter added to vadduser for 
avoiding password check (it may be a further parameter having default 
= "check").

It would make developers more protected against unwanted security bugs.

Regards,

Tonino

I agree that it would be better to explicitly indicate to vadduser() 
that no password is wanted.  I even looked quicky at setting the 
password to NULL to indicate no password, but both this and an explicit 
parameter would need changes to all the backends, so have left it as is 
for now.



!DSPAM:55faa1a741551399290072!

Re: [vchkpw] [SPAM] Password strength bug

[Tonix - Antonio Nati]

Il 15/09/2015 15:03, Drew Wells ha scritto:

On 09/15/2015 11:00 AM, Tonix - Antonio Nati wrote:

Il 15/09/2015 11:03, Drew Wells ha scritto:
In vpopmail-5.5.0 there seems to be a bug in vpopmail.c where the 
password strength is checked even if a password isn't used (such as 
when -e is used to add the encrypted password).  Patch attached.







I do not understand the problem.

Of course password strenght is checked every time, and if it founds a 
null/empty password it gives error back if password must have a 
minimum lenght.


Your patch instead permit to have null password even if strenght 
policy would not allow it.


Regards,

Tonino
The problem is is that vadduser.c can call vadduser() (in vpopmail.c) 
without a password.  It does this in the situation where vadduser.c 
has had the options "-e" or "-n" passed to it, so if this is the case 
the password can't be checked againts the password strength rules.  
The underlying function vadduser() needs to be able to add a user with 
no password.




I realize additional controls are done before calling vadduser(); but I 
personally would prefer an explicit parameter added to vadduser for 
avoiding password check (it may be a further parameter having default = 
"check").

It would make developers more protected against unwanted security bugs.

Regards,

Tonino


 



--

Inter@zioniInterazioni di Antonio Nati
   http://www.interazioni.it  to...@interazioni.it




!DSPAM:55f82abc41552085678254!

Re: [vchkpw] [SPAM] valias remove alias

[Drew Wells]

On 09/15/2015 02:26 PM, Alessio Cecchi wrote:

Il 15/09/2015 15:10, Drew Wells ha scritto:

On 09/15/2015 11:06 AM, Alessio Cecchi wrote:


Il 15/09/2015 11:22, Drew Wells ha scritto:

In vpopmail-5.5.0 (and I think all 5.4.x)


Hi Drew,

I suggest to install (and debug) vpopmail-5.4.33 that is more stable,
reliable (and recent) than 5.5.0. Whan I try to use 5.5.0 I found many
bug and problems tha new features.

Why you need vpopmail-5.5.0 ?

I have been using vpopmail-5.4.x (currently vpopmail-5.4.33) for years
and have always added this patch, so in an attempt get 5.5.0 towards
stable I thought I'd send this patch.  This patch is also applicable to
the 5.4.x branch.
The reason I want to use 5.5.0 is the shared library support which means
I don't need to recompile netqmail and dovecot (and others) each time I
make changes to vpopmail.
I've not found that many bugs with vpopmail-5.5.0 to be honest.


I remember some problems with vpopmaild (that I'm using for password 
change via webmail), with large quota size, and a missing flag in 
MySQL limits for disable_maildrop.


Vpomail-5.5.0 was started from 5.4.28 so change from 5.4.29 to 5.4.33 
are missing (please correct me if I'm wrong).


If you have others useful patch for vpopmail-5.4 you are welcome :-)

Thanks

If that is the case (the missing 5.4.29 -> 5.4.33 changes) I'll have a 
look and get those changes into 5.5.0, I'd really like to use the shared 
library support.


!DSPAM:55f81f7741555484815027!

Re: [vchkpw] [SPAM] valias remove alias

[Alessio Cecchi]

Il 15/09/2015 15:10, Drew Wells ha scritto:

On 09/15/2015 11:06 AM, Alessio Cecchi wrote:


Il 15/09/2015 11:22, Drew Wells ha scritto:

In vpopmail-5.5.0 (and I think all 5.4.x)


Hi Drew,

I suggest to install (and debug) vpopmail-5.4.33 that is more stable,
reliable (and recent) than 5.5.0. Whan I try to use 5.5.0 I found many
bug and problems tha new features.

Why you need vpopmail-5.5.0 ?

I have been using vpopmail-5.4.x (currently vpopmail-5.4.33) for years
and have always added this patch, so in an attempt get 5.5.0 towards
stable I thought I'd send this patch.  This patch is also applicable to
the 5.4.x branch.
The reason I want to use 5.5.0 is the shared library support which means
I don't need to recompile netqmail and dovecot (and others) each time I
make changes to vpopmail.
I've not found that many bugs with vpopmail-5.5.0 to be honest.


I remember some problems with vpopmaild (that I'm using for password 
change via webmail), with large quota size, and a missing flag in MySQL 
limits for disable_maildrop.


Vpomail-5.5.0 was started from 5.4.28 so change from 5.4.29 to 5.4.33 
are missing (please correct me if I'm wrong).


If you have others useful patch for vpopmail-5.4 you are welcome :-)

Thanks

--
Alessio Cecchi
https://www.linkedin.com/in/alessice

!DSPAM:55f81c8341552100219033!

Re: [vchkpw] [SPAM] valias remove alias

[Drew Wells]

On 09/15/2015 11:06 AM, Alessio Cecchi wrote:


Il 15/09/2015 11:22, Drew Wells ha scritto:

In vpopmail-5.5.0 (and I think all 5.4.x)


Hi Drew,

I suggest to install (and debug) vpopmail-5.4.33 that is more stable, 
reliable (and recent) than 5.5.0. Whan I try to use 5.5.0 I found many 
bug and problems tha new features.


Why you need vpopmail-5.5.0 ?
I have been using vpopmail-5.4.x (currently vpopmail-5.4.33) for years 
and have always added this patch, so in an attempt get 5.5.0 towards 
stable I thought I'd send this patch.  This patch is also applicable to 
the 5.4.x branch.
The reason I want to use 5.5.0 is the shared library support which means 
I don't need to recompile netqmail and dovecot (and others) each time I 
make changes to vpopmail.

I've not found that many bugs with vpopmail-5.5.0 to be honest.

!DSPAM:55f818ba41551449159681!

Re: [vchkpw] [SPAM] Password strength bug

[Drew Wells]

On 09/15/2015 11:00 AM, Tonix - Antonio Nati wrote:

Il 15/09/2015 11:03, Drew Wells ha scritto:
In vpopmail-5.5.0 there seems to be a bug in vpopmail.c where the 
password strength is checked even if a password isn't used (such as 
when -e is used to add the encrypted password).  Patch attached.







I do not understand the problem.

Of course password strenght is checked every time, and if it founds a 
null/empty password it gives error back if password must have a 
minimum lenght.


Your patch instead permit to have null password even if strenght 
policy would not allow it.


Regards,

Tonino
The problem is is that vadduser.c can call vadduser() (in vpopmail.c) 
without a password.  It does this in the situation where vadduser.c has 
had the options "-e" or "-n" passed to it, so if this is the case the 
password can't be checked againts the password strength rules.  The 
underlying function vadduser() needs to be able to add a user with no 
password.




!DSPAM:55f8173d41558919512318!

Re: [vchkpw] [SPAM] Segmentation fault in vadduser

[Drew Wells]

Yes, I know - that's I did some work on 5.5.0 and fixed the segmentation 
fault to try and get it closer to stable.


On 09/15/2015 10:39 AM, Thibault Richard wrote:

This is probably why the 5.4.0 is still not considered as stable (the latest 
stable version is still 5.4.33)

-Original Message-
From: Drew Wells [mailto:drew-vpopm...@elysium.ltd.uk]
Sent: Tuesday 15 September 2015 11:19
To: vchkpw@inter7.com
Subject: [vchkpw] [SPAM] Segmentation fault in vadduser

In vpopmail-5.5.0 there seems to be a bug in vadduser that causes a 
segmentation fault when a password does not pass the password_strength rules.  
Patch attached.










!DSPAM:55f8140941551047816349!

Re: [vchkpw] [SPAM] valias remove alias

[Alessio Cecchi]

Il 15/09/2015 11:22, Drew Wells ha scritto:

In vpopmail-5.5.0 (and I think all 5.4.x)


Hi Drew,

I suggest to install (and debug) vpopmail-5.4.33 that is more stable, 
reliable (and recent) than 5.5.0. Whan I try to use 5.5.0 I found many 
bug and problems tha new features.


Why you need vpopmail-5.5.0 ?
--
Alessio Cecchi
https://www.linkedin.com/in/alessice

!DSPAM:55f7edb641552122517293!

Re: [vchkpw] [SPAM] Password strength bug

[Tonix - Antonio Nati]

Il 15/09/2015 11:03, Drew Wells ha scritto:
In vpopmail-5.5.0 there seems to be a bug in vpopmail.c where the 
password strength is checked even if a password isn't used (such as 
when -e is used to add the encrypted password).  Patch attached.







I do not understand the problem.

Of course password strenght is checked every time, and if it founds a 
null/empty password it gives error back if password must have a minimum 
lenght.


Your patch instead permit to have null password even if strenght policy 
would not allow it.


Regards,

Tonino

--

Inter@zioniInterazioni di Antonio Nati
   http://www.interazioni.it  to...@interazioni.it




!DSPAM:55f7ec4641551939410840!

RE: [vchkpw] [SPAM] Segmentation fault in vadduser

[Thibault Richard]

This is probably why the 5.4.0 is still not considered as stable (the latest 
stable version is still 5.4.33)

-Original Message-
From: Drew Wells [mailto:drew-vpopm...@elysium.ltd.uk] 
Sent: Tuesday 15 September 2015 11:19
To: vchkpw@inter7.com
Subject: [vchkpw] [SPAM] Segmentation fault in vadduser

In vpopmail-5.5.0 there seems to be a bug in vadduser that causes a 
segmentation fault when a password does not pass the password_strength rules.  
Patch attached.





!DSPAM:55f7e75c41551355020703!

[vchkpw] Auto-Re: [vchkpw] [SPAM] vdominfo quota bug

[zhaopin]

尊敬的同学：您好！

您的求职简历已经收到，我们会尽快进行阅评，之后再决定是否与您面谈！


  中信泰富（中国）投资有限公司
 人力资源部

!DSPAM:55f7e55641551049011877!

[vchkpw] [SPAM] vdominfo quota bug

[Drew Wells]

In vpopmail-5.5.0 there is a bug in vdominfo that means option 'q' does 
not work, there is a missing break after the 'q' case. Additionally 
vdominfo's output differs from vuserinfo's output in that in vuserinfo 
the quota and the quota usage are treated seperatly, I have changed 
vdominfo to fix the bug and make it similar to vuserinfo.  Patch attached.



!DSPAM:55f7e54541556238488843!
diff -uPr vpopmail-5.5.0.orig/vdominfo.c vpopmail-5.5.0/vdominfo.c
--- vpopmail-5.5.0.orig/vdominfo.c  2010-11-05 18:37:23.0 +
+++ vpopmail-5.5.0/vdominfo.c   2015-09-07 10:51:22.215095738 +0100
@@ -43,6 +43,7 @@
 int DisplayTotalUsers;
 int DisplayRealDomain;
 int DisplayQuota;
+int DisplayQuotaUsage;
 
 void usage();
 void get_options(int argc, char **argv);
@@ -60,7 +61,7 @@
 
ret = vauth_load_module(NULL);
if (!ret)
- vexiterror(stderr, "could not load authentication module");
+  vexiterror(stderr, "could not load authentication module");
 
 if( vauth_open( 0 )) {
 vexiterror( stderr, "Initial open." );
@@ -89,7 +90,8 @@
 printf(" -d (display domain directory)\n");
 printf(" -t (display total users)\n");
 printf(" -r (display real domain)\n");
-   printf(" -q (display quota usage)\n");
+printf(" -q (display quota field)\n");
+printf(" -Q (display quota usage)\n");
 }
 
 void get_options(int argc, char **argv)
@@ -104,13 +106,14 @@
 DisplayDir = 0;
 DisplayTotalUsers = 0;
 DisplayAll = 1;
-   DisplayRealDomain = 0;
-   DisplayQuota = 0;
+DisplayRealDomain = 0;
+DisplayQuota = 0;
+DisplayQuotaUsage = 0;
 
 memset(Domain, 0, sizeof(Domain));
 
 errflag = 0;
-while( !errflag && (c=getopt(argc,argv,"vanugdtrq")) != -1 ) {
+while( !errflag && (c=getopt(argc,argv,"vanugdtrqQ")) != -1 ) {
 switch(c) {
 case 'v':
 printf("version: %s\n", VERSION);
@@ -140,11 +143,16 @@
 break;
 case 'r':
 DisplayRealDomain = 1;
-   DisplayAll = 0;
+DisplayAll = 0;
+break;
+case 'q':
+DisplayQuota = 1;
+DisplayAll = 0;
+break;
+case 'Q':
+DisplayQuotaUsage = 1;
+DisplayAll = 0;
 break;
-   case 'q':
-   DisplayQuota = 1;
-   DisplayAll = 0;
 default:
 errflag = 1;
 break;
@@ -157,18 +165,47 @@
 }
 
 if ( optind < argc ) {
-   snprintf(Domain, sizeof(Domain), "%s", argv[optind]); 
+snprintf(Domain, sizeof(Domain), "%s", argv[optind]); 
 ++optind;
 }
 }
 
-void display_domain(char *domain, char *dir, uid_t uid, gid_t gid, char 
*realdomain)
+void display_quota(char *realdomain)
 {
int ret = 0;
struct vlimits vl;
+
+ret = vget_limits(realdomain, &vl);
+if (!ret)
+printf("S=%llu,C=%llu\n", 
(storage_t)(((storage_t)vl.diskquota)*((storage_t)100)), 
(storage_t)(vl.maxmsgcount));
+else
+printf("NOQUOTA\n");
+}
+
+void display_quota_usage(char *realdomain)
+{
+   int ret = 0, len = 0;
+   struct vlimits vl;
storage_t bytes = 0, count = 0;
char b[256] = { 0 };
 
+ret = vget_limits(realdomain, &vl);
+len = strlen(realdomain);
+if (len <= (sizeof(b) - 2)) {
+memcpy((b + 1), realdomain, len);
+*b = '@';
+*(b + len + 1) = '\0';
+
+quota_get_usage(b, &bytes, &count);
+}
+
+printf("%d%% (%llu byte(s) in %llu file(s))\n",
+quota_percent(bytes, count, (storage_t)((storage_t)vl.diskquota * 
((storage_t)100)), vl.maxmsgcount),
+bytes, count);
+}
+
+void display_domain(char *domain, char *dir, uid_t uid, gid_t gid, char 
*realdomain)
+{
 if ( DisplayAll ) {
 if(strcmp(domain, realdomain)==0)
 printf("domain: %s\n", domain);
@@ -180,27 +217,10 @@
 open_big_dir(realdomain, uid, gid);
 printf("users:  %lu\n",  vdir.cur_users);
 close_big_dir(realdomain,uid,gid);
-
-   ret = vget_limits(realdomain, &vl);
-   if (!ret)
-  printf("quota:  S=%llu,C=%llu\n", 
(storage_t)(((storage_t)vl.diskquota)*((storage_t)100)), 
(storage_t)(vl.maxmsgcount));
-
-else
-   printf("quota:  NOQUOTA\n");
-
-ret = strlen(realdomain);
-if (ret <= (sizeof(b) - 2)) {
-   memcpy((b + 1), realdomain, ret);
-   *b = '@';
-   *(b + ret + 1) = '\0';
-
-   quota_get_usage(b, &bytes, &count);
-}
-
-printf("usage:  %d%% (%llu byte(s) in %llu file(s))\n",
-  quota_percent(bytes, count, 
(storage_t)((storage_t)vl.diskquota 

[vchkpw] [SPAM] valias remove alias

[Drew Wells]

In vpopmail-5.5.0 (and I think all 5.4.x) there seems to be no way of 
removing an alias_line using valias, I've added this functionality.  
Patch attached.



!DSPAM:55f7e35241555071313485!
diff -uPr vpopmail-5.5.0.orig/valias.c vpopmail-5.5.0/valias.c
--- vpopmail-5.5.0.orig/valias.c2010-11-05 18:37:22.0 +
+++ vpopmail-5.5.0/valias.c 2015-09-04 12:39:34.999094668 +0100
@@ -38,8 +38,9 @@
 
 #define VALIAS_SELECT 0
 #define VALIAS_INSERT 1
-#define VALIAS_DELETE 2
-#define VALIAS_NAMES  3
+#define VALIAS_REMOVE 2
+#define VALIAS_DELETE 3
+#define VALIAS_NAMES  4
 
 int AliasAction;
 int AliasExists;
@@ -119,6 +120,23 @@
}
break;
 
+   case VALIAS_REMOVE:
+   /* check to see if it already exists */
+   AliasExists = 0;
+   tmpalias = valias_select( Alias, Domain );
+   while (tmpalias != NULL ) {
+   if (strcmp (tmpalias, AliasLine) == 0) AliasExists = 1;
+   tmpalias = valias_select_next();
+   }
+   if (AliasExists) {
+   valias_remove( Alias, Domain, AliasLine );
+   } else {
+   fprintf (stderr, "Error: alias %s -> %s does not 
exist.\n",
+   Email, AliasLine);
+   vexit(-1);
+   }
+   break;
+
case VALIAS_DELETE:
valias_delete( Alias, Domain );
break;
@@ -139,6 +157,7 @@
printf(" -s ( show aliases, can use just domain )\n");
printf(" -d ( delete alias )\n");
printf(" -i alias_line (insert alias line)\n");
+   printf(" -r alias_line (remove alias line)\n");
printf("\n");
printf("Example: valias -i f...@inter7.com b...@inter7.com\n");
printf(" (adds alias from b...@inter7.com to 
f...@inter7.com\n");
@@ -157,7 +176,7 @@
memset(AliasLine, 0, sizeof(AliasLine));
AliasAction = VALIAS_SELECT;
 
-   while( (c=getopt(argc,argv,"vnsdi:")) != -1 ) {
+   while( (c=getopt(argc,argv,"vnsr:di:")) != -1 ) {
switch(c) {
case 'v':
printf("version: %s\n", VERSION);
@@ -168,6 +187,10 @@
case 's':
AliasAction = VALIAS_SELECT;
break;
+   case 'r':
+   AliasAction = VALIAS_REMOVE;
+   snprintf(AliasLine, sizeof(AliasLine), "%s", optarg);
+   break;
case 'd':
AliasAction = VALIAS_DELETE;
break;

[vchkpw] Auto-Re: [vchkpw] [SPAM] valias remove alias

[zhaopin]

尊敬的同学：您好！

您的求职简历已经收到，我们会尽快进行阅评，之后再决定是否与您面谈！


  中信泰富（中国）投资有限公司
 人力资源部

!DSPAM:55f7e35941551360728760!

[vchkpw] [SPAM] Segmentation fault in vadduser

[Drew Wells]

In vpopmail-5.5.0 there seems to be a bug in vadduser that causes a 
segmentation fault when a password does not pass the password_strength 
rules.  Patch attached.



!DSPAM:55f7e27341551399513616!
diff -uPr vpopmail-5.5.0.orig/vadduser.c vpopmail-5.5.0/vadduser.c
--- vpopmail-5.5.0.orig/vadduser.c  2010-11-05 18:37:22.0 +
+++ vpopmail-5.5.0/vadduser.c   2015-09-14 12:49:23.957094657 +0100
@@ -28,16 +28,19 @@
 #include 
 #include "config.h"
 #include "vpopmail.h"
-#include "vauth.h"
 #include "vauthmodule.h"
+#include "vauth.h"
+#include "pwstr.h"
 
 char Email[MAX_BUFF];
+char User[MAX_BUFF];
+char Domain[MAX_BUFF];
 char Passwd[MAX_BUFF];
 char Quota[MAX_BUFF];
 char Gecos[MAX_BUFF];
 char Crypted[MAX_BUFF];
 
-int apop;
+int apop = USE_POP;
 int RandomPw;
 int NoPassword = 0;
 
@@ -47,8 +50,6 @@
 int main(int argc,char **argv)
 {
  int i;
- char User[MAX_BUFF];
- char Domain[MAX_BUFF];
  struct vqpasswd *vpw;
 
 i = vauth_load_module(NULL);

[vchkpw] Auto-Re: [vchkpw] [SPAM] Segmentation fault in vadduser

[zhaopin]

尊敬的同学：您好！

您的求职简历已经收到，我们会尽快进行阅评，之后再决定是否与您面谈！


  中信泰富（中国）投资有限公司
 人力资源部

!DSPAM:55f7e27941558004510909!

[vchkpw] [SPAM] Onchange script

[Drew Wells]

I use the onchange functionality in vpopmail-5.5.0 but find it awkward 
that the script is only called once for "add_domain", instead of calling 
the script with "add_domain", "add_user" then "mod_user" so have written 
a patch to allow this.  One side affect is that the order of calls in 
vadduser() has changed.  Patch attached.



!DSPAM:55f7e1c341551875619181!
diff -uPr vpopmail-5.5.0.orig/backends/cdb/vcdb.c 
vpopmail-5.5.0/backends/cdb/vcdb.c
--- vpopmail-5.5.0.orig/backends/cdb/vcdb.c 2010-11-05 18:37:23.0 
+
+++ vpopmail-5.5.0/backends/cdb/vcdb.c  2015-09-04 12:42:00.306095822 +0100
@@ -664,12 +664,16 @@
 #endif
 
 #ifdef ONCHANGE_SCRIPT
+#ifdef ONCHANGE_SCRIPT_ALLOW
 if( allow_onchange ) {
+#endif
/* tell other programs that data has changed */
snprintf ( onchange_buf, MAX_BUFF, "%s@%s", inpw->pw_name, domain ) ;
call_onchange ( "mod_user" ) ;
+#ifdef ONCHANGE_SCRIPT_ALLOW
}
 #endif
+#endif
 
if (!(strcasecmp(inpw->pw_shell, "NOQUOTA")))
   remove_maildirsize(inpw->pw_dir);
diff -uPr vpopmail-5.5.0.orig/backends/ldap/vldap.c 
vpopmail-5.5.0/backends/ldap/vldap.c
--- vpopmail-5.5.0.orig/backends/ldap/vldap.c   2010-11-05 18:37:24.0 
+
+++ vpopmail-5.5.0/backends/ldap/vldap.c2015-09-04 12:42:00.307095769 
+0100
@@ -972,12 +972,16 @@
 #endif
 
 #ifdef ONCHANGE_SCRIPT
+#ifdef ONCHANGE_SCRIPT_ALLOW
 if( allow_onchange ) {
+#endif
/* tell other programs that data has changed */
snprintf ( onchange_buf, MAX_BUFF, "%s@%s", inpw->pw_name, domain );
call_onchange ( "mod_user" );
+#ifdef ONCHANGE_SCRIPT_ALLOW
}
 #endif
+#endif
 
if (!(strcasecmp(inpw->pw_shell, "NOQUOTA")))
   remove_maildirsize(inpw->pw_dir);
@@ -1733,12 +1737,16 @@
 }
 
 #ifdef ONCHANGE_SCRIPT
+#ifdef ONCHANGE_SCRIPT_ALLOW
 if( allow_onchange ) {
+#endif
/* tell other programs that data has changed */
snprintf ( onchange_buf, MAX_BUFF, "%s@%s - %s", alias, domain, 
alias_line );
call_onchange ( "alias_insert" );
+#ifdef ONCHANGE_SCRIPT_ALLOW
}
 #endif
+#endif
 
 return(0);
 }
@@ -1756,12 +1764,16 @@
 if ( (err=ldap_connect()) != 0 ) return(err);
 
 #ifdef ONCHANGE_SCRIPT
+#ifdef ONCHANGE_SCRIPT_ALLOW
 if( allow_onchange ) {
+#endif
/* tell other programs that data has changed */
snprintf ( onchange_buf, MAX_BUFF, "%s@%s - %s", alias, domain, 
alias_line );
call_onchange ( "alias_remove" );
+#ifdef ONCHANGE_SCRIPT_ALLOW
}
 #endif
+#endif
 
memset(ud, 0, sizeof(ud));
snprintf(ud, sizeof(ud), "%s@%s", alias, domain);
@@ -1863,12 +1875,16 @@
 if ( (err=ldap_connect()) != 0 ) return(err);
 
 #ifdef ONCHANGE_SCRIPT
+#ifdef ONCHANGE_SCRIPT_ALLOW
 if( allow_onchange ) {
+#endif
/* tell other programs that data has changed */
snprintf ( onchange_buf, MAX_BUFF, "%s@%s", alias, domain );
call_onchange ( "alias_delete" );
+#ifdef ONCHANGE_SCRIPT_ALLOW
}
 #endif
+#endif
 
memset(ud, 0, sizeof(ud));
snprintf(ud, sizeof(ud), "%s@%s", alias, domain);
diff -uPr vpopmail-5.5.0.orig/backends/mysql/vmysql.c 
vpopmail-5.5.0/backends/mysql/vmysql.c
--- vpopmail-5.5.0.orig/backends/mysql/vmysql.c 2010-11-05 18:37:23.0 
+
+++ vpopmail-5.5.0/backends/mysql/vmysql.c  2015-09-04 12:42:00.308095716 
+0100
@@ -875,12 +875,16 @@
 #endif
 
 #ifdef ONCHANGE_SCRIPT
+#ifdef ONCHANGE_SCRIPT_ALLOW
 if( allow_onchange ) {
+#endif
/* tell other programs that data has changed */
snprintf ( onchange_buf, MAX_BUFF, "%s@%s", inpw->pw_name, domain );
call_onchange ( "mod_user" );
+#ifdef ONCHANGE_SCRIPT_ALLOW
}
 #endif
+#endif
 
if (!(strcasecmp(inpw->pw_shell, "NOQUOTA")))
   remove_maildirsize(inpw->pw_dir);
@@ -1459,12 +1463,16 @@
 }
 
 #ifdef ONCHANGE_SCRIPT
+#ifdef ONCHANGE_SCRIPT_ALLOW
 if( allow_onchange ) {
+#endif
/* tell other programs that data has changed */
snprintf ( onchange_buf, MAX_BUFF, "%s@%s - %s", alias, domain, 
alias_line );
call_onchange ( "valias_insert" );
+#ifdef ONCHANGE_SCRIPT_ALLOW
}
 #endif
+#endif
 
 return(0);
 }
@@ -1478,12 +1486,16 @@
 if ( (err=vauth_open_update()) != 0 ) return(err);
 
 #ifdef ONCHANGE_SCRIPT
+#ifdef ONCHANGE_SCRIPT_ALLOW
 if( allow_onchange ) {
+#endif
/* tell other programs that data has changed */
snprintf ( onchange_buf, MAX_BUFF, "%s@%s - %s", alias, domain, 
alias_line );
call_onchange ( "valias_remove" );
+#ifdef ONCHANGE_SCRIPT_ALLOW
}
 #endif
+#endif
 
 qnprintf( SqlBufUpdate, SQL_BUF_SIZE, 
 "DELETE FROM valias WHERE alias = '%s' \
@@ -1508,12 +1520,16 @@
 if ( (err=vauth_open_update()) != 0 ) return(err);
 
 #ifdef ONCHANGE_SCRIPT
+#ifdef ONCHANGE_SCRIPT_ALLOW
 if( allow_onchange ) {
+#endif
/* tell other programs that data has changed */
snpri

[vchkpw] Auto-Re: [vchkpw] [SPAM] Onchange script

[zhaopin]

尊敬的同学：您好！

您的求职简历已经收到，我们会尽快进行阅评，之后再决定是否与您面谈！


  中信泰富（中国）投资有限公司
 人力资源部

!DSPAM:55f7e1cc41551654711741!

[vchkpw] Auto-Re: [vchkpw] [SPAM] Password strength bug

[zhaopin]

尊敬的同学：您好！

您的求职简历已经收到，我们会尽快进行阅评，之后再决定是否与您面谈！


  中信泰富（中国）投资有限公司
 人力资源部

!DSPAM:55f7e0eb41551555158803!

[vchkpw] [SPAM] Password strength bug

[Drew Wells]

In vpopmail-5.5.0 there seems to be a bug in vpopmail.c where the 
password strength is checked even if a password isn't used (such as when 
-e is used to add the encrypted password).  Patch attached.



!DSPAM:55f7df0641553245911066!
diff -uPr vpopmail-5.5.0.orig/vpopmail.c vpopmail-5.5.0/vpopmail.c
--- vpopmail-5.5.0.orig/vpopmail.c  2015-09-08 11:33:44.818094999 +0100
+++ vpopmail-5.5.0/vpopmail.c   2015-09-08 11:39:56.791096019 +0100
@@ -686,13 +686,11 @@
 
   if ( vauth_getpw( username, domain ) != NULL ) return(VA_USERNAME_EXISTS);
 
-  /*
- Check password strength
-  */
-
-  ret = pw_strength(password);
-  if (ret != 1)
-return ret;
+  /* Check password strength */
+  if ( password[0] != '\0' ) {
+ret = pw_strength(password);
+if (ret != 1) return ret;
+  }
 
   /* record the dir where the vadduser command was run from */
   getcwd(calling_dir, sizeof(calling_dir));

[vchkpw] Auto-Re: [vchkpw] [SPAM] integrated with maildrop

[zhaopin]

尊敬的同学：您好！

您的求职简历已经收到，我们会尽快进行阅评，之后再决定是否与您面谈！


  中信泰富（中国）投资有限公司
 人力资源部

!DSPAM:5595fb4341556565779328!

[vchkpw] [SPAM] integrated with maildrop

[Nethub Online - Ming]

Hi all,

Recently I tested vpopmail-5.4.25 / 5.4.33 with maildrop 2.7 / 2.8.2, I
found that it will add a "From " header to the first line of email, like this:

>From r...@helloworld.com Fri Jun 26 06:27:19 2015

However while I use maildrop 2.6, there is no such problem. I found that
vdelivermail.c of vpopmail contains this line:

sprintf(maildrop_command, "| preline %s", MAILDROP_PROG);

After I removed "preline ", then the maildrop won't add "From " header
anymore. And I checked preline is the qmail binary which is
"/var/qmail/bin/preline".



After discussing with Sam Varshavchik of courier-mta (discussion is here: 
http://thread.gmane.org/gmane.mail.maildrop/5331/focus=5331 , thread id is
5331 - 5339), preline let maildrop think it's delivering to an mbox file, so
that the From_ line is added.

I tried to figure out in source of vpopmail & maildrop but no luck, could
anyone help? Now I don't know the problem should be solved in vpopmail or
maildrop.

Besides, is it safe to remove "preline " like this:


sprintf(maildrop_command, "| %s", MAILDROP_PROG);


!DSPAM:5595f98b41556730565444!

[vchkpw] [SPAM] Include trashed (\Deleted) messages in quota usage

[Teodor Milkov]

Hello,

Currently vpopmail doesn't include trashed messages in quota usage. 
These are messages that were marked as deleted (IMAP flag \Deleted) but 
are still not expunged. These are denoted by the T flag in Maildir: 
http://cr.yp.to/proto/maildir.html


It seems two of the popular mail servers out there have opposing 
behavior: courier doesn't count trashed messages while dovecot does 
count them.


In my setup I have some users, who seem to forgot to expunge (also known 
as "Compact" in thunderbird) their mailboxes and trahsed messages keep 
piling up and filling filesystems. That's why I prefer including trashed 
messages in quota usage and forcing users to take measures this way.


I guess it'd be best to add a configuration option (either ./configure 
compile time or runtime to some config file), but for my specific case I 
patched maildirquota.c with the attached patch.


HTH someone.


Best regards,
Teodor


!DSPAM:54d9e9c441146365629053!
--- maildirquota.h.orig	2015-02-03 14:34:30.0 +0200
+++ maildirquota.h	2015-02-03 14:19:38.0 +0200
@@ -16,6 +16,12 @@
 #define MAILDIRSIZE_OVERLEN 5120
 #define MAILDIRSIZE_OLD_SECS 15*60
 
+/*
+ * Count messages marked as deleted, but still not expunged:
+ * http://cr.yp.to/proto/maildir.html
+ */
+#define QUOTA_COUNT_TRASHED 1
+
 /* I've removed pretty much the whole file execept for
some public functions so as to not conflict with courier.
I"ve made the courier functions static.
--- maildirquota.c.orig	2015-02-03 13:15:37.0 +0200
+++ maildirquota.c	2015-02-03 14:35:47.0 +0200
@@ -990,9 +990,7 @@
 	const char *n=de->d_name;
 
 		if (*n == '.')	continue;
-
-		/* PATCH - do not count msgs marked as deleted */
-
+#if QUOTA_COUNT_TRASHED == 0
 		for ( ; *n; n++)
 		{
 			if (n[0] != ':' || n[1] != '2' ||
@@ -1006,6 +1004,7 @@
 			break;
 		}
 		if (*n == 'T')	continue;
+#endif
 		n=de->d_name;
 
 

RE: [vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

[Stéphane SALETTES]

Thank

I suppose the '-' cause problem but i can t change :(

Cordialement

--
Stephane Salettes


ABAC Informatique
1 Bis Ave Pech Loubat
ZI La Coupe
11100 Narbonne

Tél: 33 (0)4 68 41 73 00
FAX : 33 (0)4 6841 73 02
GSM: 33 (0)6 85 36 67 28

http://www.abac-info.com


-Message d'origine-
De : Eric Shubert [mailto:e...@shubes.net] 
Envoyé : jeudi 24 avril 2014 19:46
À : vchkpw@inter7.com
Objet : [vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection 
problem

That could very well be, Tom.

Stéphane, I believe the odd behavior is due to qmail's 'extension' 
feature, which comes into play with accounts that contain a '-', and the 
portion before the dash matches another account or forward. You could avoid 
this 'collision' (or 'conflict' or 'commonality') by choosing different address 
names, such as 'ssiad_secretariat@' or 'ssiad.secretariat@' or 
'secretariat-ssiad@' (providing there is no account or forward called 
'secretariat@' in this last case).

Email extensions are a handy feature for some users, but admins need to be 
careful when using a '-' in account names.

--
-Eric 'shubes'

On 04/24/2014 09:43 AM, Tom Collins wrote:
> This sounds like a possible bug (or perhaps a configuration issue) in 
> vdelivermail.
>
> With MySQL aliases, vdelivermail handles delivery.  It's finding the ssiad 
> forward first and delivering the message there (since "-secretariat" is an 
> extension to that mailbox).
>
> By deleting the alias record stored in MySQL and replacing it with a 
> dot-qmail file (.qmail-ssiad), you're allowing Qmail to handle its delivery 
> before the message is handed off to vdelivermail.
>
> It's been a long time since I've worked with the vpopmail source code, but I 
> imagine you'll find logic in vdelivermail that has it checking for aliases 
> before mailboxes, and it's iterating through all possible base/extension 
> pairs (foo-bar-baz, then foo-bar, then foo).
>
> -Tom
>
>
> On Apr 24, 2014, at 12:50 AM, Stéphane SALETTES wrote:
>
>> Hi,
>>
>> You don't understand my problem, maybe because my english is bad :(
>>
>> ssiad-secretar...@piemont.fr is a standalone account no foward
>>
>> spa...@piemont.fr is a standalone account no foward
>>
>> and ss...@piemont.fr is just a foward to spa...@piemont.fr
>>
>> but if i send a message to ssiad-secretar...@piemont.fr   nothing in is 
>> mailbox but the message is in the box of spa...@piemont.fr
>>
>> the work arraound that i find is delete the foward on qmailadmin 
>> (mysql) (ss...@piemont.fr ->  spa...@piemont.fr) and create a file
>>
>> .qmail-ssiad
>> &spa...@piemont.fr
>>
>>
>> Hope you understand me this time sorry :)
>>
>> Thank
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Cordialement
>>
>> --
>> Stephane Salettes
>>
>>
>> ABAC Informatique
>> 1 Bis Ave Pech Loubat
>> ZI La Coupe
>> 11100 Narbonne
>>
>> Tél: 33 (0)4 68 41 73 00
>> FAX : 33 (0)4 6841 73 02
>> GSM: 33 (0)6 85 36 67 28
>>
>> http://www.abac-info.com
>>
>>
>> -Message d'origine-
>> De : xaf [mailto:x...@abaxe.net]
>> Envoyé : samedi 19 avril 2014 03:42
>> À : vchkpw@inter7.com
>> Objet : Re: [vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: 
>> [SPAM] Rrdirection problem
>>
>> |--> Eric Shubert, le 18/04/2014 23:38, a dit :
>>>> 3) what you desire to happen
>>>>> When i send a message to  ssiad-secretar...@piemont.fr i want that 
>>>>> the message go to the ssiad-secretar...@piemont.fr mail box and 
>>>>> foward to spa...@piemont.fr
>>>>>
>>>>> And when i send a massage to  ss...@piemont.fr i want a simple 
>>>>> foward to spa...@piemont.fr
>>> I think if you modify the ssiad-secretariat@ account to also forward 
>>> a copy to spasad@, that would achieve your desired behavior. I.e., 
>>> in qmailadmin, under the Routing section, select Forward To, and 
>>> check the Save a Copy checkbox.
>>
>> it's a part of a solution
>> this will create a .qmail file in the user directory but vdelivermail 
>> won't read it because of the extension addresses mechanism
>>
>> Stéphane
>> ssiad-secretariat@ is an alias for user ssiad@ it's quite a strange 
>> conf to give a forward to the user and 

Re: [vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

[Tonix - Antonio Nati]

Stéphane,

try in this way:

 * delete the forward ss...@piemont.fr
 * create one normal account ss...@piemont.fr
 * insert within this account a forward to spa...@piemont.fr

In this way it should work.

Tonino


Il 24/04/2014 19:45, Eric Shubert ha scritto:

That could very well be, Tom.

Stéphane, I believe the odd behavior is due to qmail's 'extension' 
feature, which comes into play with accounts that contain a '-', and 
the portion before the dash matches another account or forward. You 
could avoid this 'collision' (or 'conflict' or 'commonality') by 
choosing different address names, such as 'ssiad_secretariat@' or 
'ssiad.secretariat@' or 'secretariat-ssiad@' (providing there is no 
account or forward called 'secretariat@' in this last case).


Email extensions are a handy feature for some users, but admins need 
to be careful when using a '-' in account names.





--

Inter@zioniInterazioni di Antonio Nati
   http://www.interazioni.it  to...@interazioni.it




!DSPAM:5359502434261244028932!

[vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

[Eric Shubert]

That could very well be, Tom.

Stéphane, I believe the odd behavior is due to qmail's 'extension' 
feature, which comes into play with accounts that contain a '-', and the 
portion before the dash matches another account or forward. You could 
avoid this 'collision' (or 'conflict' or 'commonality') by choosing 
different address names, such as 'ssiad_secretariat@' or 
'ssiad.secretariat@' or 'secretariat-ssiad@' (providing there is no 
account or forward called 'secretariat@' in this last case).


Email extensions are a handy feature for some users, but admins need to 
be careful when using a '-' in account names.


--
-Eric 'shubes'

On 04/24/2014 09:43 AM, Tom Collins wrote:

This sounds like a possible bug (or perhaps a configuration issue) in 
vdelivermail.

With MySQL aliases, vdelivermail handles delivery.  It's finding the ssiad forward first 
and delivering the message there (since "-secretariat" is an extension to that 
mailbox).

By deleting the alias record stored in MySQL and replacing it with a dot-qmail 
file (.qmail-ssiad), you're allowing Qmail to handle its delivery before the 
message is handed off to vdelivermail.

It's been a long time since I've worked with the vpopmail source code, but I 
imagine you'll find logic in vdelivermail that has it checking for aliases 
before mailboxes, and it's iterating through all possible base/extension pairs 
(foo-bar-baz, then foo-bar, then foo).

-Tom


On Apr 24, 2014, at 12:50 AM, Stéphane SALETTES wrote:


Hi,

You don't understand my problem, maybe because my english is bad :(

ssiad-secretar...@piemont.fr is a standalone account no foward

spa...@piemont.fr is a standalone account no foward

and ss...@piemont.fr is just a foward to spa...@piemont.fr

but if i send a message to ssiad-secretar...@piemont.fr   nothing in is mailbox 
but the message is in the box of spa...@piemont.fr

the work arraound that i find is delete the foward on qmailadmin (mysql) 
(ss...@piemont.fr ->  spa...@piemont.fr) and create a file

.qmail-ssiad
&spa...@piemont.fr


Hope you understand me this time sorry :)

Thank










Cordialement

--
Stephane Salettes


ABAC Informatique
1 Bis Ave Pech Loubat
ZI La Coupe
11100 Narbonne

Tél: 33 (0)4 68 41 73 00
FAX : 33 (0)4 6841 73 02
GSM: 33 (0)6 85 36 67 28

http://www.abac-info.com


-Message d'origine-
De : xaf [mailto:x...@abaxe.net]
Envoyé : samedi 19 avril 2014 03:42
À : vchkpw@inter7.com
Objet : Re: [vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] 
Rrdirection problem

|--> Eric Shubert, le 18/04/2014 23:38, a dit :

3) what you desire to happen

When i send a message to  ssiad-secretar...@piemont.fr i want that
the message go to the ssiad-secretar...@piemont.fr mail box and
foward to spa...@piemont.fr

And when i send a massage to  ss...@piemont.fr i want a simple
foward to spa...@piemont.fr

I think if you modify the ssiad-secretariat@ account to also forward a
copy to spasad@, that would achieve your desired behavior. I.e., in
qmailadmin, under the Routing section, select Forward To, and check
the Save a Copy checkbox.


it's a part of a solution
this will create a .qmail file in the user directory but vdelivermail won't 
read it because of the extension addresses mechanism

Stéphane
ssiad-secretariat@ is an alias for user ssiad@ it's quite a strange conf to 
give a forward to the user and the account to the alias

mail delivery in a glance
qmail-send -> qmail-lspawn -> qmail-local -> vdelivermail -> vuser/valias

we must shorten delivery before vdelivermail handle it because of ssiad 
forward, vdelivermail will ignore ssiad-secretariat account
IMHO a 32 bit guest consumes less memory than a 64 bit one. Unless you

need to address more than 4GB of RAM you really don't get any benefit
from a 64bit VM.

Proxmox dev's seem to agree with me.
http://pve.proxmox.com/wiki/FAQ

Also, the disks should be of type virtio and not IDE. Performance under
IDE sucks big time.


lspawn read users/cdb, we can shorten the delivery here, answer 2 local read 
.qmail-files in domain directory, we can shorten too here, answer 1

answer 1, according vpopmail is in /home/vpopmail create a file 
.qmail-ssiad-secretariat in /home/vpopmail/domains/piemont.fr
0600 vpopmail:vchkpw
write in
&spa...@piemont.fr
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
if you want to change the headers for spasad or 
/home/vpopmail/domains/piemont.fr/spasad/Maildir/
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
for straight copy

answer 2
according to Eric explanation
we have a .qmail in /home/vpopmail/domains/piemont.fr/ssiad-secretariat/
containing
&spa...@piemont.fr
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
we need local to read this .

Re: [vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

[Tom Collins]

This sounds like a possible bug (or perhaps a configuration issue) in 
vdelivermail.

With MySQL aliases, vdelivermail handles delivery.  It's finding the ssiad 
forward first and delivering the message there (since "-secretariat" is an 
extension to that mailbox).

By deleting the alias record stored in MySQL and replacing it with a dot-qmail 
file (.qmail-ssiad), you're allowing Qmail to handle its delivery before the 
message is handed off to vdelivermail.

It's been a long time since I've worked with the vpopmail source code, but I 
imagine you'll find logic in vdelivermail that has it checking for aliases 
before mailboxes, and it's iterating through all possible base/extension pairs 
(foo-bar-baz, then foo-bar, then foo).

-Tom


On Apr 24, 2014, at 12:50 AM, Stéphane SALETTES wrote:

> Hi,
> 
> You don't understand my problem, maybe because my english is bad :(
> 
> ssiad-secretar...@piemont.fr is a standalone account no foward 
> 
> spa...@piemont.fr is a standalone account no foward
> 
> and ss...@piemont.fr is just a foward to spa...@piemont.fr
> 
> but if i send a message to ssiad-secretar...@piemont.fr   nothing in is 
> mailbox but the message is in the box of spa...@piemont.fr
> 
> the work arraound that i find is delete the foward on qmailadmin (mysql) 
> (ss...@piemont.fr ->  spa...@piemont.fr) and create a file 
> 
> .qmail-ssiad
> &spa...@piemont.fr
> 
> 
> Hope you understand me this time sorry :)
> 
> Thank
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Cordialement
> 
> --
> Stephane Salettes
> 
> 
> ABAC Informatique
> 1 Bis Ave Pech Loubat
> ZI La Coupe
> 11100 Narbonne
> 
> Tél: 33 (0)4 68 41 73 00
> FAX : 33 (0)4 6841 73 02
> GSM: 33 (0)6 85 36 67 28
> 
> http://www.abac-info.com
> 
> 
> -Message d'origine-
> De : xaf [mailto:x...@abaxe.net] 
> Envoyé : samedi 19 avril 2014 03:42
> À : vchkpw@inter7.com
> Objet : Re: [vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] 
> Rrdirection problem
> 
> |--> Eric Shubert, le 18/04/2014 23:38, a dit :
>>> 3) what you desire to happen
>>>> When i send a message to  ssiad-secretar...@piemont.fr i want that 
>>>> the message go to the ssiad-secretar...@piemont.fr mail box and 
>>>> foward to spa...@piemont.fr
>>>> 
>>>> And when i send a massage to  ss...@piemont.fr i want a simple 
>>>> foward to spa...@piemont.fr
>> I think if you modify the ssiad-secretariat@ account to also forward a 
>> copy to spasad@, that would achieve your desired behavior. I.e., in 
>> qmailadmin, under the Routing section, select Forward To, and check 
>> the Save a Copy checkbox.
> 
> it's a part of a solution
> this will create a .qmail file in the user directory but vdelivermail won't 
> read it because of the extension addresses mechanism
> 
> Stéphane
> ssiad-secretariat@ is an alias for user ssiad@ it's quite a strange conf to 
> give a forward to the user and the account to the alias
> 
> mail delivery in a glance
> qmail-send -> qmail-lspawn -> qmail-local -> vdelivermail -> vuser/valias
> 
> we must shorten delivery before vdelivermail handle it because of ssiad 
> forward, vdelivermail will ignore ssiad-secretariat account
> 
> lspawn read users/cdb, we can shorten the delivery here, answer 2 local read 
> .qmail-files in domain directory, we can shorten too here, answer 1
> 
> answer 1, according vpopmail is in /home/vpopmail create a file 
> .qmail-ssiad-secretariat in /home/vpopmail/domains/piemont.fr
> 0600 vpopmail:vchkpw
> write in
> &spa...@piemont.fr
> /home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
> if you want to change the headers for spasad or 
> /home/vpopmail/domains/piemont.fr/spasad/Maildir/
> /home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
> for straight copy
> 
> answer 2
> according to Eric explanation
> we have a .qmail in /home/vpopmail/domains/piemont.fr/ssiad-secretariat/
> containing
> &spa...@piemont.fr
> /home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
> we need local to read this .qmail file
> so lspawn have to point to the correct directory before local handle delivery
> 
> edit /var/qmail/users/assign
> add the line (check if 89:89 are uid gid of vpopmail:vchkpw)
> =piemont.fr-ssiad-secretariat:piemont.fr:89:89:/home/vpopmail/domains/piemont.fr/ssiad-secretariat:::
> before the piemont.fr virtual domain line and run /var/qmail/bin/qmail-newu 
> to rebuild /var/qmail/users/cdb
> 
> answer 3
> a forward account instead of a simple forward delete ssiad forward create 
> ssiad account apply Eric solution without saving a copy ssiad will be master 
> for ssiad-everything but secretariat
> 
> xaf
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 


!DSPAM:53593f3d34268127549349!

RE: [vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

[Stéphane SALETTES]

Hi,

You don't understand my problem, maybe because my english is bad :(

ssiad-secretar...@piemont.fr is a standalone account no foward 

spa...@piemont.fr is a standalone account no foward

and ss...@piemont.fr is just a foward to spa...@piemont.fr

but if i send a message to ssiad-secretar...@piemont.fr   nothing in is mailbox 
but the message is in the box of spa...@piemont.fr

the work arraound that i find is delete the foward on qmailadmin (mysql) 
(ss...@piemont.fr ->  spa...@piemont.fr) and create a file 

.qmail-ssiad
&spa...@piemont.fr


Hope you understand me this time sorry :)

Thank










Cordialement

--
Stephane Salettes


ABAC Informatique
1 Bis Ave Pech Loubat
ZI La Coupe
11100 Narbonne

Tél: 33 (0)4 68 41 73 00
FAX : 33 (0)4 6841 73 02
GSM: 33 (0)6 85 36 67 28

http://www.abac-info.com


-Message d'origine-
De : xaf [mailto:x...@abaxe.net] 
Envoyé : samedi 19 avril 2014 03:42
À : vchkpw@inter7.com
Objet : Re: [vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] 
Rrdirection problem

|--> Eric Shubert, le 18/04/2014 23:38, a dit :
>> 3) what you desire to happen
>> > When i send a message to  ssiad-secretar...@piemont.fr i want that 
>> > the message go to the ssiad-secretar...@piemont.fr mail box and 
>> > foward to spa...@piemont.fr
>> >
>> > And when i send a massage to  ss...@piemont.fr i want a simple 
>> > foward to spa...@piemont.fr
> I think if you modify the ssiad-secretariat@ account to also forward a 
> copy to spasad@, that would achieve your desired behavior. I.e., in 
> qmailadmin, under the Routing section, select Forward To, and check 
> the Save a Copy checkbox.

it's a part of a solution
this will create a .qmail file in the user directory but vdelivermail won't 
read it because of the extension addresses mechanism

Stéphane
ssiad-secretariat@ is an alias for user ssiad@ it's quite a strange conf to 
give a forward to the user and the account to the alias

mail delivery in a glance
qmail-send -> qmail-lspawn -> qmail-local -> vdelivermail -> vuser/valias

we must shorten delivery before vdelivermail handle it because of ssiad 
forward, vdelivermail will ignore ssiad-secretariat account

lspawn read users/cdb, we can shorten the delivery here, answer 2 local read 
.qmail-files in domain directory, we can shorten too here, answer 1

answer 1, according vpopmail is in /home/vpopmail create a file 
.qmail-ssiad-secretariat in /home/vpopmail/domains/piemont.fr
0600 vpopmail:vchkpw
write in
&spa...@piemont.fr
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
if you want to change the headers for spasad or 
/home/vpopmail/domains/piemont.fr/spasad/Maildir/
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
for straight copy

answer 2
according to Eric explanation
we have a .qmail in /home/vpopmail/domains/piemont.fr/ssiad-secretariat/
containing
&spa...@piemont.fr
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
we need local to read this .qmail file
so lspawn have to point to the correct directory before local handle delivery

edit /var/qmail/users/assign
add the line (check if 89:89 are uid gid of vpopmail:vchkpw)
=piemont.fr-ssiad-secretariat:piemont.fr:89:89:/home/vpopmail/domains/piemont.fr/ssiad-secretariat:::
before the piemont.fr virtual domain line and run /var/qmail/bin/qmail-newu to 
rebuild /var/qmail/users/cdb

answer 3
a forward account instead of a simple forward delete ssiad forward create ssiad 
account apply Eric solution without saving a copy ssiad will be master for 
ssiad-everything but secretariat

xaf








!DSPAM:5358c24734262119615012!

[vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

[Eric Shubert]

On 04/18/2014 06:41 PM, xaf wrote:

|--> Eric Shubert, le 18/04/2014 23:38, a dit :

3) what you desire to happen

When i send a message to  ssiad-secretar...@piemont.fr i want that the message 
go to the ssiad-secretar...@piemont.fr mail box and foward to spa...@piemont.fr

And when i send a massage to  ss...@piemont.fr i want a simple foward to 
spa...@piemont.fr

I think if you modify the ssiad-secretariat@ account to also forward a
copy to spasad@, that would achieve your desired behavior. I.e., in
qmailadmin, under the Routing section, select Forward To, and check the
Save a Copy checkbox.


it's a part of a solution
this will create a .qmail file in the user directory
but vdelivermail won't read it
because of the extension addresses mechanism

Stéphane
ssiad-secretariat@ is an alias for user ssiad@
it's quite a strange conf to give a forward to the user
and the account to the alias

mail delivery in a glance
qmail-send -> qmail-lspawn -> qmail-local -> vdelivermail -> vuser/valias

we must shorten delivery before vdelivermail handle it
because of ssiad forward, vdelivermail will ignore ssiad-secretariat account

lspawn read users/cdb, we can shorten the delivery here, answer 2
local read .qmail-files in domain directory, we can shorten too here, answer 1

answer 1, according vpopmail is in /home/vpopmail
create a file .qmail-ssiad-secretariat in /home/vpopmail/domains/piemont.fr
0600 vpopmail:vchkpw
write in
&spa...@piemont.fr
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
if you want to change the headers for spasad
or
/home/vpopmail/domains/piemont.fr/spasad/Maildir/
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
for straight copy

answer 2
according to Eric explanation
we have a .qmail in /home/vpopmail/domains/piemont.fr/ssiad-secretariat/
containing
&spa...@piemont.fr
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
we need local to read this .qmail file
so lspawn have to point to the correct directory
before local handle delivery

edit /var/qmail/users/assign
add the line (check if 89:89 are uid gid of vpopmail:vchkpw)
=piemont.fr-ssiad-secretariat:piemont.fr:89:89:/home/vpopmail/domains/piemont.fr/ssiad-secretariat:::
before the piemont.fr virtual domain line
and run /var/qmail/bin/qmail-newu to rebuild /var/qmail/users/cdb

answer 3
a forward account instead of a simple forward
delete ssiad forward
create ssiad account
apply Eric solution without saving a copy
ssiad will be master for ssiad-everything but secretariat

xaf










Thanks for this post, xaf. It's the best description I've seen of 
delivery in the 8 years I've been using QMT. I expect this will be 
helpful when we integrate Dovecot's LDA in the near future.


Stéphane,
FWIW, I'd go with answer #3. It seems to me to be the simplest given 
your situation. It can all be done with qmailadmin, with no need to use 
any CLI configuration methods.


--
-Eric 'shubes'


!DSPAM:5352a9f034261066319550!

Re: [vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

[xaf]

|--> Eric Shubert, le 18/04/2014 23:38, a dit :
>> 3) what you desire to happen
>> > When i send a message to  ssiad-secretar...@piemont.fr i want that the 
>> > message go to the ssiad-secretar...@piemont.fr mail box and foward to 
>> > spa...@piemont.fr
>> >
>> > And when i send a massage to  ss...@piemont.fr i want a simple foward to 
>> > spa...@piemont.fr
> I think if you modify the ssiad-secretariat@ account to also forward a 
> copy to spasad@, that would achieve your desired behavior. I.e., in 
> qmailadmin, under the Routing section, select Forward To, and check the 
> Save a Copy checkbox.

it's a part of a solution
this will create a .qmail file in the user directory
but vdelivermail won't read it
because of the extension addresses mechanism

Stéphane
ssiad-secretariat@ is an alias for user ssiad@
it's quite a strange conf to give a forward to the user
and the account to the alias

mail delivery in a glance
qmail-send -> qmail-lspawn -> qmail-local -> vdelivermail -> vuser/valias

we must shorten delivery before vdelivermail handle it
because of ssiad forward, vdelivermail will ignore ssiad-secretariat account

lspawn read users/cdb, we can shorten the delivery here, answer 2
local read .qmail-files in domain directory, we can shorten too here, answer 1

answer 1, according vpopmail is in /home/vpopmail
create a file .qmail-ssiad-secretariat in /home/vpopmail/domains/piemont.fr
0600 vpopmail:vchkpw
write in
&spa...@piemont.fr
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
if you want to change the headers for spasad
or
/home/vpopmail/domains/piemont.fr/spasad/Maildir/
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
for straight copy

answer 2
according to Eric explanation
we have a .qmail in /home/vpopmail/domains/piemont.fr/ssiad-secretariat/
containing
&spa...@piemont.fr
/home/vpopmail/domains/piemont.fr/ssiad-secretariat/Maildir/
we need local to read this .qmail file
so lspawn have to point to the correct directory
before local handle delivery

edit /var/qmail/users/assign
add the line (check if 89:89 are uid gid of vpopmail:vchkpw)
=piemont.fr-ssiad-secretariat:piemont.fr:89:89:/home/vpopmail/domains/piemont.fr/ssiad-secretariat:::
before the piemont.fr virtual domain line
and run /var/qmail/bin/qmail-newu to rebuild /var/qmail/users/cdb

answer 3
a forward account instead of a simple forward
delete ssiad forward
create ssiad account
apply Eric solution without saving a copy
ssiad will be master for ssiad-everything but secretariat

xaf





!DSPAM:5351d45834261943715214!

[vchkpw] Re: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

[Eric Shubert]

In that case,
On 04/18/2014 08:44 AM, Stéphane SALETTES wrote:

1) There are 2 emails accounts, spa...@piemont.fr , ssiad-secretar...@piemont.fr
ss...@piemont.fr simply a forward with no account to spa...@piemont.fr


I see.


2) what actually happens
When a message is sent to ssiad-secretar...@piemont.fr , 
ssiad-secretar...@piemont.fr doesn't receive this message but spa...@piemont.fr 
yes


That's what I would expect to happen, given your configuration.


3) what you desire to happen
When i send a message to  ssiad-secretar...@piemont.fr i want that the message 
go to the ssiad-secretar...@piemont.fr mail box and foward to spa...@piemont.fr

And when i send a massage to  ss...@piemont.fr i want a simple foward to 
spa...@piemont.fr


I think if you modify the ssiad-secretariat@ account to also forward a 
copy to spasad@, that would achieve your desired behavior. I.e., in 
qmailadmin, under the Routing section, select Forward To, and check the 
Save a Copy checkbox.


If that doesn't do what you desire, please explain how you expect your 
configuration to behave.


--
-Eric 'shubes'


thank



siad-secretar...@piemont.fr <mailto:siad-secretar...@piemont.fr>


spa...@piemont.fr <mailto:spa...@piemont.fr>

ss...@piemont.fr <mailto:ss...@piemont.fr>


Cordialement

--
Stephane Salettes


ABAC Informatique
1 Bis Ave Pech Loubat
ZI La Coupe
11100 Narbonne

Tél: 33 (0)4 68 41 73 00
FAX : 33 (0)4 6841 73 02
GSM: 33 (0)6 85 36 67 28

http://www.abac-info.com


-Message d'origine-
De : Eric Shubert [mailto:e...@shubes.net]
Envoyé : jeudi 17 avril 2014 17:50
À : vchkpw@inter7.com
Objet : !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

Stéphane,

This does not appear to me to be what was written on the QMT list.

In order to be clear, please describe:
1) your configuration (what are accounts, what are forwards)
2) what actually happens
3) what you desire to happen

For example:
1) There are 2 email accounts, ss...@piemont.fr and spa...@piemont.fr.
The ss...@piemont.fr account is configured to forward messages to 
spa...@piemont.fr. (Or is ss...@piemont.fr simply a forward with no
account?)

2) When an email is sent to ??, it arrives at ??.

3) When an email is sent to ??, I'd like it to arrive at ??.

Thanks.

P.S. You've repeatedly written siad-secretariat@, which I assumed was a typo 
and you meant ssiad-secretariat@. Is this the case or not?

--
-Eric 'shubes'

On 04/17/2014 07:16 AM, Stéphane SALETTES wrote:

This is 3 emails box

siad-secretar...@piemont.fr <mailto:siad-secretar...@piemont.fr>

spa...@piemont.fr <mailto:spa...@piemont.fr>

ss...@piemont.fr <mailto:ss...@piemont.fr>

and a redirection ss...@piemont.fr <mailto:ss...@piemont.fr>to
spa...@piemont.fr <mailto:spa...@piemont.fr>

When I send an email to siad-secretar...@piemont.fr
<mailto:siad-secretar...@piemont.fr>  he did not

receive but  is spa...@piemont.fr <mailto:spa...@piemont.fr> who
receives

Thank

Cordialement

--

Stephane Salettes


ABAC Informatique
1 Bis Ave Pech Loubat

ZI La Coupe
11100 Narbonne

Tél: 33 (0)4 68 41 73 00
FAX : 33 (0)4 6841 73 02
GSM: 33 (0)6 85 36 67 28

http://www.abac-info.com http://www.abac-info.com/>

logo


















!DSPAM:53519b6834261578218977!

[vchkpw] RE: !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

[Stéphane SALETTES]

1) There are 2 emails accounts, spa...@piemont.fr , ssiad-secretar...@piemont.fr
ss...@piemont.fr simply a forward with no account to spa...@piemont.fr

2) what actually happens
When a message is sent to ssiad-secretar...@piemont.fr , 
ssiad-secretar...@piemont.fr doesn't receive this message but spa...@piemont.fr 
yes

3) what you desire to happen
When i send a message to  ssiad-secretar...@piemont.fr i want that the message 
go to the ssiad-secretar...@piemont.fr mail box and foward to spa...@piemont.fr 

And when i send a massage to  ss...@piemont.fr i want a simple foward to 
spa...@piemont.fr

thank



siad-secretar...@piemont.fr <mailto:siad-secretar...@piemont.fr>
>
> spa...@piemont.fr <mailto:spa...@piemont.fr>
>
> ss...@piemont.fr <mailto:ss...@piemont.fr>

Cordialement

--
Stephane Salettes


ABAC Informatique
1 Bis Ave Pech Loubat
ZI La Coupe
11100 Narbonne

Tél: 33 (0)4 68 41 73 00
FAX : 33 (0)4 6841 73 02
GSM: 33 (0)6 85 36 67 28

http://www.abac-info.com


-Message d'origine-
De : Eric Shubert [mailto:e...@shubes.net] 
Envoyé : jeudi 17 avril 2014 17:50
À : vchkpw@inter7.com
Objet : !!! CHECK SENDER !!![vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

Stéphane,

This does not appear to me to be what was written on the QMT list.

In order to be clear, please describe:
1) your configuration (what are accounts, what are forwards)
2) what actually happens
3) what you desire to happen

For example:
1) There are 2 email accounts, ss...@piemont.fr and spa...@piemont.fr. 
The ss...@piemont.fr account is configured to forward messages to 
spa...@piemont.fr. (Or is ss...@piemont.fr simply a forward with no
account?)

2) When an email is sent to ??, it arrives at ??.

3) When an email is sent to ??, I'd like it to arrive at ??.

Thanks.

P.S. You've repeatedly written siad-secretariat@, which I assumed was a typo 
and you meant ssiad-secretariat@. Is this the case or not?

--
-Eric 'shubes'

On 04/17/2014 07:16 AM, Stéphane SALETTES wrote:
> This is 3 emails box
>
> siad-secretar...@piemont.fr <mailto:siad-secretar...@piemont.fr>
>
> spa...@piemont.fr <mailto:spa...@piemont.fr>
>
> ss...@piemont.fr <mailto:ss...@piemont.fr>
>
> and a redirection ss...@piemont.fr <mailto:ss...@piemont.fr>to
> spa...@piemont.fr <mailto:spa...@piemont.fr>
>
> When I send an email to siad-secretar...@piemont.fr 
> <mailto:siad-secretar...@piemont.fr>  he did not
>
> receive but  is spa...@piemont.fr <mailto:spa...@piemont.fr> who 
> receives
>
> Thank
>
> Cordialement
>
> --
>
> Stephane Salettes
>
>
> ABAC Informatique
> 1 Bis Ave Pech Loubat
>
> ZI La Coupe
> 11100 Narbonne
>
> Tél: 33 (0)4 68 41 73 00
> FAX : 33 (0)4 6841 73 02
> GSM: 33 (0)6 85 36 67 28
>
> http://www.abac-info.com http://www.abac-info.com/>
>
> logo
>
> 







!DSPAM:5351484734261160721075!

Re: [vchkpw] [SPAM] Re: [vchkpw] Patches for qmail suggestions and upgrade

[Alessio Cecchi]

Il 17/04/2014 20:39, Jeremy Kister ha scritto:

On 4/17/2014 2:33 PM, Remo Mattei wrote:

Hello all
I have a qmail which is running now I want to up it to netqmail 1.06
so I plan to recomp it and I have vpopmail working so on the new one I
want to add chkuser and tls but also few others like the channel since
gmail and others have been really a pain does anyone suggest a set of
patches or one that does it all in one?


i still like and use my qmail-1.03.isp.patch

it's named "isp" because i was working for an isp at the them and had
nothing better to name it.  it's used in lots of places that have
nothing to do with an isp.


http://jeremy.kister.net/code/qmail-1.03.isp.patch



Hi,

I'm also running the qmail-1.03.isp.patch from Jeremy and I can confirm 
that works really fine for "ISP".


I have made some small add to Jeremy's patch:

http://notes.sagredo.eu/sites/notes.sagredo.eu/files/qmail/patches/qmail-1.03-reread-concurrency.2.patch

and

http://notes.sagredo.eu/sites/notes.sagredo.eu/files/qmail/patches/qmail-queue-custom-error-v2.netqmail-1.05.patch

I'm also using http://jeremy.kister.net/code/ucspi-tcp-0.88.isp.patch.

Thanks Jeremy for your code!

--
Alessio Cecchi is:
@ ILS -> http://www.linux.it/~alessice/
on LinkedIn -> http://www.linkedin.com/in/alessice
Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz
Cloud Email Hosting -> http://www.qboxmail.com
@ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it

!DSPAM:5350c49234262695215939!

Re: [vchkpw] [SPAM] Re: [vchkpw] Patches for qmail suggestions and upgrade

[Remo Mattei]

Nice does it have tls?

Inviato da iPhone ()

> Il giorno Apr 17, 2014, alle ore 11:39, Jeremy Kister 
>  ha scritto:
> 
>> On 4/17/2014 2:33 PM, Remo Mattei wrote:
>> Hello all
>> I have a qmail which is running now I want to up it to netqmail 1.06 so I 
>> plan to recomp it and I have vpopmail working so on the new one I want to 
>> add chkuser and tls but also few others like the channel since gmail and 
>> others have been really a pain does anyone suggest a set of patches or one 
>> that does it all in one?
> 
> i still like and use my qmail-1.03.isp.patch
> 
> it's named "isp" because i was working for an isp at the them and had nothing 
> better to name it.  it's used in lots of places that have nothing to do with 
> an isp.
> 
> 
> http://jeremy.kister.net/code/qmail-1.03.isp.patch
> 
> -- 
> 
> Jeremy Kister
> http://jeremy.kister.net./
> 
> 
> 
> 
> 
> 
> 

!DSPAM:535022f934261946090414!

Re: [vchkpw] [SPAM] Re: [vchkpw] Patches for qmail suggestions and upgrade

[Remo Mattei]

Do u know what does this patch include will it work on netqmail 1.06?

Thanks

Inviato da iPhone ()

> Il giorno Apr 17, 2014, alle ore 11:39, Jeremy Kister 
>  ha scritto:
> 
>> On 4/17/2014 2:33 PM, Remo Mattei wrote:
>> Hello all
>> I have a qmail which is running now I want to up it to netqmail 1.06 so I 
>> plan to recomp it and I have vpopmail working so on the new one I want to 
>> add chkuser and tls but also few others like the channel since gmail and 
>> others have been really a pain does anyone suggest a set of patches or one 
>> that does it all in one?
> 
> i still like and use my qmail-1.03.isp.patch
> 
> it's named "isp" because i was working for an isp at the them and had nothing 
> better to name it.  it's used in lots of places that have nothing to do with 
> an isp.
> 
> 
> http://jeremy.kister.net/code/qmail-1.03.isp.patch
> 
> -- 
> 
> Jeremy Kister
> http://jeremy.kister.net./
> 
> 
> 
> 
> 
> 
> 

!DSPAM:5350229534261724115646!

[vchkpw] [SPAM] Re: [vchkpw] Patches for qmail suggestions and upgrade

[Jeremy Kister]

On 4/17/2014 2:33 PM, Remo Mattei wrote:

Hello all
I have a qmail which is running now I want to up it to netqmail 1.06 so I plan 
to recomp it and I have vpopmail working so on the new one I want to add 
chkuser and tls but also few others like the channel since gmail and others 
have been really a pain does anyone suggest a set of patches or one that does 
it all in one?


i still like and use my qmail-1.03.isp.patch

it's named "isp" because i was working for an isp at the them and had 
nothing better to name it.  it's used in lots of places that have 
nothing to do with an isp.



http://jeremy.kister.net/code/qmail-1.03.isp.patch

--

Jeremy Kister
http://jeremy.kister.net./


!DSPAM:53501fe034262670412911!

[vchkpw] [SPAM] Patches for qmail suggestions and upgrade

[Remo Mattei]

Hello all
I have a qmail which is running now I want to up it to netqmail 1.06 so I plan 
to recomp it and I have vpopmail working so on the new one I want to add 
chkuser and tls but also few others like the channel since gmail and others 
have been really a pain does anyone suggest a set of patches or one that does 
it all in one? 

Thanks


Inviato da iPhone ()
!DSPAM:53501ec534266584610313!

[vchkpw] [SPAM] Re: [SPAM] Rrdirection problem

[Eric Shubert]

Stéphane,

This does not appear to me to be what was written on the QMT list.

In order to be clear, please describe:
1) your configuration (what are accounts, what are forwards)
2) what actually happens
3) what you desire to happen

For example:
1) There are 2 email accounts, ss...@piemont.fr and spa...@piemont.fr. 
The ss...@piemont.fr account is configured to forward messages to 
spa...@piemont.fr. (Or is ss...@piemont.fr simply a forward with no 
account?)


2) When an email is sent to ??, it arrives at ??.

3) When an email is sent to ??, I'd like it to arrive at ??.

Thanks.

P.S. You've repeatedly written siad-secretariat@, which I assumed was a 
typo and you meant ssiad-secretariat@. Is this the case or not?


--
-Eric 'shubes'

On 04/17/2014 07:16 AM, Stéphane SALETTES wrote:

This is 3 emails box

siad-secretar...@piemont.fr 

spa...@piemont.fr 

ss...@piemont.fr 

and a redirection ss...@piemont.fr to
spa...@piemont.fr 

When I send an email to siad-secretar...@piemont.fr
  he did not

receive but  is spa...@piemont.fr  who receives

Thank

Cordialement

--

Stephane Salettes


ABAC Informatique
1 Bis Ave Pech Loubat

ZI La Coupe
11100 Narbonne

Tél: 33 (0)4 68 41 73 00
FAX : 33 (0)4 6841 73 02
GSM: 33 (0)6 85 36 67 28

http://www.abac-info.com http://www.abac-info.com/>

logo







!DSPAM:534ff83234265858656019!

[vchkpw] [SPAM] vpopmail and qmail/assign subaddress separator configuration

[Tom Ierna]

Hello,

I have a couple of vpopmail/qmail-based e-mail servers that have worked well 
for many years.

A few years ago, we began using the Calendar Server on MacOSX. The calendar 
server sits on an internet pipe which doesn't pass port 25, so I can't use the 
built-in mail server to handle calendar invites and replies. Luckily, the 
Calendar Server configuration allows you to set up an e-mail address which it 
will use to send invites via SMTP and receive replies to the invites via IMAP.

Initially, I tried to set up an address on one of my vpopmail/qmail servers, as 
they service the domains which these calendar servers sit on. However, the 
Calendar Server uses "+" subaddressing, and vpopmail/qmail use "-" 
subaddressing.

The qmail docs say that you can configure the subaddress separator character by 
changing the "-" to a "+" following the user name in /var/qmail/users/assign. 
In vpopmail, users aren't in the assign file - it seems to contain a listing of 
domains that vpopmail services. Unsurprisingly, changing the "-" to a "+" and 
running qmail-newu as the qmail docs suggest doesn't change the subaddressing 
behavior for that domain.

The workaround since I did this research last has been to use a Gmail account 
specifically for each Calendar Server I maintained. This worked for a while, 
but then at some point recently, Gmail and Google Calendar started causing 
invites to be handled improperly. I'm not sure what conditions are necessary, 
but it seems like it has something to do with the recipient using Google 
Calendar instead of another calendar service with their Gmail address (and why 
wouldn't they?)

In any case, I'm again looking into how to make a domain on one of my 
vpopmail/qmail servers use the "+" separator for subaddresses, rather than "-", 
and I'm coming up dry. I realize that changing the subaddress separator will 
have an effect on ezmlm-idx, which I use on this server, so that's why I only 
want to change the subaddress separator on a single domain.

Any pointers?

Thanks,
-Tom
!DSPAM:534c460734269808015307!

[vchkpw] Re: [SPAM] Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp

[Eric Shubert]

PLAIN authentication is ok, provided that TLS has been activated by the 
client (presumably before credentials are sent) or SSL is in use 
(unconventional 465 port).


In changing this, each client will need to be manually reconfigured. I'm 
not aware of any client that automatically adjusts to changes such as this.


I'm not aware of a practical way to require encrypted passwords for 
qmail-smtpd (whether on port 25 or 587) at this point. Spamdyke has a 
recent feature allowing it to handle authentication, and I believe that 
Sam will be adding a setting to require encryption before authentication 
in the next release. When that's available, I'll be changing QMT to use 
spamdyke for authentication, which will (at last) allow for enforcement 
of this policy (no passwords sent in clear text).


On the retrieval side of things, dovecot provides such a configuration 
parameter, #disable_plaintext_auth = yes, which is the default value.


P.S. FWIW, I would have not expected to see (as many) unauthorized 
attempts on port 587. Spammers will eventually use this port though.


--
-Eric 'shubes'

On 03/05/2014 08:34 AM, LHTek wrote:

I am using PLAIN text passwords I'm afraid. I will be changing that now
though. I very tired of these password hacks.

Since this will be a new process for me I have questions: In changing
the server to require encrypted passwords, will I need to contact all my
clients and have them change the way they connect? Or will their email
clients just automate the change?





*From:* "c...@milos.co.za" 
*To:* vchkpw@inter7.com
*Sent:* Wednesday, March 5, 2014 6:45 AM
*Subject:* [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM]
Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp

It doesn't matter how good your password is if you're using
plaintext connections :)
Since every MUA I've used i nthe last few years supports SSL or TLS
I should really get around to deprecating pop3 and imap and only
using pop3s and imaps.
This is especially imporant since some govts are trying to push
through laws forcing ISP's to store all of the data each of their
users downloads meaning that your unencrypted data will remain
stored for however long is legislated with access by who knows how
many people.
\\Clay
On 2014-03-05 07:57, Tom Collins wrote:

The submission entries outside the US could very well be from
hacked accounts.
I'm finding a surprising number of compromised accounts (once a
week?), including users with good passwords, so I have to assume
they're snooped on public wireless, or their computers are
compromised by malware of some sort.
The vckpw-smtp entries from outside the US are probably also
hacked accounts, since mail received from remote servers doesn't
include authentication.  Sorry I wasn't thinking clearly in my
previous response -- I forgot these were vchkpw entries and are
only related to authentication.  I was thinking about qmail logs.

-Tom

On Mar 4, 2014, at 10:43 PM, LHTek wrote:


Thanks for the reply.

NOTE: None of my users will have sent anything from outside the US.

I've got some log entries for vchkpw-submission (marked as
successful in the log) with non-US IP's (Russia, Egypt, Honk
Kong, etc).In my analysis I'm marking those entries as hacked
accounts.

From what I read from your response, vchkpw-smtp (marked as
successful in the log) entries could be mail sent TO my server
FROM another server on port 25. That tells me those are probably
safe submissions - even if they are from overseas IPs. Am I
thinking correctly?


*From:* Tom Collins mailto:t...@tomlogic.com>>
*To:* vchkpw@inter7.com <mailto:vchkpw@inter7.com>
*Sent:* Wednesday, March 5, 2014 12:02 AM
*Subject:* Re: [vchkpw] Qmail maillog vchkpw-submission vs
vchkpw-smtp

vchkpw-submission is on port 587, and is typically used for
emai clients relaying mail.  It's often set up to require
authentication.
vchkpw-smtp is on port 25, and can be used for email clients
to relay mail, or by other servers delivering mail to your
server.

-Tom

On Mar 4, 2014, at 9:41 PM, LHTek wrote:


In the /var/log/maillog file what is the difference between
these 2 entries (vchkpw-submission, vchkpw-smtp)?
example:
Mar  4 17:27:03 michael vpopmail[14701]: vchkpw-submission:
(PLAIN) login success t...@domain.com:64.185.3.238
Mar  4 10:54:42 michael vpopmail[29027]: vchkpw-smtp:
(PLAIN) login success t...@domain.com:64.57.239.114












!DSPAM:531756ed34261630194476!

Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp

[LHTek]

I am using PLAIN text passwords I'm afraid. I will be changing that now though. 
I very tired of these password hacks.

Since this will be a new process for me I have questions: In changing the 
server to require encrypted passwords, will I need to contact all my clients 
and have them change the way they connect? Or will their email clients just 
automate the change?







>
> From: "c...@milos.co.za" 
>To: vchkpw@inter7.com 
>Sent: Wednesday, March 5, 2014 6:45 AM
>Subject: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Re: [vchkpw] 
>Qmail maillog  vchkpw-submission vs vchkpw-smtp
> 
>
>
>It doesn't matter how good your password is if you're using plaintext 
>connections :)
>Since every MUA I've used i nthe last few years supports SSL or TLS I should 
>really get around to deprecating pop3 and imap and only using pop3s and imaps.
>This is especially imporant since some govts are trying to push through laws 
>forcing ISP's to store all of the data each of their users downloads meaning 
>that your unencrypted data will remain stored for however long is legislated 
>with access by who knows how many people.
> 
>\\Clay
> 
>On 2014-03-05 07:57, Tom Collins wrote:
>The submission entries outside the US could very well be from hacked accounts. 
>> 
>>I'm finding a surprising number of compromised accounts (once a week?), 
>>including users with good passwords, so I have to assume they're snooped on 
>>public wireless, or their computers are compromised by malware of some sort.
>> 
>>The vckpw-smtp entries from outside the US are probably also hacked accounts, 
>>since mail received from remote servers doesn't include authentication.  
>>Sorry I wasn't thinking clearly in my previous response -- I forgot these 
>>were vchkpw entries and are only related to authentication.  I was thinking 
>>about qmail logs.
>>
>>
>>-Tom
>>
>>On Mar 4, 2014, at 10:43 PM, LHTek wrote:
>>
>>Thanks for the reply.
>>>
>>>NOTE: None of my users will have sent anything from outside the US.
>>>
>>>I've got some log entries for vchkpw-submission (marked as successful in the 
>>>log) with non-US IP's (Russia, Egypt, Honk Kong, etc).In my analysis I'm 
>>>marking those entries as hacked accounts. 
>>>
>>>
>>>From what I read from your response, vchkpw-smtp (marked as successful in 
>>>the log) entries could be mail sent TO my server FROM another server on port 
>>>25. That tells me those are probably safe submissions - even if they are 
>>>from overseas IPs. Am I thinking correctly?
>>> 
>>> 
>>> 
>>>
>>>
>>>
>>>>
>>>>From: Tom Collins 
>>>>To: vchkpw@inter7.com 
>>>>Sent: Wednesday, March 5, 2014 12:02 AM
>>>>Subject: Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp
>>>>
>>>>
>>>>
>>>>vchkpw-submission is on port 587, and is typically used for emai clients 
>>>>relaying mail.  It's often set up to require authentication. 
>>>> 
>>>>vchkpw-smtp is on port 25, and can be used for email clients to relay mail, 
>>>>or by other servers delivering mail to your server.
>>>>
>>>>
>>>> 
>>>>-Tom
>>>>
>>>>On Mar 4, 2014, at 9:41 PM, LHTek wrote:
>>>>
>>>>In the /var/log/maillog file what is the difference between these 2 entries 
>>>>(vchkpw-submission, vchkpw-smtp)?
>>>>> 
>>>>>example:
>>>>>Mar  4 17:27:03 michael vpopmail[14701]: vchkpw-submission: (PLAIN) login 
>>>>>success t...@domain.com:64.185.3.238
>>>>>Mar  4 10:54:42 michael vpopmail[29027]: vchkpw-smtp: (PLAIN) login 
>>>>>success t...@domain.com:64.57.239.114
>>>>> 
>>>>> 
>>>>
>>>>
> 
> 
 
>
>

!DSPAM:531743f234265098613353!

[vchkpw] [SPAM] Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp

[clay]

 

It doesn't matter how good your password is if you're using plaintext
connections :) 

Since every MUA I've used i nthe last few years supports SSL or TLS I
should really get around to deprecating pop3 and imap and only using
pop3s and imaps. 

This is especially imporant since some govts are trying to push through
laws forcing ISP's to store all of the data each of their users
downloads meaning that your unencrypted data will remain stored for
however long is legislated with access by who knows how many people. 

\Clay 

On 2014-03-05 07:57, Tom Collins wrote: 

> The submission entries outside the US could very well be from hacked 
> accounts. 
> 
> I'm finding a surprising number of compromised accounts (once a week?), 
> including users with good passwords, so I have to assume they're snooped on 
> public wireless, or their computers are compromised by malware of some sort. 
> 
> The vckpw-smtp entries from outside the US are probably also hacked accounts, 
> since mail received from remote servers doesn't include authentication. Sorry 
> I wasn't thinking clearly in my previous response -- I forgot these were 
> vchkpw entries and are only related to authentication. I was thinking about 
> qmail logs. 
> 
> -Tom 
> 
> On Mar 4, 2014, at 10:43 PM, LHTek wrote: 
> 
> Thanks for the reply.
> 
> NOTE: None of my users will have sent anything from outside the US.
> 
> I've got some log entries for vchkpw-submission (marked as successful in the 
> log) with non-US IP's (Russia, Egypt, Honk Kong, etc). In my analysis I'm 
> marking those entries as hacked accounts. 
> 
> From what I read from your response, vchkpw-smtp (marked as successful in the 
> log) entries could be mail sent TO my server FROM another server on port 25. 
> That tells me those are probably safe submissions - even if they are from 
> overseas IPs. Am I thinking correctly? 
> 
> -
> FROM: Tom Collins 
> TO: vchkpw@inter7.com 
> SENT: Wednesday, March 5, 2014 12:02 AM
> SUBJECT: Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp
> 
> vchkpw-submission is on port 587, and is typically used for emai clients 
> relaying mail. It's often set up to require authentication. 
> 
> vchkpw-smtp is on port 25, and can be used for email clients to relay mail, 
> or by other servers delivering mail to your server. 
> 
> -Tom 
> 
> On Mar 4, 2014, at 9:41 PM, LHTek wrote: 
> 
> In the /var/log/maillog file what is the difference between these 2 entries 
> (vchkpw-submission, vchkpw-smtp)? 
> 
> example: 
> Mar 4 17:27:03 michael vpopmail[14701]: vchkpw-submission: (PLAIN) login 
> success t...@domain.com:64.185.3.238 
> Mar 4 10:54:42 michael vpopmail[29027]: vchkpw-smtp: (PLAIN) login success 
> t...@domain.com:64.57.239.114
  

 

!DSPAM:53171ca934269165765629!

[vchkpw] [SPAM] Re: [vchkpw] [SPAM] Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp

[Tom Collins]

The submission entries outside the US could very well be from hacked accounts.

I'm finding a surprising number of compromised accounts (once a week?), 
including users with good passwords, so I have to assume they're snooped on 
public wireless, or their computers are compromised by malware of some sort.

The vckpw-smtp entries from outside the US are probably also hacked accounts, 
since mail received from remote servers doesn't include authentication.  Sorry 
I wasn't thinking clearly in my previous response -- I forgot these were vchkpw 
entries and are only related to authentication.  I was thinking about qmail 
logs.

-Tom


On Mar 4, 2014, at 10:43 PM, LHTek wrote:

> Thanks for the reply.
> 
> NOTE: None of my users will have sent anything from outside the US.
> 
> I've got some log entries for vchkpw-submission (marked as successful in the 
> log) with non-US IP's (Russia, Egypt, Honk Kong, etc). In my analysis I'm 
> marking those entries as hacked accounts.
> 
> From what I read from your response, vchkpw-smtp (marked as successful in the 
> log) entries could be mail sent TO my server FROM another server on port 25. 
> That tells me those are probably safe submissions - even if they are from 
> overseas IPs. Am I thinking correctly?
> 
> 
> 
> 
> From: Tom Collins 
> To: vchkpw@inter7.com 
> Sent: Wednesday, March 5, 2014 12:02 AM
> Subject: Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp
> 
> vchkpw-submission is on port 587, and is typically used for emai clients 
> relaying mail.  It's often set up to require authentication.
> 
> vchkpw-smtp is on port 25, and can be used for email clients to relay mail, 
> or by other servers delivering mail to your server.
> 
> -Tom
> 
> 
> On Mar 4, 2014, at 9:41 PM, LHTek wrote:
> 
>> In the /var/log/maillog file what is the difference between these 2 entries 
>> (vchkpw-submission, vchkpw-smtp)?
>> 
>> example:
>> Mar  4 17:27:03 michael vpopmail[14701]: vchkpw-submission: (PLAIN) login 
>> success t...@domain.com:64.185.3.238
>> Mar  4 10:54:42 michael vpopmail[29027]: vchkpw-smtp: (PLAIN) login success 
>> t...@domain.com:64.57.239.114
>> 
>> 
> 
> 
> 
> 



!DSPAM:5316cae034263249811152!

[vchkpw] [SPAM] Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp

[LHTek]

Thanks for the reply.

NOTE: None of my users will have sent anything from outside the US.

I've got some log entries for vchkpw-submission (marked as successful in the 
log) with non-US IP's (Russia, Egypt, Honk Kong, etc).In my analysis I'm 
marking those entries as hacked accounts.

>From what I read from your response, vchkpw-smtp (marked as successful in the 
>log) entries could be mail sent TO my server FROM another server on port 25. 
>That tells me those are probably safe submissions - even if they are from 
>overseas IPs. Am I thinking correctly?






>
> From: Tom Collins 
>To: vchkpw@inter7.com 
>Sent: Wednesday, March 5, 2014 12:02 AM
>Subject: Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp
> 
>
>
>vchkpw-submission is on port 587, and is typically used for emai clients 
>relaying mail.  It's often set up to require authentication.
>
>
>vchkpw-smtp is on port 25, and can be used for email clients to relay mail, or 
>by other servers delivering mail to your server.
>
>
>-Tom
>
>
>On Mar 4, 2014, at 9:41 PM, LHTek wrote:
>
>In the /var/log/maillog file what is the difference between these 2 entries 
>(vchkpw-submission, vchkpw-smtp)?
>>
>>
>>example:
>>Mar  4 17:27:03 michael vpopmail[14701]: vchkpw-submission: (PLAIN) login 
>>success t...@domain.com:64.185.3.238
>>
>>Mar  4 10:54:42 michael vpopmail[29027]: vchkpw-smtp: (PLAIN) login success 
>>t...@domain.com:64.57.239.114
>>
>>
>>
>>
>
 
>
>

!DSPAM:5316c7aa34265248780387!

[vchkpw] [SPAM] Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp

[FBBE -- INTERNET]

Cher Client,

Nous avons bien reçu votre e-mail et nous vous en remercions. Nos 
collaborateurs le traiteront aussi rapidement que possible.

Attention : ceci est une réponse automatique. Vous ne pouvez donc pas y 
répondre.

Veuillez agréer nos salutations distinguées. 

BNP Paribas Fortis SA
T : +32(0)2 762 20 00
Montagne du Parc 3, 1QA5E, 1000 Bruxelles | www.bnpparibasfortis.be



Geachte klant,

Wij hebben uw e-mail goed ontvangen, waarvoor dank. Onze medewerkers zullen uw 
vraag zo snel mogelijk beantwoorden.

Opgelet : dit is een automatisch bericht. Hierop kan u geen antwoord versturen.

Met vriendelijke groeten,

BNP Paribas Fortis NV
T : +32(0)2 762 60 00
Warandeberg 3, 1QA5E, 1000 Brussel | www.bnpparibasfortis.be



Dear customer,

We hereby acknowledge receipt of your e-mail. Thank you. Our staff will answer 
your query as soon as possible.

Careful: This is an automatic message. Please do not reply.

Yours sincerely,

BNP Paribas Fortis SA/NV
T : +32(0)2 261 11 11
Warandeberg 3, 1QA5E, 1000 Brussels | www.bnpparibasfortis.be



Sehr geehrte Kundin, sehr geehrter Kunde,

Wir danken Ihnen für Ihre E-Mail. Unsere Mitarbeiter werden Ihnen so schnell 
wie möglich antworten.

Achtung: dies ist eine automatische Nachricht. Sie können sie folglich nicht 
beantworten.

Freundliche Grüße

BNP Paribas Fortis SA/NV
T : +32(0)2 261 11 11
Warandeberg 3, 1QA5E, 1000 Brussel | www.bnpparibasfortis.be

- Original Message -
From: Tom Collins 
Sent: Tuesday, March 4, 2014 10:02:12 PM GMT-08:00
Subject: Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp

vchkpw-submission is on port 587, and is typically used for emai clients 
relaying mail.  It's often set up to require authentication.

vchkpw-smtp is on port 25, and can be used for email clients to relay mail, or 
by other servers delivering mail to your server.

-Tom


On Mar 4, 2014, at 9:41 PM, LHTek wrote:

> In the /var/log/maillog file what is the difference between these 2 entries 
> (vchkpw-submission, vchkpw-smtp)?
> 
> example:
> Mar  4 17:27:03 michael vpopmail[14701]: vchkpw-submission: (PLAIN) login 
> success t...@domain.com:64.185.3.238
> Mar  4 10:54:42 michael vpopmail[29027]: vchkpw-smtp: (PLAIN) login success 
> t...@domain.com:64.57.239.114
> 
> 
> 




==
BNP Paribas Fortis disclaimer:
http://www.bnpparibasfortis.com/e-mail-disclaimer.html
 
BNP Paribas Fortis privacy policy:
http://www.bnpparibasfortis.com/privacy-policy.html
 
==


!DSPAM:5316be7c34261148094982!

[vchkpw] [SPAM] Re: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp

[FBBE -- INTERNET]

Cher Client,

Nous avons bien reçu votre e-mail et nous vous en remercions. Nos 
collaborateurs le traiteront aussi rapidement que possible.

Attention : ceci est une réponse automatique. Vous ne pouvez donc pas y 
répondre.

Veuillez agréer nos salutations distinguées. 

BNP Paribas Fortis SA
T : +32(0)2 762 20 00
Montagne du Parc 3, 1QA5E, 1000 Bruxelles | www.bnpparibasfortis.be



Geachte klant,

Wij hebben uw e-mail goed ontvangen, waarvoor dank. Onze medewerkers zullen uw 
vraag zo snel mogelijk beantwoorden.

Opgelet : dit is een automatisch bericht. Hierop kan u geen antwoord versturen.

Met vriendelijke groeten,

BNP Paribas Fortis NV
T : +32(0)2 762 60 00
Warandeberg 3, 1QA5E, 1000 Brussel | www.bnpparibasfortis.be



Dear customer,

We hereby acknowledge receipt of your e-mail. Thank you. Our staff will answer 
your query as soon as possible.

Careful: This is an automatic message. Please do not reply.

Yours sincerely,

BNP Paribas Fortis SA/NV
T : +32(0)2 261 11 11
Warandeberg 3, 1QA5E, 1000 Brussels | www.bnpparibasfortis.be



Sehr geehrte Kundin, sehr geehrter Kunde,

Wir danken Ihnen für Ihre E-Mail. Unsere Mitarbeiter werden Ihnen so schnell 
wie möglich antworten.

Achtung: dies ist eine automatische Nachricht. Sie können sie folglich nicht 
beantworten.

Freundliche Grüße

BNP Paribas Fortis SA/NV
T : +32(0)2 261 11 11
Warandeberg 3, 1QA5E, 1000 Brussel | www.bnpparibasfortis.be

- Original Message -
From: LHTek 
Sent: Tuesday, March 4, 2014 9:41:18 PM GMT-08:00
Subject: [vchkpw] Qmail maillog vchkpw-submission vs vchkpw-smtp

In the /var/log/maillog file what is the difference between these 2 entries 
(vchkpw-submission, vchkpw-smtp)?

example:
Mar  4 17:27:03 michael vpopmail[14701]: vchkpw-submission: (PLAIN) login 
success t...@domain.com:64.185.3.238

Mar  4 10:54:42 michael vpopmail[29027]: vchkpw-smtp: (PLAIN) login success 
t...@domain.com:64.57.239.114


==
BNP Paribas Fortis disclaimer:
http://www.bnpparibasfortis.com/e-mail-disclaimer.html
 
BNP Paribas Fortis privacy policy:
http://www.bnpparibasfortis.com/privacy-policy.html
 
==


!DSPAM:5316ba7434262017919841!

[vchkpw] [SPAM] Bug in maildirquota.c

[Simone Lazzaris]

Hi everybody.

I've been hit by a bug in vdelivermail (in maildirquota.c, precisely), and I 
want to share the
resolution I've found.


I've recently upgraded to vpopmail 5.4.33, and we experienced that occasionally 
(once o twice a day) vdelivermail starts looping, eating all the CPU.

An strace on the offending instance resulted in:
read(5, 0xf5e4317, 2963227893)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4316, 2963227894)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4315, 2963227895)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4314, 2963227896)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4313, 2963227897)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4312, 2963227898)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4311, 2963227899)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4310, 2963227900)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e430f, 2963227901)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e430e, 2963227902)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e430d, 2963227903)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e430c, 2963227904)  = -1 EINVAL (Invalid argument)
...
...

The file descriptor number 5 of that process is pointing at the maildirsize 
file of the mailbox, and is marked as "deleted" in /proc//fd

We store the mail in a NetApp NFS share, without locking for performance 
reasons, and I think I've found the problem:
the file is deleted by someone else while vdelivermail is reading it.

In maildirquota.c, function maildirsize_read, there is a while loop that reads:
while (l)
{
n=read(f, p, l);
if (n < 0)
{

But n is defined as a unsigned int (64 bit) , so even if "read" returns a 
negative value (error) the "if" is never trigged.

So I've made this patch:
--- maildirquota.c.orig 2014-01-31 12:21:22.0 +0100
+++ maildirquota.c  2014-01-31 12:08:47.0 +0100
@@ -337,7 +337,6 @@
  int f;
  char *p;
  unsigned l;
- storage_t n;
  int first;
  int ret = 0;
 
@@ -360,15 +359,16 @@
 
while (l)
{
-   n=read(f, p, l);
-   if (n < 0)
+   ssize_t nr;
+   nr=read(f, p, l);
+   if (nr < 0)
{
close(f);
return (-1);
}
-   if (n == 0) break;
-   p += n;
-   l -= n;
+   if (nr == 0)break;
+   p += nr;
+   l -= nr;
}
if (l == 0 || ret)  /* maildir too big */
{

which fixes the problem.


Any chance to incorporate the fix in the next version ?


Thanks


-- 
Simone Lazzaris
QCom S.p.A.

!DSPAM:52eb8b0234261033718879!

[vchkpw] [SPAM] Bug in maildirquota.c

[Simone Lazzaris]

Hi everybody.

I've been hit by a bug in vdelivermail (in maildirquota.c, precisely), and I 
want to share the
resolution I've found.


I've recently upgraded to vpopmail 5.4.33, and we experienced that occasionally 
(once o twice a day) vdelivermail starts looping, eating all the CPU.

An strace on the offending instance resulted in:
read(5, 0xf5e4317, 2963227893)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4316, 2963227894)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4315, 2963227895)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4314, 2963227896)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4313, 2963227897)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4312, 2963227898)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4311, 2963227899)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e4310, 2963227900)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e430f, 2963227901)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e430e, 2963227902)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e430d, 2963227903)  = -1 EINVAL (Invalid argument)
read(5, 0xf5e430c, 2963227904)  = -1 EINVAL (Invalid argument)
...
...

The file descriptor number 5 of that process is pointing at the maildirsize 
file of the mailbox, and is marked as "deleted" in /proc//fd

We store the mail in a NetApp NFS share, without locking for performance 
reasons, and I think I've found the problem:
the file is deleted by someone else while vdelivermail is reading it.

In maildirquota.c, function maildirsize_read, there is a while loop that reads:
while (l)
{
n=read(f, p, l);
if (n < 0)
{

But n is defined as a unsigned int (64 bit) , so even if "read" returns a 
negative value (error) the "if" is never trigged.

So I've made this patch:
--- maildirquota.c.orig 2014-01-31 12:21:22.0 +0100
+++ maildirquota.c  2014-01-31 12:08:47.0 +0100
@@ -337,7 +337,6 @@
  int f;
  char *p;
  unsigned l;
- storage_t n;
  int first;
  int ret = 0;
 
@@ -360,15 +359,16 @@
 
while (l)
{
-   n=read(f, p, l);
-   if (n < 0)
+   ssize_t nr;
+   nr=read(f, p, l);
+   if (nr < 0)
{
close(f);
return (-1);
}
-   if (n == 0) break;
-   p += n;
-   l -= n;
+   if (nr == 0)break;
+   p += nr;
+   l -= nr;
}
if (l == 0 || ret)  /* maildir too big */
{

which fixes the problem.


Any chance to incorporate the fix in the next version ?


Thanks


-- 
Simone Lazzaris
QCom S.p.A.

!DSPAM:52eb8a1334261024417156!

Re: [vchkpw] [SPAM] Re: vusaged compile error

[Marcello Lupo]

Hi Eric,

i have it under:

libvpopmail_a-vpopmail.o:
U vauth_getpw
libvpopmail_a-vauth.o:
0caa T vauth_getpw
libvpopmail_a-vutil.o:
U vauth_getpw

So i think it is ok.
Thank you
Bye
Marcello


Il giorno 14/dic/2013, alle ore 03:01, Eric Shubert  ha 
scritto:

> On 12/13/2013 04:31 PM, Marcello Lupo wrote:
>> Hi,
>> I have all correct I think.
>> 
>> /home/vpopmail/etc/lib_deps contains:
>> 
>> -L/home/vpopmail/lib -lvpopmail -Xlinker -R -Xlinker /usr/lib/mysql 
>> -L/usr/lib/mysql  -lmysqlclient -lz -lm -lcrypt
>> 
>> So it is correct.
>> 
>> If you see in my log:
>> 
>> checking for ev.h... yes
>> checking for ev_loop_new in -lev... yes
>> checking vpopmail.h usability... yes
>> checking vpopmail.h presence... yes
>> checking for vpopmail.h... yes
>> checking vauth.h usability... yes
>> checking vauth.h presence... yes
>> checking for vauth.h... yes
>> checking for vauth_getpw in -lvpopmail... no
>> checking for vauth_getall in -lvpopmail... no
>> checking for get_domain_entries in -lvpopmail... no
>> checking for client_query_quick in -lvpopmail... yes
>> configure: error: No vauth_getpw in libvpopmail
>> 
>> The line before the error is "checking for client_query_quick in -lvpopmail… 
>> yes” so the configure found correctly the library. I think we have to focus 
>> on the way the check for vauth_getpw is done or x86_64 or ubuntu 
>> distribution issue.
>> 
>> I tried to do with the default ./configure (without any option) and the 
>> result is the same.
>> 
>> Thank you for your time.
>> Bye
>> Marcello
> 
> Sorry I didn't notice that earlier Marcello. You're correct, it is apparently 
> finding a vpopmail library.
> 
> If you "nm libvpopmail.a | less", do you find/see the missing vauth_ 
> functions? I show them under both the libvpopmail_a-vpopmail.o: and 
> libvpopmail_a-vauth.o: sections. If you don't see them then there's a problem 
> with your make of libvpopmail.a, as you suspect. If you do see them, then it 
> appears that your libvpopmail.a isn't being picked up for some reason (the 
> lib_deps file is silently not being found).
> 
> Which is it?
> 
> -- 
> -Eric 'shubes'
> 
> 
> 
> 


!DSPAM:52ac2da134269935620071!

Re: [vchkpw] [SPAM] Re: vusaged compile error

[Marcello Lupo]

Hi,
I have all correct I think.

/home/vpopmail/etc/lib_deps contains:

-L/home/vpopmail/lib -lvpopmail -Xlinker -R -Xlinker /usr/lib/mysql 
-L/usr/lib/mysql  -lmysqlclient -lz -lm -lcrypt

So it is correct.

If you see in my log:

checking for ev.h... yes
checking for ev_loop_new in -lev... yes
checking vpopmail.h usability... yes
checking vpopmail.h presence... yes
checking for vpopmail.h... yes
checking vauth.h usability... yes
checking vauth.h presence... yes
checking for vauth.h... yes
checking for vauth_getpw in -lvpopmail... no
checking for vauth_getall in -lvpopmail... no
checking for get_domain_entries in -lvpopmail... no
checking for client_query_quick in -lvpopmail... yes
configure: error: No vauth_getpw in libvpopmail

The line before the error is "checking for client_query_quick in -lvpopmail… 
yes” so the configure found correctly the library. I think we have to focus on 
the way the check for vauth_getpw is done or x86_64 or ubuntu distribution 
issue.

I tried to do with the default ./configure (without any option) and the result 
is the same.

Thank you for your time.
Bye
Marcello

Il giorno 13/dic/2013, alle ore 23:47, Eric Shubert  ha 
scritto:

> On 12/13/2013 03:04 PM, Eric Shubert wrote:
>> Well, I think I know why my build fails, as I've patched vpopmail to
>> alter the location of the includes and lib directories.
>> 
>> /home/vpopmail/etc (or /etc/vpopmail in my case) should have an
>> include_deps and a lib_deps file.
>> 
>> What do you have in /home/vpopmail/etc/lib_deps ?
>> The first -L option there should be where your libvpopmail.a resides.
>> 
>> HTH.
>> 
> 
> vusaged builds fine for me now.
> Check your lib_deps file.
> 
> -- 
> -Eric 'shubes'
> 
> 
> 
> 


!DSPAM:52ab98de34261115181404!

Re: [vchkpw] [SPAM] Re: vusaged compile error

[Remo Mattei]

One more thing, I am looking at my compile location and I do have it, I do get 
a shared lib but I am not using it on my server. 


Anyhow, I will check and let you know. 

Ciao
-- 
Remo Mattei


On December 13, 2013 at 12:21:39, Marcello Lupo (ml...@itspecialist.it) wrote:

vusaged

!DSPAM:52ab6e0f34263773815312!

Re: [vchkpw] [SPAM] Re: vusaged compile error

[Remo Mattei]

Hi Marcello, 
I am looking at my installation and I do not have vusaged are you sure you are 
using 5.4.33?

Ciao
-- 
Remo Mattei


On December 13, 2013 at 12:21:39, Marcello Lupo (ml...@itspecialist.it) wrote:

vusaged

!DSPAM:52ab6d5c34264660412975!

Re: [vchkpw] [SPAM] Re: vusaged compile error

[Marcello Lupo]

Hi,
Thank you.

I tried in vpopmail-5.4.33 dir:

make distclean
autoreconf
automake
autoconf

./configure --enable-tcpserver-file=/home/vpopmail/etc/tcp.smtp  \
--disable-roaming-users \
--enable-onchange-script \
--enable-auth-module=mysql \
--enable-logging=p \
--disable-mysql-limits \
--enable-valias \
--disable-clear-passwd \
--enable-sql-logging \
--enable-auth-logging \
--enable-qmail-newu=/var/qmail/bin/qmail-newu \
--enable-qmail-inject=/var/qmail/bin/qmail-inject \
--enable-qmail-newmrh=/var/qmail/bin/qmail-newmrh

make
make install-strip
ldconfig

All compiled fine and installed.
When compile vusaged i get the same error both with or without the export 
LDFLAGS='-ldl’ command.
Other hints?
Thank you
Bye
Marcello

Il giorno 13/dic/2013, alle ore 20:11, Eric Shubert  ha 
scritto:

> For your reference, here's the .spec file I'm using for the QMailToaster 
> version of vpopmail:
> https://github.com/QMailToaster/vpopmail/blob/master/vpopmail.spec
> This is building ok on CentOS 5 & 6, and both x86_64 and i386 arch's.
> 
> You might try running autoreconf && automake && autoconf before running the 
> configure script, and see what that does for you.
> 
> HTH.
> -- 
> -Eric 'shubes'
> 
> On 12/13/2013 11:14 AM, Marcello Lupo wrote:
>> Hi,
>> yes all is correct:
>> 
>> the only libvpopmail.a found are:
>> 
>> /usr/src/vpopmail-5.4.33/libvpopmail.a
>> /home/vpopmail/lib/libvpopmail.a
>> 
>> and are identical files.
>> 
>> I think the issue can reside in the way the configure script make the check 
>> of vauth_getpw in the libvpopmail or depending on some configure option i 
>> used.
>> I tried to dig a little bit in the sources but was not able to understand so 
>> much. I’m not so skilled coder.
>> Thank you if you have any other suggestion.
>> Eventually i can give you access to the system of you need it. I really need 
>> to compile it otherwise the server will never start.
>> Thank you
>> Bye
>> Marcello
>> 
>> Il giorno 13/dic/2013, alle ore 18:58, Eric Shubert  ha 
>> scritto:
>> 
>>> Is the system finding the correct libvpopmail?
>>> Perhaps search the entire system for all libvpopmail files to be sure 
>>> there's not another one being picked up inadvertently?
>>> --
>>> -Eric 'shubes'
>>> 
>>> On 12/13/2013 04:38 AM, Marcello Lupo wrote:
 Hello,
 Yes i have done it but it is not woking.
 Anyway the make distclean is useless in the vusaged directory. It doesn’t 
 produce any effect since the Makefile have still to be created because 
 ./configure is not working.
 The libvpopmail.a is correctly found and loaded in the LDCONFIG.
 Any hint?
 Thank you
 Bye
 Marcello
 
 Il giorno 12/dic/2013, alle ore 19:09, Eric Shubert  ha 
 scritto:
 
> Have you done as Matt suggested?
> 
> # make distclean
> # export LDFLAGS='-ldl'
> # ./configure && make.
> 
> On 12/12/2013 10:16 AM, Marcello Lupo wrote:
>> Hello,
>> any news on this issue?
>> I have exactly this issue on ubuntu server 12.04 LTS x86_64 .
>> 
>> checking for vauth_getpw in -lvpopmail... no
>> checking for vauth_getall in -lvpopmail... no
>> checking for get_domain_entries in -lvpopmail... no
>> checking for client_query_quick in -lvpopmail... yes
>> configure: error: No vauth_getpw in libvpopmail
>> 
>> I tried vpopmail version 5.4.32 and 5.4.33 .
>> 
>> This are the options:
>> 
>> ./configure --enable-tcpserver-file=/home/vpopmail/etc/tcp.smtp \
>> --disable-roaming-users \
>> --enable-onchange-script \
>> --enable-auth-module=mysql \
>> --enable-logging=p \
>> --enable-mysql-limits \
>> --enable-valias \
>> --disable-clear-passwd \
>> --enable-sql-logging \
>> --enable-auth-logging \
>> --enable-qmail-newu=/var/qmail/bin/qmail-newu \
>> --enable-qmail-inject=/var/qmail/bin/qmail-inject \
>> --enable-qmail-newmrh=/var/qmail/bin/qmail-newmrh
>> 
>> I already tried all the solutions suggested in this thread with no 
>> success.
>> 
>> Thank you all for any help.
>> Bye
>> Marcello
>> 
>> 
>> Il giorno 05/mar/2013, alle ore 17:55, Remo Mattei  ha 
>> scritto:
>> 
>>> which version of vpop?
>>> 
>>> On Mar 5, 2013, at 07:45 , Franko Fang  wrote:
>>> 
 Dear Matt:
 
 Matt Brookings  inter7.com> writes:
 
> 
> 
> On 01/24/2011 10:22 AM, Qmail List wrote:
>> Hi,
>> 
>> For Vpopmail, i did this.
>> 
>> ./configure --enable-logging=v \
>> make
>> make install-strip
>> 
>> Vpopmail config.log
>> http://pastebin.com/5xZT1EiH
>> 
>> Vpopmail config.h
>> http://pastebin.com/t6FQzp0U
>> 
>> For  Vusaged, i did this.
>> ./configure
>> make
>> 
>> Vusaged config.log
>> http://pastebin.com/78MsKPjh

Re: [vchkpw] [SPAM] Re: vusaged compile error

[Marcello Lupo]

Hi,
yes all is correct:

the only libvpopmail.a found are: 

/usr/src/vpopmail-5.4.33/libvpopmail.a
/home/vpopmail/lib/libvpopmail.a

and are identical files.

I think the issue can reside in the way the configure script make the check of 
vauth_getpw in the libvpopmail or depending on some configure option i used.
I tried to dig a little bit in the sources but was not able to understand so 
much. I’m not so skilled coder.
Thank you if you have any other suggestion.
Eventually i can give you access to the system of you need it. I really need to 
compile it otherwise the server will never start.
Thank you
Bye
Marcello

Il giorno 13/dic/2013, alle ore 18:58, Eric Shubert  ha 
scritto:

> Is the system finding the correct libvpopmail?
> Perhaps search the entire system for all libvpopmail files to be sure there's 
> not another one being picked up inadvertently?
> -- 
> -Eric 'shubes'
> 
> On 12/13/2013 04:38 AM, Marcello Lupo wrote:
>> Hello,
>> Yes i have done it but it is not woking.
>> Anyway the make distclean is useless in the vusaged directory. It doesn’t 
>> produce any effect since the Makefile have still to be created because 
>> ./configure is not working.
>> The libvpopmail.a is correctly found and loaded in the LDCONFIG.
>> Any hint?
>> Thank you
>> Bye
>> Marcello
>> 
>> Il giorno 12/dic/2013, alle ore 19:09, Eric Shubert  ha 
>> scritto:
>> 
>>> Have you done as Matt suggested?
>>> 
>>> # make distclean
>>> # export LDFLAGS='-ldl'
>>> # ./configure && make.
>>> 
>>> On 12/12/2013 10:16 AM, Marcello Lupo wrote:
 Hello,
 any news on this issue?
 I have exactly this issue on ubuntu server 12.04 LTS x86_64 .
 
 checking for vauth_getpw in -lvpopmail... no
 checking for vauth_getall in -lvpopmail... no
 checking for get_domain_entries in -lvpopmail... no
 checking for client_query_quick in -lvpopmail... yes
 configure: error: No vauth_getpw in libvpopmail
 
 I tried vpopmail version 5.4.32 and 5.4.33 .
 
 This are the options:
 
 ./configure --enable-tcpserver-file=/home/vpopmail/etc/tcp.smtp \
 --disable-roaming-users \
 --enable-onchange-script \
 --enable-auth-module=mysql \
 --enable-logging=p \
 --enable-mysql-limits \
 --enable-valias \
 --disable-clear-passwd \
 --enable-sql-logging \
 --enable-auth-logging \
 --enable-qmail-newu=/var/qmail/bin/qmail-newu \
 --enable-qmail-inject=/var/qmail/bin/qmail-inject \
 --enable-qmail-newmrh=/var/qmail/bin/qmail-newmrh
 
 I already tried all the solutions suggested in this thread with no success.
 
 Thank you all for any help.
 Bye
 Marcello
 
 
 Il giorno 05/mar/2013, alle ore 17:55, Remo Mattei  ha 
 scritto:
 
> which version of vpop?
> 
> On Mar 5, 2013, at 07:45 , Franko Fang  wrote:
> 
>> Dear Matt:
>> 
>> Matt Brookings  inter7.com> writes:
>> 
>>> 
>>> 
>>> On 01/24/2011 10:22 AM, Qmail List wrote:
 Hi,
 
 For Vpopmail, i did this.
 
 ./configure --enable-logging=v \
 make
 make install-strip
 
 Vpopmail config.log
 http://pastebin.com/5xZT1EiH
 
 Vpopmail config.h
 http://pastebin.com/t6FQzp0U
 
 For  Vusaged, i did this.
 ./configure
 make
 
 Vusaged config.log
 http://pastebin.com/78MsKPjh
 
 Vusaged config.h
 http://pastebin.com/k9kk7Zff
>>> 
>>> In the vusaged source directory, run "make clean", then "export
>>> LDFLAGS='-ldl'", then try to build again.
>> 
>> --I did the same compile on Ubuntu 12.04 32bit system,
>> and the error still exists.
>> checking for vauth_getpw in -lvpopmail... no
>> checking for vauth_getall in -lvpopmail... no
>> checking for get_domain_entries in -lvpopmail... no
>> checking for client_query_quick in -lvpopmail... yes
>> configure: error: No vauth_getpw in libvpopmail
>> 
>> --Any ideas for my issue?
>> 
>> Best Regards,
>> Franko Fang
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 
> 
> 
> 
 
 
 
 
>>> 
>>> 
>>> --
>>> -Eric 'shubes'
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
> 
> 
> 
> 
> 
> 


!DSPAM:52ab4e9d34261008010253!

Re: [vchkpw] [SPAM] Re: vusaged compile error

[Marcello Lupo]

Hello,
Yes i have done it but it is not woking.
Anyway the make distclean is useless in the vusaged directory. It doesn’t 
produce any effect since the Makefile have still to be created because 
./configure is not working.
The libvpopmail.a is correctly found and loaded in the LDCONFIG.
Any hint?
Thank you
Bye
Marcello

Il giorno 12/dic/2013, alle ore 19:09, Eric Shubert  ha 
scritto:

> Have you done as Matt suggested?
> 
> # make distclean
> # export LDFLAGS='-ldl'
> # ./configure && make.
> 
> On 12/12/2013 10:16 AM, Marcello Lupo wrote:
>> Hello,
>> any news on this issue?
>> I have exactly this issue on ubuntu server 12.04 LTS x86_64 .
>> 
>> checking for vauth_getpw in -lvpopmail... no
>> checking for vauth_getall in -lvpopmail... no
>> checking for get_domain_entries in -lvpopmail... no
>> checking for client_query_quick in -lvpopmail... yes
>> configure: error: No vauth_getpw in libvpopmail
>> 
>> I tried vpopmail version 5.4.32 and 5.4.33 .
>> 
>> This are the options:
>> 
>> ./configure --enable-tcpserver-file=/home/vpopmail/etc/tcp.smtp \
>> --disable-roaming-users \
>> --enable-onchange-script \
>> --enable-auth-module=mysql \
>> --enable-logging=p \
>> --enable-mysql-limits \
>> --enable-valias \
>> --disable-clear-passwd \
>> --enable-sql-logging \
>> --enable-auth-logging \
>> --enable-qmail-newu=/var/qmail/bin/qmail-newu \
>> --enable-qmail-inject=/var/qmail/bin/qmail-inject \
>> --enable-qmail-newmrh=/var/qmail/bin/qmail-newmrh
>> 
>> I already tried all the solutions suggested in this thread with no success.
>> 
>> Thank you all for any help.
>> Bye
>> Marcello
>> 
>> 
>> Il giorno 05/mar/2013, alle ore 17:55, Remo Mattei  ha 
>> scritto:
>> 
>>> which version of vpop?
>>> 
>>> On Mar 5, 2013, at 07:45 , Franko Fang  wrote:
>>> 
 Dear Matt:
 
 Matt Brookings  inter7.com> writes:
 
> 
> 
> On 01/24/2011 10:22 AM, Qmail List wrote:
>> Hi,
>> 
>> For Vpopmail, i did this.
>> 
>> ./configure --enable-logging=v \
>> make
>> make install-strip
>> 
>> Vpopmail config.log
>> http://pastebin.com/5xZT1EiH
>> 
>> Vpopmail config.h
>> http://pastebin.com/t6FQzp0U
>> 
>> For  Vusaged, i did this.
>> ./configure
>> make
>> 
>> Vusaged config.log
>> http://pastebin.com/78MsKPjh
>> 
>> Vusaged config.h
>> http://pastebin.com/k9kk7Zff
> 
> In the vusaged source directory, run "make clean", then "export
> LDFLAGS='-ldl'", then try to build again.
 
 --I did the same compile on Ubuntu 12.04 32bit system,
 and the error still exists.
 checking for vauth_getpw in -lvpopmail... no
 checking for vauth_getall in -lvpopmail... no
 checking for get_domain_entries in -lvpopmail... no
 checking for client_query_quick in -lvpopmail... yes
 configure: error: No vauth_getpw in libvpopmail
 
 --Any ideas for my issue?
 
 Best Regards,
 Franko Fang
 
 
 
 
 
 
 
 
 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
> 
> 
> -- 
> -Eric 'shubes'
> 
> 
> 
> 


!DSPAM:52aaf19734261071129162!

Re: [vchkpw] [SPAM] Re: vusaged compile error

[Marcello Lupo]

Hello,
any news on this issue?
I have exactly this issue on ubuntu server 12.04 LTS x86_64 .

checking for vauth_getpw in -lvpopmail... no
checking for vauth_getall in -lvpopmail... no
checking for get_domain_entries in -lvpopmail... no
checking for client_query_quick in -lvpopmail... yes
configure: error: No vauth_getpw in libvpopmail

I tried vpopmail version 5.4.32 and 5.4.33 .

This are the options:

./configure --enable-tcpserver-file=/home/vpopmail/etc/tcp.smtp \
--disable-roaming-users \
--enable-onchange-script \
--enable-auth-module=mysql \
--enable-logging=p \
--enable-mysql-limits \
--enable-valias \
--disable-clear-passwd \
--enable-sql-logging \
--enable-auth-logging \
--enable-qmail-newu=/var/qmail/bin/qmail-newu \
--enable-qmail-inject=/var/qmail/bin/qmail-inject \
--enable-qmail-newmrh=/var/qmail/bin/qmail-newmrh

I already tried all the solutions suggested in this thread with no success.

Thank you all for any help.
Bye
Marcello


Il giorno 05/mar/2013, alle ore 17:55, Remo Mattei  ha scritto:

> which version of vpop? 
> 
> On Mar 5, 2013, at 07:45 , Franko Fang  wrote:
> 
>> Dear Matt:
>> 
>> Matt Brookings  inter7.com> writes:
>> 
>>> 
>>> 
>>> On 01/24/2011 10:22 AM, Qmail List wrote:
 Hi,
 
 For Vpopmail, i did this.
 
 ./configure --enable-logging=v \
 make
 make install-strip
 
 Vpopmail config.log
 http://pastebin.com/5xZT1EiH
 
 Vpopmail config.h
 http://pastebin.com/t6FQzp0U
 
 For  Vusaged, i did this.
 ./configure
 make
 
 Vusaged config.log
 http://pastebin.com/78MsKPjh
 
 Vusaged config.h
 http://pastebin.com/k9kk7Zff
>>> 
>>> In the vusaged source directory, run "make clean", then "export
>>> LDFLAGS='-ldl'", then try to build again.
>> 
>> --I did the same compile on Ubuntu 12.04 32bit system, 
>> and the error still exists.
>> checking for vauth_getpw in -lvpopmail... no
>> checking for vauth_getall in -lvpopmail... no
>> checking for get_domain_entries in -lvpopmail... no
>> checking for client_query_quick in -lvpopmail... yes
>> configure: error: No vauth_getpw in libvpopmail
>> 
>> --Any ideas for my issue?
>> 
>> Best Regards,
>> Franko Fang
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 
> 
> 
> 


!DSPAM:52a9ef5634261418742760!

Re: [vchkpw] [SPAM] 5GB quota, limitations?

[Charles Sprickman]

Replying to myself…

http://comments.gmane.org/gmane.mail.vpopmail/20650

Looks like I need 5.4.33.  Built it with most of the strncpy and other nice 
patches, compiled clean, and I'll do some testing tomorrow.  If it holds up, 
I'll submit my updated port to the FreeBSD folks and see if they'll take it and 
bump their version up to 5.4.33.


On Dec 11, 2013, at 10:42 PM, Charles Sprickman wrote:

> Where should I be digging around to see where large quotas fall apart in 
> vpopmail?
> 
> I'm on 5.4.32 (long story, but I like the extra security cleanup in the 
> FreeBSD ports version) and while 5GB+ quotas seem to work fine when dealing 
> with individual user accounts (delivery, displaying quota, maildirsize), it 
> seems like the domain-related limits start to fall apart.
> 
> Something like "vmoddomlimits -q5000m example.com" results in this output:
> 
> vmoddomlimits -S eylward.com
> […]
> Domain Quota: 0 MB
> Default User Quota: 1073741824 bytes <<<---
> Max Domain Messages: 0
> Default Max Messages per User: 0
> 
> In the database (limits table), I have this value as well:  1073741824
> 
> I made sure the db can take a larger value.  If I manually set the 
> "defaultquota" column in the db to "5368709120", adding a new user results in 
> a user with the same 1073741824 quota.  Manually upping that user to 5GB with 
> vmoduser works fine.
> 
> I also noted that when I had the default set to 3GB in vlimits.default, all 
> those domains created had a defaultquota (displayed with vmoddomlimits and in 
> the db itself) of -1073741824.
> 
> Removing the default entry from vlimits.default does not change this behavior 
> either (thought I'd check it).
> 
> Any ideas?  Anyone else running more than 2GB quotas?
> 
> We're looking at 5GB as a target, I've been ramping ours up 1GB every few 
> weeks.  Noticed oddness with new domains at the 3GB mark.
> 
> Thanks,
> 
> Charles
> 
> 


!DSPAM:52a9812234264376319608!

[vchkpw] [SPAM] 5GB quota, limitations?

[Charles Sprickman]

Where should I be digging around to see where large quotas fall apart in 
vpopmail?

I'm on 5.4.32 (long story, but I like the extra security cleanup in the FreeBSD 
ports version) and while 5GB+ quotas seem to work fine when dealing with 
individual user accounts (delivery, displaying quota, maildirsize), it seems 
like the domain-related limits start to fall apart.

Something like "vmoddomlimits -q5000m example.com" results in this output:

vmoddomlimits -S eylward.com
[…]
Domain Quota: 0 MB
Default User Quota: 1073741824 bytes <<<---
Max Domain Messages: 0
Default Max Messages per User: 0

In the database (limits table), I have this value as well:  1073741824

I made sure the db can take a larger value.  If I manually set the 
"defaultquota" column in the db to "5368709120", adding a new user results in a 
user with the same 1073741824 quota.  Manually upping that user to 5GB with 
vmoduser works fine.

I also noted that when I had the default set to 3GB in vlimits.default, all 
those domains created had a defaultquota (displayed with vmoddomlimits and in 
the db itself) of -1073741824.

Removing the default entry from vlimits.default does not change this behavior 
either (thought I'd check it).

Any ideas?  Anyone else running more than 2GB quotas?

We're looking at 5GB as a target, I've been ramping ours up 1GB every few 
weeks.  Noticed oddness with new domains at the 3GB mark.

Thanks,

Charles
!DSPAM:52a9309534261110179075!

Re: [vchkpw] [SPAM] Using Dovecot's LDA / spamc and maildrop support

[Alessio Cecchi]

Il 02/10/2013 03:30, Charles Sprickman ha scritto:

Simple question I hope…

What's the recommendation on the vpopmail side on integrating Dovecot's LDA for 
final delivery?

I've seen various suggestions, including just calling it from the user's .qmail 
file.  In that particular case, it's not at all clear to me how other tools 
that would touch that file (like qmailadmin) would be taught to not alter the 
call to dovecot_lda.  I imagine it would get munged everytime a user went to 
setup a vacation message or forward.

Also I'm in the midst of upgrading from 5.4.10 to 5.4.33.  I see that there's 
new support to have vdelivermail handle the call to spamc for tagging, and also 
support to have maildrop handle the filtering.  A few questions regarding this 
setup if vpopmail is configured to use spamc and maildrop:

* Is maildrop always doing the final delivery?
* What's the message flow when a .qmail file is encountered that has a forward?
* What's the message flow when a .qmail file is encountered that's piping to 
maildrop (we have a ton of these on the old system, I assume I'd have to find 
and nuke all of them)?
* Does this limit qmailadmin's abilities at all?
* If using valias, do we filter a message before forwarding offsite?

Hoping the list is still alive, didn't even realize I'm still subscribed here!

Thanks,

Charles




Hi,

I think that a possibile solutions could be a configuration where 
vpopmail is configured to call maildrop and maildrop "sent" the messagge 
to an LMTP server (Postfix) that use dovecot LDA to delivery the email 
in the Maildir. LMTP is fast and can also be used with Dovecot Director, 
Director is needed when you have a shared storage and more than one 
POP/IMAP server.


From the qmail/vpopmail point of view this configuration will be 
transparent.


From the maildrop point of view is necessary find the rigth "script" 
(email -> pipe to LMTP)  and insert in /etc/maildroprc.


Could be an idea?

--
Alessio Cecchi is:
@ ILS -> http://www.linux.it/~alessice/
on LinkedIn -> http://www.linkedin.com/in/alessice
Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/
@ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it

!DSPAM:5255173734261611143367!

[vchkpw] [SPAM] Re: [SPAM] Using Dovecot's LDA / spamc and maildrop support

[Eric Shubert]

On 10/01/2013 06:30 PM, Charles Sprickman wrote:

Simple question I hope…


Some yes, some no. ;)


What's the recommendation on the vpopmail side on integrating Dovecot's LDA for 
final delivery?


I'm not aware of any recommendation per se.

In the QMail-Toaster community (I am the project leader there FWIW), 
we've informally implemented dovecot with vpopmail for imap/pop3, but 
have yet to implement Dovecot's LDA, which will come after formal 
adoption of Dovecot imap/pop3 in the forthcoming QMT release.


So I'm very interested in the best way to replace vdelivermail/maildrop 
with dovecot's Deliver and Pigeonhole. I'm especially looking forward to 
implementing server-side message filtering.



I've seen various suggestions, including just calling it from the user's .qmail 
file.  In that particular case, it's not at all clear to me how other tools 
that would touch that file (like qmailadmin) would be taught to not alter the 
call to dovecot_lda.  I imagine it would get munged everytime a user went to 
setup a vacation message or forward.


I imagine you're correct. qmailadmin, vqadmin et al would need to be 
modified for this. Off hand, I've expected that this will be the method 
used. It might be more suitable (simpler) though to develop a 
vdelivermail replacement which would simply pass the message on to 
Deliver. I really haven't thought about this much.



Also I'm in the midst of upgrading from 5.4.10 to 5.4.33.  I see that there's 
new support to have vdelivermail handle the call to spamc for tagging, and also 
support to have maildrop handle the filtering.  A few questions regarding this 
setup if vpopmail is configured to use spamc and maildrop:


QMT was upgraded from 5.4.17 to 5.4.33 not too long ago. It's not using 
spamc at the delivery stage though.




* Is maildrop always doing the final delivery?


Afaik, yes.


* What's the message flow when a .qmail file is encountered that has a forward?


Forwards are handled in the database now. I'm not sure exactly how that 
works, but I expect that vdelivermail (could be maildrop though) checks 
the database and forwards accordingly by putting the message back into 
the queue with a new recipient. Now that I think of it, I wonder how 
Deliver would handle forwards. Can Deliver handle forwards at all? More 
specifically, vpopmail-type forwards?



* What's the message flow when a .qmail file is encountered that's piping to 
maildrop (we have a ton of these on the old system, I assume I'd have to find 
and nuke all of them)?


This is the standard mechanism in QMT. I'm guessing that maildrop passes 
messages on to vdelivermail. I'm not positive about this though.



* Does this limit qmailadmin's abilities at all?


qmailadmin pretty much controls the .qmail files (again, ttbomk). On a 
side note, I am aware that there's a bug in qmailadmin where if the name 
is changed, a 2nd delivery record is created in the .qmail file causing 
duplicate deliveries. It'd be nice to get this fixed at some point. I 
imagine that there might be a few other bugs in there which need fixing.


I imagine that vqadmin may touch these as well, but I'm not really 
familiar with vqadmin (it was a bit broken on QMT until we upgraded to 
5.4.33).



* If using valias, do we filter a message before forwarding offsite?


I don't know anything about this off hand.


Hoping the list is still alive, didn't even realize I'm still subscribed here!


Yeah, barely. ;)

You might want to consider joining us on the QMT list. Lots of friendly 
help there. :)


Good luck Charles, and please let us know about your endeavors with Deliver.

--
-Eric 'shubes'


!DSPAM:524c18fb34284707794799!

[vchkpw] [SPAM] Using Dovecot's LDA / spamc and maildrop support

[Charles Sprickman]

Simple question I hope…

What's the recommendation on the vpopmail side on integrating Dovecot's LDA for 
final delivery?

I've seen various suggestions, including just calling it from the user's .qmail 
file.  In that particular case, it's not at all clear to me how other tools 
that would touch that file (like qmailadmin) would be taught to not alter the 
call to dovecot_lda.  I imagine it would get munged everytime a user went to 
setup a vacation message or forward.

Also I'm in the midst of upgrading from 5.4.10 to 5.4.33.  I see that there's 
new support to have vdelivermail handle the call to spamc for tagging, and also 
support to have maildrop handle the filtering.  A few questions regarding this 
setup if vpopmail is configured to use spamc and maildrop:

* Is maildrop always doing the final delivery?
* What's the message flow when a .qmail file is encountered that has a forward?
* What's the message flow when a .qmail file is encountered that's piping to 
maildrop (we have a ton of these on the old system, I assume I'd have to find 
and nuke all of them)?
* Does this limit qmailadmin's abilities at all?
* If using valias, do we filter a message before forwarding offsite?

Hoping the list is still alive, didn't even realize I'm still subscribed here!

Thanks,

Charles
!DSPAM:524b4e9034281958284551!

[vchkpw] [SPAM] [suggestion] vdelivermail environment changes

[Laurent Bercot]

 Hello,

 I am installing vpopmail together with dovecot.
 Mail must be delivered to /home/vpopmail/domains///Maildir,
not by vdelivermail itself, but by dovecot-lda (to keep index files updated,
among other things).
 So, I write a /home/vpopmail/domains///.qmail file,
containing simply

 | preline -f dovecot-lda
 
 as the dovecot instructions say.

 But it does not work: mail gets delivered to
/home/vpopmail/domains//Maildir - which is definitely not
what I want if I have more than one user. :)
 I have investigated and found the source of the problem: when
dovecot-lda is run, the virtual user's home directory, contained in
the HOME environment variable, is not
/home/vpopmail/domains// as it should be. It is still
/home/vpopmail/domains/, the value it has when vdelivermail
is executed.

 It makes sense to have HOME=/home/vpopmail/domains/ when
executing vdelivermail, because that's the correct home for the
-@ virtual user from qmail-local's point of view.
However, when vdelivermail processes a dot-qmail file itself in
/home/vpopmail/domains//, it knows what the right
home for @ is, and should adjust HOME accordingly before
running other programs in the qmail-command fashion.

 I am currently modifying HOME myself before executing into
dovecot-lda, in the .qmail file, and it's working perfectly. However,
it would be cleaner if vdelivermail did this itself.

 It would also be a lot cleaner if vdelivermail hid the -
thing under the rug: once qmail-send has been fooled and control has
been given to vdelivermail, the virtualdomains hack is not necessary
anymore, and is only confusing to software run in further .qmail files.
For instance, a qreceipt instruction in a
/home/vpopmail/domains///.qmail file currently has to be:

| qreceipt $EXT@$HOST

But it really should be

| qreceipt $USER@$HOST

like with system users. Also, specific workarounds have to be enabled
to make ezmlm lists work under vpopmail; if vdelivermail was putting
the right environment variables back, ezmlm would work out of the box.

 Please consider this change - along with a new, vpopmail-specific
environment variable so vpopmail-aware applications still know that
the address is virtual and really handled by vpopmail.

 Developer bait: with this change, vdelivermail wouldn't have to perform
MDA duties itself anymore. If it found a user in the vpasswd
database, it could just hand the delivery to qmail-local. :)

 Thank you,

-- 
 Laurent

!DSPAM:5214c8b334256189513643!

[vchkpw] [SPAM] odd problem after OS upgrade

[Jeremy Kister]

I have qmail 1.03 with several patches including qmail-smtpd-auth-0.4.3 
and vpopmail 5.4.33.


After upgrading Debian 6 -> 7, I broke SMTP-AUTH *only* when using 
stunnel for SSL.



When trying to auth over stunnel4, i see:
454 oops, problem with child and I can't auth (#4.3.0)

syslog shows:
Jun 21 23:19:29 s4 vpopmail[3080]: vchkpw-smtps: (PLAIN) login success 
u...@example.com:10.36.87.4


using smtp-auth on port 25 or 587 works fine.

/service/qmail-smtpd-ssl/run:
  http://jeremy.kister.net/tmp/auth/qmail-smtpd-ssl-run
/usr/local/etc/stunnel/smtps.conf:
  http://jeremy.kister.net/tmp/auth/smtps.conf

i modified smtps.conf to use strace like:
exec = /usr/bin/strace
execargs = /usr/bin/strace -ff -o /tmp/vchkpw.dump 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true


the dumps are at:
  http://jeremy.kister.net/tmp/auth/strace/

i tried increasing & just removing softlimit.
i tried recompiling/reinstalling vpopmail

I dont think the problem is with stunnel since the SSL layer is working 
fine.


I'm out of ideas.  More eyes please ?

--

Jeremy Kister
http://jeremy.kister.net./


!DSPAM:51c51fac34131129417734!

Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[Thibault Richard]

You’re right ... and this guide is indeed using old-fashioned software.

As Debian has just released last week-end a new version, I’m currently working 
on a new installation guide with Dovecot

From: Remo Mattei 
Sent: Thursday, May 16, 2013 6:51 PM
To: vchkpw@inter7.com 
Subject: Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain 
directory

HI Thibs,  
looks nice but you are still running courier ops!! So maybe it's a new project 
for you to update to dovecot faster and supported better than courier now. 

Just my 2 cents, 

Remo 

On May 16, 2013, at 08:54 , "Thibault Richard"  wrote:


  My way of doing (I’m the author of http://qmailrocks.thibs.com) is not so bad 



  From: Ron Herzing 
  Sent: Thursday, May 16, 2013 3:49 PM
  To: vchkpw@inter7.com 
  Subject: Re: [vchkpw] [SPAM] Error: Unable to chdir to 
vpopmail/domains/domain directory

  I word of caution. Qmailrocks is not a good way to learn how to install Qmail.



  On Thu, May 16, 2013 at 7:14 AM, swaroop kumar  wrote:


Hi All,


I am switching my mail server from sendmail to qmail, currently installing 
qmail in debian and i am following this link http://qmailrocks.thibs.com/


I Have a problem in creating domains using vpopmail, below is the error 
thrown when i am trying to create a domain.

"Unable to chdir to vpopmail/domains/domain directory"


Can any one suggest me to overcome this, quick response is highly 
appreciated.


Thanks in Advance.


Regards,

Swaroop Kundeti





  -- 
  Ron Herzing
  ron.herz...@gmail.com


 

!DSPAM:5195118b34126731113110!

Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[Remo Mattei]

HI Thibs, 
looks nice but you are still running courier ops!! So maybe it's a new project 
for you to update to dovecot faster and supported better than courier now. 

Just my 2 cents, 

Remo 
 
On May 16, 2013, at 08:54 , "Thibault Richard"  wrote:

> My way of doing (I’m the author of http://qmailrocks.thibs.com) is not so bad 
> 
>  
>  
> From: Ron Herzing
> Sent: Thursday, May 16, 2013 3:49 PM
> To: vchkpw@inter7.com
> Subject: Re: [vchkpw] [SPAM] Error: Unable to chdir to 
> vpopmail/domains/domain directory
>  
> I word of caution. Qmailrocks is not a good way to learn how to install Qmail.
> 
> 
> On Thu, May 16, 2013 at 7:14 AM, swaroop kumar  wrote:
>  
> Hi All,
> 
> I am switching my mail server from sendmail to qmail, currently installing 
> qmail in debian and i am following this link http://qmailrocks.thibs.com/
> 
> I Have a problem in creating domains using vpopmail, below is the error 
> thrown when i am trying to create a domain.
> 
> "Unable to chdir to vpopmail/domains/domain directory"
> 
> Can any one suggest me to overcome this, quick response is highly appreciated.
> 
> Thanks in Advance.
>  
> Regards,
> Swaroop Kundeti
> 
> 
>  
> -- 
> Ron Herzing
> ron.herz...@gmail.com
> 



!DSPAM:51950ee734121639429747!

Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[swaroop kumar]

HI,

I missed "perl-suid" package to install, its actually broken and below is
the output when i am trying to install. Is this package effecting GUI for
not working properly?

Regards,
--
Swaroop Kundeti.


On Thu, May 16, 2013 at 10:08 PM, Thibault Richard  wrote:

>   Hello,
>
> OK I understand now. You didn’t specified in your request that you tried
> from the webinterface
>
> The result of the script is normal at this install step (it verify all the
> steps)
>
> Best Regards
>
> Thibault
>
>  *From:* swaroop kumar 
> *Sent:* Thursday, May 16, 2013 3:51 PM
> *To:* vchkpw@inter7.com
> *Subject:* Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir
> to vpopmail/domains/domain directory
>
>Hello Geeks,
>
> I resolved it by adding www-data to vchkpw group and changed owner and
> group of the apache files to vpopmail:vchkpw earlier it was www-data was
> owner and group. Now i am facing new error "could not update file".
>
> @Thibs
>
> I ran this script "/downloads/scripts/qmr_inst_check" and below is the
> output.
>
> ! Couldn't find /var/qmail/supervise!
> ! /var/qmail/supervise/qmail-send/run is missing
> ...try: cp /downloads/scripts/service-qmail-send-run
> /var/qmail/supervise/qmail-send/run
> ! /service directory is missing
> ! Couldn't find /var/qmail/control/defaultdelivery
> ! DatabaseOwner is incorrect in /etc/clamav/freshclam.conf
> ! LocalSocketGroup is incorrect in /etc/clamav/clamd.conf
> ! User is incorrect in /etc/clamav/clamd.conf
> ! /var/qmail/bin/qmailctl is missing
> ! /usr/bin/qmailctl is missing
> ...try: ln -s /var/qmail/bin/qmailctl /usr/bin
> ! /var/qmail/supervise/qmail-send/run file is missing
> ! /var/qmail/supervise/qmail-send/log/run file is missing
> ! /var/qmail/supervise/qmail-smtpd/run file is missing
> ! /var/qmail/supervise/qmail-smtpd/log/run file is missing
> ! /var/qmail/control/concurrencyincoming is missing
> ...try: echo 30 >/var/qmail/control/concurrencyincoming
> ! /var/log/clamav has wrong owner, should be qscand
> ...try: chown -R qscand:clamav /var/log/clamav
> ! /var/lib/clamav has wrong owner, should be qscand
> ...try: chown -R qscand:clamav /var/lib/clamav
> ! /var/run/clamav has wrong owner, should be qscand
> ...try: chown -R qscand:clamav /var/run/clamav
> ! /service/qmail-send is missing
> ...try: ln -s /var/qmail/service/qmail-send /service/qmail-send
> ! /service/qmail-smtpd is missing
> ...try: ln -s /var/qmail/service/qmail-smtpd /service/qmail-smtpd
> ! /etc/tcp.smtp is missing
> ...try: echo '127.:allow,RELAYCLIENT=""' >>/etc/tcp.smtp
> ! /etc/tcp.smtp.cdb is missing
> ...try: /var/qmail/bin/qmailctl cdb
> ! Alias for root is missing
> ...try: echo me >/var/qmail/alias/.qmail-root
> root@mail:~# /downloads/scripts/qmr_inst_check
> ! Couldn't find /var/qmail/supervise!
> ! /var/qmail/supervise/qmail-send/run is missing
> ...try: cp /downloads/scripts/service-qmail-send-run
> /var/qmail/supervise/qmail-send/run
> ! /service directory is missing
> ! Couldn't find /var/qmail/control/defaultdelivery
> ! DatabaseOwner is incorrect in /etc/clamav/freshclam.conf
> ! LocalSocketGroup is incorrect in /etc/clamav/clamd.conf
> ! User is incorrect in /etc/clamav/clamd.conf
> ! /var/qmail/bin/qmailctl is missing
> ! /usr/bin/qmailctl is missing
> ...try: ln -s /var/qmail/bin/qmailctl /usr/bin
> ! /var/qmail/supervise/qmail-send/run file is missing
> ! /var/qmail/supervise/qmail-send/log/run file is missing
> ! /var/qmail/supervise/qmail-smtpd/run file is missing
> ! /var/qmail/supervise/qmail-smtpd/log/run file is missing
> ! /var/qmail/control/concurrencyincoming is missing
> ...try: echo 30 >/var/qmail/control/concurrencyincoming
> ! /var/log/clamav has wrong owner, should be qscand
> ...try: chown -R qscand:clamav /var/log/clamav
> ! /var/lib/clamav has wrong owner, should be qscand
> ...try: chown -R qscand:clamav /var/lib/clamav
> ! /var/run/clamav has wrong owner, should be qscand
> ...try: chown -R qscand:clamav /var/run/clamav
> ! /service/qmail-send is missing
> ...try: ln -s /var/qmail/service/qmail-send /service/qmail-send
> ! /service/qmail-smtpd is missing
> ...try: ln -s /var/qmail/service/qmail-smtpd /service/qmail-smtpd
> ! /etc/tcp.smtp is missing
> ...try: echo '127.:allow,RELAYCLIENT=""' >>/etc/tcp.smtp
> ! /etc/tcp.smtp.cdb is missing
> ...try: /var/qmail/bin/qmailctl cdb
> ! Alias for root is missing
> ...try: echo me >/var/qmail/alias/.qmail-root
> ! Alias for postmaster is missing
> ...try: echo me >/var/qmail/alias/.qmail-postmaster
> ! Alias for mailer-daemon is missing
> ...try: echo me >/var/q

Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[Thibault Richard]

Hello,

OK I understand now. You didn’t specified in your request that you tried from 
the webinterface

The result of the script is normal at this install step (it verify all the 
steps)

Best Regards

Thibault

From: swaroop kumar 
Sent: Thursday, May 16, 2013 3:51 PM
To: vchkpw@inter7.com 
Subject: Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to 
vpopmail/domains/domain directory

Hello Geeks,


I resolved it by adding www-data to vchkpw group and changed owner and group of 
the apache files to vpopmail:vchkpw earlier it was www-data was owner and 
group. Now i am facing new error "could not update file".


@Thibs


I ran this script "/downloads/scripts/qmr_inst_check" and below is the output. 

! Couldn't find /var/qmail/supervise!
! /var/qmail/supervise/qmail-send/run is missing
...try: cp /downloads/scripts/service-qmail-send-run 
/var/qmail/supervise/qmail-send/run
! /service directory is missing
! Couldn't find /var/qmail/control/defaultdelivery
! DatabaseOwner is incorrect in /etc/clamav/freshclam.conf
! LocalSocketGroup is incorrect in /etc/clamav/clamd.conf
! User is incorrect in /etc/clamav/clamd.conf
! /var/qmail/bin/qmailctl is missing
! /usr/bin/qmailctl is missing
...try: ln -s /var/qmail/bin/qmailctl /usr/bin
! /var/qmail/supervise/qmail-send/run file is missing
! /var/qmail/supervise/qmail-send/log/run file is missing
! /var/qmail/supervise/qmail-smtpd/run file is missing
! /var/qmail/supervise/qmail-smtpd/log/run file is missing
! /var/qmail/control/concurrencyincoming is missing
...try: echo 30 >/var/qmail/control/concurrencyincoming
! /var/log/clamav has wrong owner, should be qscand
...try: chown -R qscand:clamav /var/log/clamav
! /var/lib/clamav has wrong owner, should be qscand
...try: chown -R qscand:clamav /var/lib/clamav
! /var/run/clamav has wrong owner, should be qscand
...try: chown -R qscand:clamav /var/run/clamav
! /service/qmail-send is missing
...try: ln -s /var/qmail/service/qmail-send /service/qmail-send
! /service/qmail-smtpd is missing
...try: ln -s /var/qmail/service/qmail-smtpd /service/qmail-smtpd
! /etc/tcp.smtp is missing
...try: echo '127.:allow,RELAYCLIENT=""' >>/etc/tcp.smtp
! /etc/tcp.smtp.cdb is missing
...try: /var/qmail/bin/qmailctl cdb
! Alias for root is missing
...try: echo me >/var/qmail/alias/.qmail-root
root@mail:~# /downloads/scripts/qmr_inst_check
! Couldn't find /var/qmail/supervise!
! /var/qmail/supervise/qmail-send/run is missing
...try: cp /downloads/scripts/service-qmail-send-run 
/var/qmail/supervise/qmail-send/run
! /service directory is missing
! Couldn't find /var/qmail/control/defaultdelivery
! DatabaseOwner is incorrect in /etc/clamav/freshclam.conf
! LocalSocketGroup is incorrect in /etc/clamav/clamd.conf
! User is incorrect in /etc/clamav/clamd.conf
! /var/qmail/bin/qmailctl is missing
! /usr/bin/qmailctl is missing
...try: ln -s /var/qmail/bin/qmailctl /usr/bin
! /var/qmail/supervise/qmail-send/run file is missing
! /var/qmail/supervise/qmail-send/log/run file is missing
! /var/qmail/supervise/qmail-smtpd/run file is missing
! /var/qmail/supervise/qmail-smtpd/log/run file is missing
! /var/qmail/control/concurrencyincoming is missing
...try: echo 30 >/var/qmail/control/concurrencyincoming
! /var/log/clamav has wrong owner, should be qscand
...try: chown -R qscand:clamav /var/log/clamav
! /var/lib/clamav has wrong owner, should be qscand
...try: chown -R qscand:clamav /var/lib/clamav
! /var/run/clamav has wrong owner, should be qscand
...try: chown -R qscand:clamav /var/run/clamav
! /service/qmail-send is missing
...try: ln -s /var/qmail/service/qmail-send /service/qmail-send
! /service/qmail-smtpd is missing
...try: ln -s /var/qmail/service/qmail-smtpd /service/qmail-smtpd
! /etc/tcp.smtp is missing
...try: echo '127.:allow,RELAYCLIENT=""' >>/etc/tcp.smtp
! /etc/tcp.smtp.cdb is missing
...try: /var/qmail/bin/qmailctl cdb
! Alias for root is missing
...try: echo me >/var/qmail/alias/.qmail-root
! Alias for postmaster is missing
...try: echo me >/var/qmail/alias/.qmail-postmaster
! Alias for mailer-daemon is missing
...try: echo me >/var/qmail/alias/.qmail-mailer-daemon
! Sendmail is still running
...try: /init.d/sendmail stop



Regards,

Swaroop Kundeti.




On Thu, May 16, 2013 at 7:01 PM, Thibault Richard  wrote:

  Hello,



  I’ve checked on my own install … it’s indeed the right permissions



  drwxrwx---  9 vpopmail vchkpw   4.0K Feb 21  2012 vpopmail



  With the command “ls -lah /home/vpopmail/” you should have



  drwx-- 150 vpopmail vchkpw 4.0K Apr 10 16:29 domains



  If you have at least one working domain it should be 



  ls -lah /home/vpopmail/domains



  drwx--   7 vpopmail vchkpw 4.0K Jul 29  2012 thibs.com





  Normally the vpopmail user should look like this



  grep vpopmail /etc/passwd

  vpopmail:x:89:89:Vpopmail (virtual domains) 
user:/home/vpopmail:/usr/sbin/n

Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[Thibault Richard]

My way of doing (I’m the author of http://qmailrocks.thibs.com) is not so bad 


From: Ron Herzing 
Sent: Thursday, May 16, 2013 3:49 PM
To: vchkpw@inter7.com 
Subject: Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain 
directory

I word of caution. Qmailrocks is not a good way to learn how to install Qmail.



On Thu, May 16, 2013 at 7:14 AM, swaroop kumar  wrote:


  Hi All,


  I am switching my mail server from sendmail to qmail, currently installing 
qmail in debian and i am following this link http://qmailrocks.thibs.com/


  I Have a problem in creating domains using vpopmail, below is the error 
thrown when i am trying to create a domain.

  "Unable to chdir to vpopmail/domains/domain directory"


  Can any one suggest me to overcome this, quick response is highly appreciated.


  Thanks in Advance.


  Regards,

  Swaroop Kundeti





-- 
Ron Herzing
ron.herz...@gmail.com

 

!DSPAM:5195017534121629432076!
<>

[vchkpw] Re: [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[Eric Shubert]

On 05/16/2013 06:51 AM, swaroop kumar wrote:

I resolved it by adding www-data to vchkpw group and changed owner and
group of the apache files to vpopmail:vchkpw earlier it was www-data was
owner and group. Now i am facing new error "could not update file".


This bit is solved in qmail-toaster by the following permissions:
[root@tacs-mail qmailadmin]# ls -l /usr/share/qmailadmin
total 200
drwxr-xr-x 2 root root 4096 Feb 21 10:58 html
drwxr-xr-x 3 apache   apache   4096 Feb 21 10:58 images
lrwxrwxrwx 1 vpopmail vchkpw 10 Feb 21 10:58 index.cgi -> qmailadmin
drwxr-xr-x 2 root root 4096 Feb 21 10:58 lang
-rwsr-sr-x 1 vpopmail vchkpw 184860 Feb 21 10:56 qmailadmin
[root@tacs-mail qmailadmin]#

Note the sticky bit.

HTH.

--
-Eric 'shubes'


!DSPAM:5194f58334121759474663!

Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[Remo Mattei]

I agree with that! It used to be a good point, then the best one was from Bill 
but that was taken down ;). I would suggest to look at qmail.org  or at this url

http://notes.sagredo.eu

Bye, 
Remo 

On May 16, 2013, at 06:49 , Ron Herzing  wrote:

> I word of caution. Qmailrocks is not a good way to learn how to install Qmail.
> 
> 
> On Thu, May 16, 2013 at 7:14 AM, swaroop kumar  wrote:
> 
> Hi All,
> 
> I am switching my mail server from sendmail to qmail, currently installing 
> qmail in debian and i am following this link http://qmailrocks.thibs.com/
> 
> I Have a problem in creating domains using vpopmail, below is the error 
> thrown when i am trying to create a domain.
> 
> "Unable to chdir to vpopmail/domains/domain directory"
> 
> Can any one suggest me to overcome this, quick response is highly appreciated.
> 
> Thanks in Advance.
>   
> Regards,
> Swaroop Kundeti
> 
> 
> 
> -- 
> Ron Herzing
> ron.herz...@gmail.com
> 



!DSPAM:5194f44f34123729460077!

[vchkpw] [SPAM] Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[Tom Collins]

If you're talking about QmailAdmin, you need to make sure it's got the suid bit 
set and is owned by the vpopmail user.

You shouldn't have changed Apache to run as vpopmail, and should revert those 
changes.

If vpopmail is working for you, you should focus your efforts on 
troubleshooting QmailAdmin.

-Tom


On May 16, 2013, at 7:07 AM, swaroop kumar wrote:
> I could able to add domains by using command line 
> "/home/vpopmail/bin/vadddomain virtual-labs.ac.in admin" but not in gui. 
> error "could not update file" was trown when i am trying to create domain.
> 
> After creating domain using command i could able to view the details of the 
> domain over gui.



!DSPAM:5194c1a634122055419353!

Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[swaroop kumar]

Hello,

Thibs::

I could able to add domains by using command line
"/home/vpopmail/bin/vadddomain virtual-labs.ac.in admin" but not in gui.
error "could not update file" was trown when i am trying to create domain.

After creating domain using command i could able to view the details of the
domain over gui.

Regards,
Swaroop Kundeti


On Thu, May 16, 2013 at 7:01 PM, Thibault Richard  wrote:

> Hello,
>
> ** **
>
> I’ve checked on my own install … it’s indeed the right permissions
>
> ** **
>
> drwxrwx---  9 vpopmail vchkpw   4.0K Feb 21  2012 vpopmail
>
> ** **
>
> With the command “*ls -lah /home/vpopmail/*” you should have
>
> ** **
>
> drwx-- 150 vpopmail vchkpw 4.0K Apr 10 16:29 domains
>
> ** **
>
> If you have at least one working domain it should be 
>
> ** **
>
> *ls -lah /home/vpopmail/domains*
>
> ** **
>
> drwx--   7 vpopmail vchkpw 4.0K Jul 29  2012 thibs.com
>
> ** **
>
> ** **
>
> Normally the vpopmail user should look like this
>
> ** **
>
> *grep vpopmail /etc/passwd*
>
> vpopmail:x:89:89:Vpopmail (virtual domains)
> user:/home/vpopmail:/usr/sbin/nologin
>
> ** **
>
> How do you try to create the domain ? 
>
> ** **
>
> By command line you should use
>
> ** **
>
> */home/vpopmail/bin/vadddomain test.com username*
>
> ** **
>
> As it seems you are using my guide, could you please do :
>
> ** **
>
> *chmod +x /downloads/scripts/qmr_inst_check
> /downloads/scripts/qmr_inst_check*
>
> ** **
>
> and tell me the result
>
> ** **
>
> ** **
>
> Best Regards
>
> ** **
>
> ** **
>
> Thibault a.k.a Thibs
>
> ** **
>
> *From:* swaroop kumar [mailto:swaroopk...@gmail.com]
> *Sent:* jeudi 16 mai 2013 14:23
> *To:* vchkpw@inter7.com
> *Subject:* Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir
> to vpopmail/domains/domain directory
>
> ** **
>
> Hi,
>
> Permissions seems to be ok.
>
> drwxrwx--- 8 vpopmail vchkpw 4096 May 16 13:56 vpopmail
>
> Regards,
> Swaroop.
>
> ** **
>
> On Thu, May 16, 2013 at 5:50 PM, Todor Petkov  wrote:
>
> On 16/05/2013 03:14 PM, swaroop kumar wrote:
>
> Hi All,
>
> I am switching my mail server from sendmail to qmail, currently
> installing qmail in debian and i am following this link
>
> http://qmailrocks.thibs.com/ [1]
>
>
>
> I Have a problem in creating domains using vpopmail, below is the
> error thrown when i am trying to create a domain.
>
> "Unable to chdir to vpopmail/domains/domain directory"
>
> Can any one suggest me to overcome this, quick response is highly
> appreciated.
>
> Thanks in Advance.
>
>
> Regards,
> Swaroop Kundeti
>  
>
> Links:
> --
> [1] http://qmailrocks.thibs.com/
>
>
>
> Hi,
>
> check the directory permissions. ~vpopmail and below must be owned by the
> vpopmail user.
>
>
> Regards,
>
>
>
>
> 
>
>
>
>
> -- 
>
> Sincerely,
> --
> Swaroop Kundeti.
> Project Engineer.
> Virtual-Labs.
> IIIT - Gachibowli.
> Hyderabad.
> +91-9866221131.
>
> 
> 
>



-- 
Sincerely,
--
Swaroop Kundeti.
Project Engineer.
Virtual-Labs.
IIIT - Gachibowli.
Hyderabad.
+91-9866221131.


!DSPAM:5194bf3d34121642640776!

Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[swaroop kumar]

* **
>
> */home/vpopmail/bin/vadddomain test.com username*
>
> ** **
>
> As it seems you are using my guide, could you please do :
>
> ** **
>
> *chmod +x /downloads/scripts/qmr_inst_check
> /downloads/scripts/qmr_inst_check*
>
> ** **
>
> and tell me the result
>
> ** **
>
> ** **
>
> Best Regards
>
> ** **
>
> ** **
>
> Thibault a.k.a Thibs
>
> ** **
>
> *From:* swaroop kumar [mailto:swaroopk...@gmail.com]
> *Sent:* jeudi 16 mai 2013 14:23
> *To:* vchkpw@inter7.com
> *Subject:* Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir
> to vpopmail/domains/domain directory
>
> ** **
>
> Hi,
>
> Permissions seems to be ok.
>
> drwxrwx--- 8 vpopmail vchkpw 4096 May 16 13:56 vpopmail
>
> Regards,
> Swaroop.
>
> ** **
>
> On Thu, May 16, 2013 at 5:50 PM, Todor Petkov  wrote:
>
> On 16/05/2013 03:14 PM, swaroop kumar wrote:
>
> Hi All,
>
> I am switching my mail server from sendmail to qmail, currently
> installing qmail in debian and i am following this link
>
> http://qmailrocks.thibs.com/ [1]
>
>
>
> I Have a problem in creating domains using vpopmail, below is the
> error thrown when i am trying to create a domain.
>
> "Unable to chdir to vpopmail/domains/domain directory"
>
> Can any one suggest me to overcome this, quick response is highly
> appreciated.
>
> Thanks in Advance.
>
>
> Regards,
> Swaroop Kundeti
>  
>
> Links:
> --
> [1] http://qmailrocks.thibs.com/
>
>
>
> Hi,
>
> check the directory permissions. ~vpopmail and below must be owned by the
> vpopmail user.
>
>
> Regards,
>
>
>
>
> 
>
>
>
>
> -- 
>
> Sincerely,
> --
> Swaroop Kundeti.
> Project Engineer.
> Virtual-Labs.
> IIIT - Gachibowli.
> Hyderabad.
> +91-9866221131.
>
> 
> 
>


!DSPAM:5194bb8934125324512510!

Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[Ron Herzing]

I word of caution. Qmailrocks is not a good way to learn how to install
Qmail.


On Thu, May 16, 2013 at 7:14 AM, swaroop kumar wrote:

>
> Hi All,
>
> I am switching my mail server from sendmail to qmail, currently installing
> qmail in debian and i am following this link http://qmailrocks.thibs.com/
>
> I Have a problem in creating domains using vpopmail, below is the error
> thrown when i am trying to create a domain.
>
> "Unable to chdir to vpopmail/domains/domain directory"
>
> Can any one suggest me to overcome this, quick response is highly
> appreciated.
>
> Thanks in Advance.
>
> Regards,
> Swaroop Kundeti
> 




-- 
Ron Herzing
ron.herz...@gmail.com


!DSPAM:5194bb0f34129738711467!

RE: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[Thibault Richard]

Hello,

 

I've checked on my own install . it's indeed the right permissions

 

drwxrwx---  9 vpopmail vchkpw   4.0K Feb 21  2012 vpopmail

 

With the command "ls -lah /home/vpopmail/" you should have

 

drwx-- 150 vpopmail vchkpw 4.0K Apr 10 16:29 domains

 

If you have at least one working domain it should be 

 

ls -lah /home/vpopmail/domains

 

drwx--   7 vpopmail vchkpw 4.0K Jul 29  2012 thibs.com

 

 

Normally the vpopmail user should look like this

 

grep vpopmail /etc/passwd

vpopmail:x:89:89:Vpopmail (virtual domains)
user:/home/vpopmail:/usr/sbin/nologin

 

How do you try to create the domain ? 

 

By command line you should use

 

/home/vpopmail/bin/vadddomain test.com username

 

As it seems you are using my guide, could you please do :

 

chmod +x /downloads/scripts/qmr_inst_check
/downloads/scripts/qmr_inst_check

 

and tell me the result

 

 

Best Regards

 

 

Thibault a.k.a Thibs

 

From: swaroop kumar [mailto:swaroopk...@gmail.com] 
Sent: jeudi 16 mai 2013 14:23
To: vchkpw@inter7.com
Subject: Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to
vpopmail/domains/domain directory

 

Hi,

Permissions seems to be ok.

drwxrwx--- 8 vpopmail vchkpw 4096 May 16 13:56 vpopmail

Regards,
Swaroop.

 

On Thu, May 16, 2013 at 5:50 PM, Todor Petkov  wrote:

On 16/05/2013 03:14 PM, swaroop kumar wrote:

Hi All,

I am switching my mail server from sendmail to qmail, currently
installing qmail in debian and i am following this link

http://qmailrocks.thibs.com/ [1]



I Have a problem in creating domains using vpopmail, below is the
error thrown when i am trying to create a domain.

"Unable to chdir to vpopmail/domains/domain directory"

Can any one suggest me to overcome this, quick response is highly
appreciated.

Thanks in Advance.

 
Regards,
Swaroop Kundeti
 

Links:
--
[1] http://qmailrocks.thibs.com/



Hi,

check the directory permissions. ~vpopmail and below must be owned by the
vpopmail user.


Regards,









-- 

Sincerely,
--
Swaroop Kundeti.
Project Engineer.
Virtual-Labs.
IIIT - Gachibowli.
Hyderabad.
+91-9866221131.

 



!DSPAM:5194b6f434127088155763!

[vchkpw] Re: [This is probably spam] Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[Todor Petkov]

On 16/05/2013 03:23 PM, swaroop kumar wrote:

Hi,

Permissions seems to be ok.

drwxrwx--- 8 vpopmail vchkpw 4096 May 16 13:56 vpopmail

Regards,
Swaroop.




Check ~vpopmail/domains and all the directories leading to the 
domain.com one.



!DSPAM:5194ac5434121347158045!

Re: [vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[swaroop kumar]

Hi,

Permissions seems to be ok.

drwxrwx--- 8 vpopmail vchkpw 4096 May 16 13:56 vpopmail

Regards,
Swaroop.


On Thu, May 16, 2013 at 5:50 PM, Todor Petkov  wrote:

> On 16/05/2013 03:14 PM, swaroop kumar wrote:
>
>> Hi All,
>>
>> I am switching my mail server from sendmail to qmail, currently
>> installing qmail in debian and i am following this link
>> http://qmailrocks.thibs.com/ [1]
>>
>>
>> I Have a problem in creating domains using vpopmail, below is the
>> error thrown when i am trying to create a domain.
>>
>> "Unable to chdir to vpopmail/domains/domain directory"
>>
>> Can any one suggest me to overcome this, quick response is highly
>> appreciated.
>>
>> Thanks in Advance.
>>
>>
>> Regards,
>> Swaroop Kundeti
>>
>> Links:
>> --
>> [1] http://qmailrocks.thibs.com/
>>
>
>
> Hi,
>
> check the directory permissions. ~vpopmail and below must be owned by the
> vpopmail user.
>
>
> Regards,
>
>
>
> 
>
>


-- 
Sincerely,
--
Swaroop Kundeti.
Project Engineer.
Virtual-Labs.
IIIT - Gachibowli.
Hyderabad.
+91-9866221131.


!DSPAM:5194a6d834129043313283!

[vchkpw] [SPAM] Re: [vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[Todor Petkov]

On 16/05/2013 03:14 PM, swaroop kumar wrote:

Hi All,

I am switching my mail server from sendmail to qmail, currently
installing qmail in debian and i am following this link
http://qmailrocks.thibs.com/ [1]

I Have a problem in creating domains using vpopmail, below is the
error thrown when i am trying to create a domain.

"Unable to chdir to vpopmail/domains/domain directory"

Can any one suggest me to overcome this, quick response is highly
appreciated.

Thanks in Advance.

 
Regards,
Swaroop Kundeti
 


Links:
--
[1] http://qmailrocks.thibs.com/



Hi,

check the directory permissions. ~vpopmail and below must be owned by 
the vpopmail user.



Regards,



!DSPAM:5194a61634121924852515!

[vchkpw] [SPAM] Error: Unable to chdir to vpopmail/domains/domain directory

[swaroop kumar]

Hi All,

I am switching my mail server from sendmail to qmail, currently installing
qmail in debian and i am following this link http://qmailrocks.thibs.com/

I Have a problem in creating domains using vpopmail, below is the error
thrown when i am trying to create a domain.

"Unable to chdir to vpopmail/domains/domain directory"

Can any one suggest me to overcome this, quick response is highly
appreciated.

Thanks in Advance.

Regards,
Swaroop Kundeti


!DSPAM:5194a4bc34126005364638!