I've just finished setting up a test email system for my website customers, but I'm not very happy with it, I'm interested in any suggesstions for improvement, but I also have specific areas that are major annoyances, and I think there has to be a better way..
I'd like them to be able to have as many email addresses on their domain(s) as they choose ( within reason, I have code to limit this already ) I don't want to add any additional users to the system ( as in /etc/passwd ) I had written some mod_perl stuff and a bunch of crons on the old email system that mucked about with system users, and aliases, and the virtusers table to accomplish the same thing, but it's pretty ugly, and probably not very secure. So I'm trying to get away from adding system users for email accounts, and from dealing with a lot of different files when adding/changing/deleting email users. my current setup uses Postfix for MTA, Courier for pop3/imap, and sqWebMail for web based email sending/checking. sqWebMail and Courier are setup to use a Postgres table for authentication, and to determine where the users mailbox is. I'm using Maildir mailbox format, this is required by sqwebmail and Courier. Postfix, however, uses the aliases table to determine where a virtual users mailbox is. so I have this information in 2 separate places, which need to match. has anyone successfully gotten Postfix to play nicely with Postgres for aliases? is it a stable solution? is there some doc on doing this somewhere? this prevents having to write to aliases, and run newaliases, and postfix reload after every change, in addition to updating the database. ( and no, using MySQL which is supported by postfix natively is not an option ) would I be correct in saying that changing the info in this database would not require a postfix reload for it to take effect ? the virtual user mailboxes are in /home/mail/$user I had to set perms 777 in order to get Postfix to deliver mail there, I'm not happy about that . I tried various owner/group combos including nobody.nobody and postfix.postfix, none worked without 777. the docs I've read either don't cover this issue or I'm just not seeing it. I'm guessing it's because the given user has no login, therefore the local delivery agent cant su to that user ? am I stuck with wide open perms then ? how can I find out who the local delivery agent runs as? should I be using an MDA instead ? would it be easier ? which one ? ( it has to support Maildir ) lastly, I'm surprised there isn't a simpler solution for accomplishing this, or is there, and I just haven't seen it ? - Bryan ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
