I've installed the new vpopmail 4.9.5 and created a couple users under
system users other than vpopmail and they work just fine for mail delivery
and pop but neither sqwebmail nor courier-imap will authenticate users whose
UID/GID is not vpopmail/vchkpw.
Courier-imap has it's own authentication module for authenticating a
vpopmail user. I had courier-imap 1.0 installed and it failed with an error
message that indicated an authentication failure. Just for grins I decided
to see if it was fixed in courier-imap 1.1 and installed it. It works just
fine for domains installed user the vpopmail UID/GID but still won't
authenticate for domains within another home dirctory. The error message
returned is:
Your account is temporarily unavailable (+t bit set on home directory).
Configuration:
Account: admin.mail.safeserver.com (1)
Server: admin.mail.safeserver.com
User name: [EMAIL PROTECTED]
Protocol: IMAP
Port: 993
Secure(SSL): 1
Code: 800cccdd
It yields the same error message when connecting to either the IMAP or IMAP
SSL ports.
The same problem plagues sqwebmail at this time too. It won't authenticate
users whose domains are not located within the ~vpopmail dir. I tried
installing the newer 1.0.0.20001007 version but without success (so far, I'm
still playing with it).
Have I just missed something completely obvious or is this a valid
limitation at this time?
Matt
-Original Message-
From: listy-dyskusyjne Krzysztof Dabrowski [mailto:[EMAIL PROTECTED]]
Sent: Sunday, October 15, 2000 2:42 PM
To: [EMAIL PROTECTED]
Subject: Re: quota question on 4.9.5
I don't mind doing some coding, but there seems to
be more missing. I'll need to dig through the code
some more. It would be nice if we can have the
postmaster get an unlimited quota so they can be
informed that their domain is over quota and that
they should get the quota increased or have their
people start cleaning up their mail. The postmaster
may need to get mail on each bounce (not the message,
but that a message from so-and-so bounced), and possibly
which ID's are using up the space so it can be cleaned
properly.
Before putting some code together, we may want to put
together a real design first and try to think it through.
The domain per unix ID is good, but we may want to put
the postmaster in a different place so they can still
get notifications.
What are your thoughts? What else did I miss? (I'm sure
I've missed alot).
My vargid patch (get it from my page, announced on the list separately)
will let you choose any gid/uid for any domain.
We can then use a GID per domain scheme.
Postmaster can be given another uid (a special one) so it wont have the
quota.
I do not know 2 things at this point:
a) how group user quotas mix together
b) is it reasonable to have one quota-less account and give it to user...
they will use this account to transfer big emials for sure and this is what
we want to stop , using quotas.
Kris
