Tom Collins wrote:
i have a problem with the pop auth... i get for every user a pop
access denied.. it's not apop. i have compiled without the
roaming-user option.
If you use Courier-IMAP, did you recompile it after installing the new
vpopmail?
Is anyone out there successfully making POP
X-Istence wrote:
Tom Collins wrote:
On Tuesday, October 21, 2003, at 09:11 AM, Trey Nolen wrote:
After upgrading to 5.3.29, we are getting the following error when
trying to
add a domain:
Error: (vadduser) can't read domain limits
If you have a ~vpopmail/etc/vlimits.default file, it should
Tom Collins wrote:
On Tuesday, October 21, 2003, at 11:28 AM, Jochen Schug wrote:
Is there a documentation about what these values mean? What's the
difference between quota, default_quota, perm_quota and
perm_defaultquota?
Here's the file I built for the distribution which includes some
Tom Collins wrote:
On Tuesday, October 21, 2003, at 12:50 PM, Jochen Schug wrote:
# quota for entire domain, in megabytes
# example shows a domain with a 100MB quota and a limit of 10,000
messages
#quota 100
Unless the behaviour changed, shouldn't this read 104857600 instead
Tom Collins wrote:
http://vpopmail.sf.net/
More bug fixes as we move toward a stable 5.4 release.
This version includes changes to the configure and build process, so
please post bug reports to the bug tracker on SourceForge if you
encounter any problems with configure/build.
Seems to be
Tom Collins wrote:
On Friday, October 17, 2003, at 05:27 PM, David Bristol wrote:
This may not be the way to go about this, but have you verified that
both domains are in the qmail/control/locals file?
Don't put vpopmail domains in control/locals. You'll mess things up.
There isn't a known
Eduardo M. Bragatto wrote:
What do I need to know before upgrading from this version to that one?!
Is there any changes that I need to do about? I'm using CDB to store
users/passes.
Eduardo,
A while ago I upgraded from 5.3.20 to 5.3.27 and recently to 5.3.28. The
upgrade was easy and
Hi,
I noticed that vmoddomlimits doesn't care about a trailing 'M' or 'K'
when specifing quotas... Instead of complaining that there's an unknown
character in the quota, it silently ignores it. I ended up with a domain
with 100 byte quota and 20 byte per-user quota, and only noticed it from
[EMAIL PROTECTED] wrote:
Say, during setup of vpopmail initially, I setup a default quota of 10m. I use
the latest vpopmail/qmailadmin and don't allow domain postmasters to change
quotas (must be done through commandline only).
Now, let's say I add 3 domains: domain1.com, domain2.com, and
Alexander Bruns wrote:
I am traying to get quota work for my installation og vpopmail stable (5.2.1)
I don't know how reliable the quota support in vpopmail-5.2.1 is, in the
developement branch it's working pretty good. One big improvement is the
per-domain quota, and not just on a per-user
[EMAIL PROTECTED] wrote:
I'm trying to compile qmailadmin-1.0.27 and I'm getting the following error:
gcc -I. -I/usr/local/vpopmail/include -g -O2 -c qmailadmin.c
qmailadmin.c:32:21: vlimits.h: No such file or directory
qmailadmin.c:67: error: storage size of `Limits' isn't known
make: ***
Hi,
I'm running qmail for quite a while now, and recently decided to give
the latest vpopmail version a try. So I upgraded from 5.3.20 to 5.3.27.
Everything works fine so far, except that I'm getting some weird log
entries when mail is delivered to a catchall address. The mail is
delivered
Tom Collins wrote:
On Wednesday, October 1, 2003, at 01:10 PM, Jochen Schug wrote:
And that's what it looks like with 5.3.27:
new msg 240629
info msg 240629: bytes 79927 from *removed* qp 13841 uid 106
starting delivery 24: msg 240629 to local
[EMAIL PROTECTED]
status: local 1/10 remote 0/20
Tom Collins wrote:
On Wednesday, October 1, 2003, at 03:20 PM, Jochen Schug wrote:
I tried adding the trailing slash, there's the result:
Please remove the trailing slash and try this patch. The changes in
vdelivermail resulted in a double-slash (adding a / and the
/Maildir/). The result
14 matches
Mail list logo
