Our DBMail/Postfix setup does just this and adds several additional tables
including client, domain and password_hint (for plain text password
storage)
Our Postfix main.cf looks like this (everything else is defaulted)
# NO local recipient lookups
local_recipient_maps =
# DBMail looks after alles ..
mydestination = mysql:/etc/postfix/transport.cf
transport_maps = mysql:/etc/postfix/transport.cf
transport.cf contains .....
user=dbmail
password=***********
dbname=dbmail
table=domain
select_field=transport
where_field=domain
hosts=localhost
The domain table is additional to the standard dbmail sql setup and
contains (amongst other things) ..
Field Type Null Key Default Extra
domain_id mediumint(7) unsigned PRI NULL auto_increment
client_idnr mediumint(7) unsigned
domain varchar(40)
is_suspended enum('No','Yes') No
transport varchar(20) dbmail:
Our hosting service runs almost entirely on the dbmail database and our
users table includes additional fields including :
uid UNIX User ID
gid UNIX Group ID
homedir user's home directory
When a new account is created. it is assigned an "internal" userid based
on service type (someting like cm033192, etc) which lives in the UNIX
passwd file and provides GID/UID - his logon - which lives in the dbmail
table "users" will be [EMAIL PROTECTED] - only the admin user has a
gid/uid (at this stage).
We use pure-ftpd as our FTP agent and it also has a MySQL capability. As a
result, all ftp access is also authorized using the dbmail users table.
Very simple and it all works.
Keep up the good work with DBMail - it's a great product and one of the
easiest MTAs to manage that I have come across.
--
Tom Salter
Linux is like a TEPEE - No Gates - No Windows - Apache Inside!
--
Tom Salter
011-949-1709
082-940-0754
Linux is like a TEPEE - No Gates - No Windows - Apache Inside!
