----- Original Message -----
From: "Rick Romero" <[EMAIL PROTECTED]>
To: "Michael Bowe" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, March 26, 2003 12:15 AM
Subject: Re: [qmailadmin] qmailadmin and vpopmail+mysql inconsistency


> I really don't what what you're doing (sign up script? why not
> vqregister?), so what I've said may not work for you.  Heck, that's even
> better.  Just install vqregister, and fill in the form fields with your
> asp.

Hi Rick

I will give you a bit more background...

We are an ISP

When a new user signs up, they initally get allocated a single email address

However, we allow each customer though to have up to 2 email addresses at no
charge

We have an ASP script on our web site that allows customers to create a 2nd
mailbox in real time.

If the user needs a 2nd mailbox, they can go to our web site, selected the
new email address that they desire, and the ASP script makes a connection to
the MySQL database and inserts the record directly into the correct table

That way the mailbox is available immediately for the customer to use

We dont have to worry about taking processing crcd or anything like that as
their 2nd mailbox is available at no charge.

It is certainly possible for my ASP to use a perlscript function to POP auth
against the mailbox after creation, so maybe this is going to be my best bet
to ensure the maildir gets created there-and-then.

We have been doing these direct inserts for quite a while and from the
previous discussions I had seen on the Inter7 lists, and from reading the
docs, I was under the impression that this was acceptable practice

However I can see that with the new limits code that is currently under
development, that such inserts are going to bypass any such limits checking.

We only use this technique on our main email domain (which does not have any
limits with regards to the max # of mailboxes allowed). All our domainname
hosting customers use qmailadmin to create mailboxes and the normal
.qmailadmin-limits keep them within their quota limitations.

But the question still remains that qmailadmin is consistent in the way it
handles these types of users-without-maildirs. Logging in as postmaster lets
you access the mailbox ok, but logging in as the user results in a nasty
error. Hopefully it can me changed so that either both display a
meaningful/friendly error, or both work ok.

Michael.


Reply via email to