Finally, hit S to save your configuration settings, followed by Q to quit the config utility.Hit 6 to activate compatibility (a change_sqlpass prerequisite).From the main menu, hit 8 for plugin settings.Now we need to activate the change_sqlpass plugin we just configured.We’re only using IMAP over port 993 with TLS, so specify that.įrom the main menu, hit 2 for server settings, then A for IMAP settings, and ensure you’ve set the following:.From the main menu, hit D to set up a pre-defined configuration for specific IMAP servers.Run the /usr/sbin/squirrelmail-configure configuration utility. Step 6: Configure SquirrelMail for our mail server Comment out csp_salt_query it won't be used anyway Set to a4 to match MYSQLENCRYPT method In our previous article, we used the MySQL encrypt() function to store passwords this function does the same 'UPDATE users SET crypt_password = %4, force_change_pwd = 0 WHERE username = "%1"', 'UPDATE user_flags SET force_change_pwd = 0 WHERE username = "%1"', 'UPDATE virtual_users SET password = %4 WHERE email = "%1"', Password update, ensure this matches your MySQL virtual_users table $lookup_password_query = 'SELECT count(*) FROM virtual_users WHERE email = "%1" AND password = %4' $csp_dsn = Pretty self-explanatory: how do you query your virtual_users table? Change mailuser:mailpass to your local username and password, and change mailserver to your mail database Step 5: Set up change_sqlpass for our local database.Įdit /usr/share/squirrelmail/plugins/change_sqlpass/config.php (as usual, I’m only including the settings I changed): This way people can’t log in unless they have a mail account on our server. This allows SquirrelMail to authenticate usenames and passwords against the mail database we created in our Postfix/Dovecot article. $ tar -xvzf change_sqlpass-3.3-1.2.tar.gz Since we’re using MySQL to store our email domains and users, we’ll install the change_sqlpass plugin: Step 4: Allow users to change their passwords from the web interface htaccess file in /usr/share/squirrelmail to require a double login. If you don’t want the web interface to be publicly accessible, you can put an. $ ln -s /etc/squirrelmail/nf /etc/apache2/sites-available/ Step 3: Make your SquirrelMail web site accessibleĬreate a symbolic link to the SquirrelMail config file so Apache knows about it, then restart Apache: ServerName # the URL where you want SquirrelMail to live $ apt-get install squirrelmail squirrelmail-compatibilityĮdit the provided /etc/squirrelmail/nf configuration file: Installing SquirrelMail Step 1: Installation If not, you may want to refer to the Apache documentation. It also presumes you’re familiar with Apache virtual hosting. This article assumes you have a standard LAMP setup with Apache 2/PHP 5/mysqli running on your server. And since you access it using standard software over standard network ports (HTTP and HTTPS, TCP/80 and TCP/443), it’s hard for your employer to block. SquirrelMail lets you log in and read your personal email like you’d read any other web site. One workaround is a web-based email client like the SquirrelMail web mail system. Furthermore, they don’t want you using your phone in the office, so reading your personal email is a problem. But you have another problem: your IT department at work won’t let you add your own email accounts to the Outlook mail program they make you use. So now you have an Ubuntu 12.04 mail server set up with Postfix, Dovecot, virtual users, and a spam filtering system. I’d strongly consider using Roundcube instead. Update July 2017: SquirrelMail seems to have been abandoned by its developer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |