The "flat file" you speak of actually isn't quite a "flat file." vpopmail, unless specified otherwise, will store it's password info in cdb databases. cdb is a file database format created by DJB (same guy that wrote qmail). It's pretty speedy, but it falls to certain disadvantages that you would expect to have with a simple database like that. The most common one you see is that you can't write and rewrite to it as rapidly as you could with a mysql database (several times a second).

Please read the documentation on vpopmail and explore the inter7.com website before you post a question like this. Almost all of these questions could have been answered with a little reading. If you've got a large set of users, your best to go with MySQL because of speed, but mostly for the wide range of support and tools that MySQL has. Regardless of what database format you decide to put your data into, vpopmail can be compiled with a "clear password" field that stores the users password in clear text, as well as in an encrypted field. As for spamassassin, that's a different story all together. You'll really want to beef up on the qmail documentation, as well as vpopmail (mostly qmail though) to get a solid understanding of how your mail server actually works. Getting customized SA settings can be done, but you need to understand how qmail, SA, and vpopmail all work and how they integrate with eachother if you're going to do it.

And lastly, admin tools. Go to inter7.com and poke around. You'll find several tools, notably, qmailadmin and vqadmin. Both which should serve your purpose well. If you do go the mysql route, you can also write your own custom php scripts to run mysql queries to add/remove users and change passwords and such.

-Clayton

On Monday, December 30, 2002, at 05:09 PM, Alan Murrell wrote:

Hello,

We will be moving our mail system over to a
Qmail/Vpopmail solution very soon, and I am just
trying to decide between using the default "flat" file
format, or a MySQL backend.  My only concern at this
point is allowing our tech staff to look up a client's
password, should it become necessary.  Currently, the
email accounts are tied in to our billing database,
but this will no longer be the case.  I guess my
questions are:

  1. Is it possible to look up an email user's
password regardless of whether a the "flat file"
format is used, or the MySQL backend?  (i.e., is there
a web-based admin tool that will allow our tech staff
to do this)?
  2. Would using MySQL tend to be faster or slower
than using the "flat file" format?  We have just over
1200 email users, and expect this to grow
significantly in the next 12-18 months, so I would
like to have the better of the two in place now,rather
than looking at upgrading down the road.  (I like the
idea of using MySQL as the back end, as I think it
will allow us to write a custom interface, as well as
make certain things easier, like Spamassassin
administration, whcih we will be implementing, no?)

TIA for your input.

Alan Murrell <[EMAIL PROTECTED]>


______________________________________________________________________
Post your free ad now! http://personals.yahoo.ca



Reply via email to