- SQUIRRELMAIL AUTHENTICATED USER HOW TO
- SQUIRRELMAIL AUTHENTICATED USER UPDATE
- SQUIRRELMAIL AUTHENTICATED USER CODE
Of course, if I wanted to RESTRICT squirrelmail access to only specific domains I could have accompished that by only installing the squirrelmail code block in the VirtualHost code blocks of the individual domains that needed mail access from the web.
Nevertheless, I wanted to report back on what I found in the hope that my footrprints in the sand may one day prove useful to another wanderer in these regions.Īdding the alias shown in the first code block above to nf BEFORE the virtual hosts were defined enabled access to the squirrelmail directory from all my virtual domains. I managed to make this work well in the end. Thanks in advance for any advice or guidance you can provide!
Options Indexes MultiViews FollowSymLinks # Possible values include: debug, info, notice, warn, error, crit,ĬustomLog /home/public_html//logs/ap2access.log co Options ExecCGI -MultiViews +SymLinksIfOwnerMatchĮrrorLog /home/public_html//logs/ap2error.log Options Indexes FollowSymLinks MultiViews ServerAlias DocumentRoot /home/public_html//html/ How do I achieve this when my current virtual domain configuration blocks look like this? This clearly won't work in my case because although the path to squirrelmail will remain the same for ALL virtual hosts, I want a different ALIAS for squirrelhost for each virtual domain and I'd obviously LIKE to have squirrelhost for ONLY allow users who are members of that domain's user group to login by pointing their browser to However, when I read the sample apache config file for squirrelmail what it SHOWS as an example is: This will obviously require a webmail alias for each virtual domain of some sort. What I obviously WANT is for each webmail user to be able to go to their browser and type something like:Īnd be prompted to login with their username and password by squirrelmail should I be looking for the tool to do this in Postfix?) or is it done some other way?Ĭan some savvy expert guide me here, please? What am I overlooking that will automatically tell the MTA (in this case either postfix or smtp) when a user sends mail that mail sent by user userA should go out as but mail sent by userB should go out as That's question 1.
SQUIRRELMAIL AUTHENTICATED USER UPDATE
If so, where the heck is it and how do I update it? Is this user-to-domain association defined through the MTA? (i.e.
Is there a database somewhere that creates this association.
SQUIRRELMAIL AUTHENTICATED USER HOW TO
What I obviously want and expect here is that when userA who is part of the group sends mail, it will be sent and received as However, when userB who is part of the group sends mail it will be sent and received as mail from I've found yet gives me a clue about how to do this. What that MEANS in my case is even though user 'myname' belongs to the user group when myname sends email from the server it is sent as and not as So far, I can't figure out how to change that behavior. Although I have several other domains defined as virtual hosts on the server, that's the primary domain. I'm hoping someone here will either be able to point me to an article somewhere that will demystify this whole area for me or can help me fill in the details I'm missing here.įirst, assume the primary hosting domain for my server is. Now, I'm wondering how to setup the web-account (Virtual Host level) aliases for squirrelmail and find I'm "udderly cornfused" (Mooo) about how to do this. # access to configtest is limited by default to prevent information leak Code: Select all Alias /squirrelmail /usr/share/squirrelmail
0 kommentar(er)
