I've read pretty much all the posts in this thread and have seen several suggestions for accomplishing some version of the two things needed to make the Squirrelmail plugin work "nicely" for all sites in ISPConfig:
1) Make it so it's easy for users to enter the URL for Squirrelmail and so it looks like the Squirrelmail instance is a part of the client's domain. This could be done in one of two ways (I don't care which.)...
Method 1: Redirect http://www.clientdomain.com/webmail to https://webmail.clientdomain.com:81/squirrelmail/ and have that actually invoke the common Squirrelmail plugin site.
Method 2: Redirect http://webmail.clientdomain.com to https://webmail.clientdomain.com:81/squirrelmail/
Once again, this should really be the .pkg'd Squirrelmail plugin serving up the content.
Either way makes it simple for users to get to their web e-mail system without having to remember to enter "https://" or put in the ":81". It also LOOKS nice and integrated with the client's web site since the domain name stays the same all the way through - even while inside SquirrelMail.
Make it so that when a user logs in with their full e-mail address: email@example.com
- all the mail they send will go out as coming from firstname.lastname@example.org
even if they don't fill in the "from" or "reply-to" fields under "OPTIONS" - "Personal Information" in Squirrelmail. I say this because 90% of the users won't fill that stuff in - at least not initially.
I ALMOST got this second part working by using a mod I found earlier in this thread:
To Fix it do that:
on config/config.php line 32, replace:
'$domain = 'example.com';
on src/redirect.php, line 50, add:
sqsession_register(substr($login_username, strpos($login_username, '@') + 1), 'domainname');
Fixed, every user will get the domain name they use to login.
With these mods, a user can log in as email@example.com
and send mail. When it arrives, it appears as coming from firstname.lastname@example.org
. (The "web2" part is just an example of the standard ISPConfig "webX_" prefixing scheme.) If we could strip the "web2_" then the second issue would be solved.
I've installed no plugins for Squirrelmail other than the ones already installed in the .pkg version of ISPConfig Squirrelmail.
Lastly, this all needs to happen by making one set of global modifications, one time - not by having to edit or create any additional files. Then, just by performing the standard steps inside ISPConfig one normally does to create a site for a client - the client will also have a "ready to go" SquirrelMail instance. No "create the options file for each user" kind of solutions. If you have 100 clients each with 50-200 users, one can't afford to introduce additional steps in the client or site creation process.
Has someone managed to accomplish these two goals completely? If so, would share your cool-solutions with us?