On Fri, Mar 27, 2009 at 3:32 PM, Matt Brookings wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> aledr wrote:
>>> Here is the section for MD5 on a x86_64 system:
>
> What OS and flavor btw? I'm installing CentOS on a laptop over here. I've
> got to resize the partitions first though.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
aledr wrote:
>> Here is the section for MD5 on a x86_64 system:
What OS and flavor btw? I'm installing CentOS on a laptop over here. I've
got to resize the partitions first though. Another hour and 45 left on the
resize.
- --
/*
Matt Brookings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
aledr wrote:
>> I think I found another problem: configure is not checking for
>> "--enable-auth-login", if always show it OFF.
Fixed in SVN.
>> configure:7420: ./conftest
>> ./configure: line 7421: 29575 Segmentation fais theult
>> ./conftest$
On Fri, Mar 27, 2009 at 10:29 AM, Matt Brookings wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> aledr wrote:
>> I updated my spec files and tested:
>>
>> - Seems to be a wrong check against MD5 support on x86_64 systems;
>
> I updated the MD5 check because it was already having an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manvendra Bhangui wrote:
> My mistake. That flag was meant for a filter executable built using eps.
> I have not yet completed it for vpopmail. It should be removed.
Sounds good. It's in the repository.
- --
/*
Matt BrookingsGnuPG Key D94
On Fri, Mar 27, 2009 at 7:29 PM, Matt Brookings wrote:
> I'm adding vmoddomain to 5.5 along with a few other changes and I noticed a
> 'vfilter' flag in
> vmoddomain which is not used. What is the purpose of this flag?
> Left-overs from other work?
> If it has no specific use within vpopmail as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm adding vmoddomain to 5.5 along with a few other changes and I noticed a
'vfilter' flag in
vmoddomain which is not used. What is the purpose of this flag? Left-overs
from other work?
If it has no specific use within vpopmail as a whole, which it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
aledr wrote:
> I updated my spec files and tested:
>
>- Seems to be a wrong check against MD5 support on x86_64 systems;
I updated the MD5 check because it was already having an issue on some
older systems. I'm pretty sure I tested it on a 64bit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wouter van der Schagt wrote:
> Yup :) My question is, perhaps i should rephrase it, whether it can be
> included in the next version automatically :)
I'll get it in 5.5 later today. I have to patch it for 5.5 first.
- --
/*
Matt Brookings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Itamar Reis Peixoto wrote:
> + CFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic'
> + export CFLAGS
> + CXXFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
>
Yup :) My question is, perhaps i should rephrase it, whether it can be included
in the next version automatically :)
Sincerely,
- Wouter van der Schagt
- Original Message -
From: Manvendra Bhangui
To: vchkpw@inter7.com
Sent: Friday, March 27, 2009 5:34 PM
Subject: Re: [vchkpw
On Fri, Mar 27, 2009 at 2:57 PM, Wouter van der Schagt
wrote:
> I have one more request. Could you have a look at
>
> https://sourceforge.net/tracker/?func=detail&atid=577801&aid=2532389&group_id=85937
> for possible inclusion in 5.5? It is a nice feature that is also useful in
> automation which
I've added the vmoduserflags binary to 5.5. It handles what people were
looking for
in regards to toggling of settings in a user's bitfield.
Wonderful, i am going to test it immediately :) thank a lot!! I will let you
know the test
results of our production environment.
I have one more requ
13 matches
Mail list logo
