Hi Matt,
Matt Brookings wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Harm van Tilborg wrote:
>> No, it's really 'rubbish' :]. I've posted this in the 'some experiences
>> with 5.5' thread before, but here we go:
>
> My apologies :)
>
>> [cv] ~# ls -l /home/vpopmail/domains/example
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harm van Tilborg wrote:
> No, it's really 'rubbish' :]. I've posted this in the 'some experiences
> with 5.5' thread before, but here we go:
My apologies :)
> [cv] ~# ls -l /home/vpopmail/domains/example.com
> total 28
> drwx-- 3 vpopmail vchkpw
Hi Matt,
Matt Brookings wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harm van Tilborg wrote:
That counter is not really working properly, since I at least downloaded
the `previous' 5.4.28 release about 10 times I guess.
Really? That's no good. Their file release system has been pre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harm van Tilborg wrote:
> That counter is not really working properly, since I at least downloaded
> the `previous' 5.4.28 release about 10 times I guess.
Really? That's no good. Their file release system has been pretty broken
since the new interfa
Hi Matt,
That counter is not really working properly, since I at least downloaded
the `previous' 5.4.28 release about 10 times I guess.
Btw: I'm looking into my personal vusage `symbolic link problem'. Like I
said: the individual user usage's are computed correctly. However, if I
request the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Collins wrote:
> If it was modified, you should increment the version number. In 3
> months, when someone reports a bug, how will we know which 5.4.28
> they're running?
Considering it has 0 downloads, I'm not entirely concerned about this
circum
If it was modified, you should increment the version number. In 3
months, when someone reports a bug, how will we know which 5.4.28
they're running?
-Tom
On Sep 2, 2009, at 10:56 AM, Matt Brookings wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adds a fix for long domain names
- --
