I've done this, it's not the cleanest patch in the world and you still have
the problem of local delivery, how does sendmail or whatever look into the
mysql table? I'm looking at switching to Exim instead of sendmail or maybe
something else as it seems to be easier to extend and easier to query
databases from - it's got a builtin Perl interpreter, so you can write your
mail delivery rules in Perl, which is a big win in my book,
Fergal
At 15:33 07/09/00, S�ren Peter Skou wrote:
>Okay, so far so good, I've got the pam_mysql working on FreeBSD with 3.1B10
>(Version correct this time :) and together with qpopper I'm now able to
>Authenticate users, but only if those users exists both in master.passwd and
>in the SQL Database I've setup for the purpose. The password the system
>checks against is the one from SQL so that part is fine and dandy.
>
>I then stepped back and looked at what I was trying once again, and it
>became apparent that it wasn't what I wanted, instead I wanted something
>along these lines:
>
>MySQL (Or other SQL for that matter) contains the equivalent of
>master.passwd
>Pop3 server then knows where to look for it's mailfile for a given user, ie.
>the user bork will have /var/mail/bork (yes, I am incredibly simpleminded)
>:).
>apache server looks into the same table to find users homedir, and can
>prepend whatever USER_DIR is defined to be in the httpd.conf
>MTA also looks here to find where to put the mail (ie, /var/spool).
>
>I'm imagining a table that looks something like this:
>
>id - Only inside the Database
>username - For the authentication and location of mailfiles.
>password - For authentication purposes
>home_dir - user's homedir
>mail_dir - Where to look for the users mailfile.
>
>As I see it this is more or less what I need, anyone who has done this, or
>are in the process of doing so, I'd be more than happy to help in anyway I
>can.
>
>
>Friendly Greetings
>S. P. Skou
