On Monday 24 February 2003 10:35, Jesse Cablek wrote: > Jesse Guardiani wrote: > > On Sunday 23 February 2003 23:21, Jesse Cablek wrote: > >>Kurt Bigler said: > >>>on 2/22/03 8:37 PM, Jesse Guardiani <[EMAIL PROTECTED]> wrote: > >>>>----- Original Message ----- > >>>>From: "Kurt Bigler" <[EMAIL PROTECTED]> > >>>>To: <[EMAIL PROTECTED]> > >>>>Sent: Saturday, February 22, 2003 10:53 PM > >>>>Subject: Re: [sqwebmail] NEW: domainmap Patch > >
<snip> > > Then the 'logindomainlist' dropdown will still exist, but the > > 'mydomain.com' option will be the default! This makes the > > 'logindomainlist' file even more user friendly, I think. > > Alright, understandable. > Though you can use this patch without the logindomainlist and it will > still work as intended using a hidden form field, correct? Absolutely. It's an either or thing. > > >>I personally would prefer to keep this separate. Then hosted users > >>wouldn't see a dropdown list for my personal domains, and vice versa. As > >>Jesse G said earlier, these 2 lists provide completely different > >>functionality. > >> > >>logindomainlist - gives users a dropdown choice of what domain to use > >>domainmap - dynamically assigns the domain so the user doesn't need a > >>choice > >> > >>Please correct me if I'm wrong on these points? > > > > Not wrong, but missing some information. See above. > > Thanks for the correction - at least this gives alternate uses that can > be used for the documentation ;) Definately. Thanks. <snip> > > I'd like this patch to be as flexible as possible, so if there is a way > > to accomodate mixed system and virtual accounts, I'll implement it. > > Possibly have it only select a default domain and/or put in a hidden > form field with the domain IF it shows up in logindomainlist OR domainmap. Silly me. It already does this! No-one should have any problems using this with system accounts. Just make sure you leave a domain off the 'domainmap' list or make sure you use 'logindomainlist' with 'domainmap' so that you can select the blank option in the drop down. Alternatively, you could set up a subdomain like: system.mydomain.com This would allow you to list 'mydomain.com' in the 'domainmap' file, and still access your system accounts from 'system.mydomain.com' (unless you're using IP-alias mapping, of coarse.) Good notes for documentation. > > With logindomainlist you can still leave it as a blank option - and it > should work fine with system accounts. SO if the domain you're accessing > it from doesn't show up in either, then leave it as normal and allow > full choice up to the user. > > > Thanks for the comments! > > No problem. > > Personally, I don't think I'll use this patch - I see it's functionality > and I probably would have previously, but since I've learned a lot more, > specifically about SSL in httpd then I use https with SqWebMail. httpd > doesn't allow named virtual hosts for https so this functionality > wouldn't much help me. You could always get some IPs for those domains. > > Well I technically 'could' set it up but I'd be getting all sorts of > certificate errors, so I'm probably not going to. Keep up the work > though, I'd like to see it implemented for a time that SSL "may" be able > to support virtual hosts on 1 IP :) Doubtfull. Probably a security risk. Besides, your mail comes into the server unencrypted. Why bother encrypting it just to read it? I use SSL to protect valuable passwords, but I don't see much point in using it to read email. (unless your email account has a valuable password) > > That's nothing this patch can fix! Unfortunately true. Sorry. > > /jesse -- 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.
