I have patched VpopMail 5.4.13 so that each user in a domain can have
there E-Mail handled by there own set of .qmail files (in
/var/vpopmail/domains/{domain}/{user}), this is a patch to
'int check_forward_deliver(char *dir)' in vdelivermail.c.
This means for us when we delete an E-Mail address
It extends the normal use of .qmail file to .qmail, .qmail-default,
.qmail-extension and .qmail-extension-default based on the remaining
extension on the incoming E-Mail address in the order as specified in the
qmail source code.
On Fri, 16 Dec 2005, DAve wrote:
Drew Wells wrote:
I have
including . to : character handling?
Ken Jones
Drew Wells wrote:
It extends the normal use of .qmail file to .qmail, .qmail-default,
.qmail-extension and .qmail-extension-default based on the remaining
extension on the incoming E-Mail address in the order as specified in the
qmail
Yep, exactly that. I am using '[EMAIL PROTECTED]' and it is
handled by /var/vpopmain/domains/elysium.ltd.uk/drew/.qmail-vpopmail.
On Fri, 16 Dec 2005, DAve wrote:
Drew Wells wrote:
It extends the normal use of .qmail file to .qmail, .qmail-default,
.qmail-extension and .qmail-extension
Yep, it is exactly that. At the moment I have all the files in
~vpopmail/domains/domainname/username called '.qmail'.
I have attached the patch 'as is' that I have been using for a while now,
and have also quickly modded the patch in include .vpopmail files (as a
secondary to .qmail, please
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.c
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
---
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
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
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
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
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
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
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
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
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
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/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
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
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
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
21 matches
Mail list logo
