on 2/25/03 7:47 PM, Jesse Guardiani <[EMAIL PROTECTED]> wrote:
> Greetings list,
>
> New! An updated version of my 'domainmap' patch, without the domainmap file,
> and with a bunch more functionality!
I did a quick test of most of the features - but only the name-based virtual
hosting side of things.
My original logindomainlist worked just as things used to work.
mapping works (name-based)
* modifier works
@ modifiers works
group identifier works
Hey! What can I say. That was easy. Thanks again.
-Kurt Bigler
>
> The logindomainlist file now takes on the following format:
>
> DOMAIN1:IP1:MODIFIER
> DOMAIN2:IP2:MODIFIER
> DOMAIN3:DOMAIN4:MODIFIER
> DOMAIN4:DOMAIN5:MODIFIER
> DOMAIN6:IP3:MODIFIER
> etc...
>
> The first field indicates the mail domain we want to log into, and the domain
> that will be displayed in the drop down list on
> login.html, if we specify that we want to see it.
>
> The second field can be either an IP or a Domain. This field is matched
> against the SERVER_ADDR and HTTP_HOST CGI environment
> variables. If a match is found, then the domain listed in field one is set to
> be the default option in the drop down, or is set to
> be the value of the 'logindomain' hidden field if a drop down is not
> specified.
>
> The third field is new. This is where the magic happens. There are currently
> THREE possible values:
>
> 1.) The third field can consist of a single asterisk ("*"). This essentially
> means, "Do not display a drop down menu on login.html
> for this domain."
>
> Example:
>
> DOMAIN1:13.13.13.13:*
>
> 2.) Also, the third field can consist of a single @ symbol! This essentially
> means exactly what the asterisk ("*") means, except the
> text "@DOMAIN1" is displayed in the drop-down's place.
>
> Example:
>
> DOMAIN2:13.13.13.14:@
>
> 3.) And finally, the third field can be a 147 character or less "group"
> identifier. This identifier can then be used to mark other
> domains as belonging to the group. All domains belonging to a group are
> displayed together in the drop down.
>
> Example:
>
> DOMAIN3:13.13.13.15:personaldomains
> DOMAIN4:13.13.13.16:@
> DOMAIN5:13.13.13.17:personaldomains
>
> In the example above, if someone logs into the following URL:
>
> http://DOMAIN3/cgi-bin/sqwebmail
>
> or
>
> http://DOMAIN5/cgi-bin/sqwebmail
>
> They will see a drop down menu containing the following:
>
> @DOMAIN3
> @DOMAIN5
>
> Conversely, if someone were to access the following URL:
>
> http://DOMAIN4/cgi-bin/sqwebmail
>
> They would see the text: "@DOMAIN4" next to their userid field.
>
> Note: You don't have to use IP addresses in field two of the logindomainlist
> file. I just used IPs for clarity.
>
> Also, this logindomainlist patch aims to be 100% backward compatible with
> previous logindomainlist implementations.
>
> Please let me know if you have any troubles with it.
>
>
> See attached for the patch.tar.gz.
>
> I created it against sqwebmail-3.5.0.20030215, so you'll need to install that
> version.
>
> You shouldn't need automake for this one, since I'm not creating any new
> defines/constants.
>
> --
> Jesse Guardiani, Systems Administrator
> WingNET Internet Services,
> P.O. Box 2605 // Cleveland, TN 37320-2605
> 423-559-LINK (v) 423-559-5145 (f)
> http://www.wingnet.net
>
> We are actively looking for companies that do a lot of long
> distance faxing and want to cut their long distance bill by
> up to 50%. Contact [EMAIL PROTECTED] for more info.
>
>
