on 2/21/03 1:56 PM, Jesse Guardiani <[EMAIL PROTECTED]> wrote: > On Friday 21 February 2003 16:22, Kurt Bigler wrote: >> on 2/21/03 12:44 PM, Jesse Guardiani <[EMAIL PROTECTED]> wrote: >>> On Friday 21 February 2003 15:26, Kurt Bigler wrote: >>>> on 2/21/03 11:33 AM, Jesse Guardiani <[EMAIL PROTECTED]> wrote: >>>>> On Friday 21 February 2003 13:58, Kurt Bigler wrote: >>>>>> on 2/21/03 10:07 AM, Jesse Guardiani <[EMAIL PROTECTED]> wrote: >>>>>>> On Friday 21 February 2003 11:55, Dale wrote: >> > > <snippety snip snip> > >>> Can you currently log into IMAP or POP3 on your domain without specifying >>> [EMAIL PROTECTED] as the userid? >> >> Absolutely, but of course it is not a login to IMAP or POP3 but into a >> Maildir, whose contents could have been put there by any means. > > So, you've never used POP3 or IMAP? Just sqwebmail?
No, I was just clarifying in case there was some feature of sqwebmail that I didn't know about for acting as a POP3 or IMAP client. I also know there are POP3/IMAP clients that will serve into Maildir's - and I want to find one of those. Actually it would be great to integrate hotmail-like POP3 access for multiple accounts into a single webmail login. Has anyone managed to do that? (Potential new thread here.) > >> So yes, I started by using the logindomainlist feature, so right away >> entering [EMAIL PROTECTED] was not necessary, but I still had to select the >> domain from the popup list. But then I changed sqwebmail.c so that it >> would set a default value for the popup list by recognizing the list item >> that matched HTTP_HOST with "webmail." prepended. As I said, not a general >> solution yet. >> > > <snip> > >> I suspect that the same configuration file could specify either a name or >> an ip, and accordingly you would match it against either SERVER_ADDR or >> HTTP_HOST. Once you do a lookup in either case you are determining a login >> domain NAME, so the rest of the implementation should be identical. > > Hmmm. That's not a bad idea. I don't remember real clearly what the HTTP_HOST > variable looks like, but I could easily do a comparison against both > variables. > > Good idea! > >> >> Can I get you to buy into the idea that this can all be done using >> logindomainlist? Use records of one of two formats: >> >> logindomain:http_host:popup_flag >> logindomain:server_addr:popup_flag > > No. I want to keep the two files separate for compatibility reasons, as well > as functionality reasons. I like the idea of "defaulting" the domain drop down > on the login page if the 'logindomainlist' file exists. I think that would > be a bit harder to implement if I overload the 'logindomainlist' file for this > new functionality. I think it might not be harder - might actually be the easiest way. (Sent you some details off-list.) -Kurt Bigler
