----- Original Message -----
From: "Kurt Bigler" <[EMAIL PROTECTED]>
To: "Jesse Guardiani" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, February 26, 2003 8:16 PM
Subject: Re: [sqwebmail] new file proposal


> on 2/26/03 7:40 AM, Jesse Guardiani <[EMAIL PROTECTED]> wrote:
>
> [snip]
>
> > Value         Meaning
> > ----------    -------
> > allvirtual    default to displaying a hidden field with the value
> >               of HTTP_HOST. This way, a server that runs all virtual
> >               domains wouldn't have to enter a separate record in
> >               the logindomainlist file for each domain. The
> >               logindomainlist would 'overload' or 'override' the
> >               default (which is to use HTTP_HOST as the login domain).
> >
> > vpopmail      default to setting the TCPLOCALIP environment variable
> >               to facilitate automatic vpopmail IP-alias domain support.
> >               This would require that IP-alias support is already
> >               compiled into vpopmail.
>
> Is this analogous to VPOPMAIL_DOMAIN, but for the IP-based hosting side of
> things?  If so I am just wondering whether this is another case of doing
> something on the IP side but omitting a trivial counterpart on the
> name-based side.  But this it out of my territory, so I just had to ask.

For some perspective, this vpopmail field is the driving idea behind all of these 
patches. I needed a solid way to implement
vpopmail IP-alias support in sqwebmail, and I figured that the only real way that I 
could get away with it would be to write IP and
DNS alias support for all of the non-vpopmail people first. (Plus, it provides a 
fallback option if I can't get it working)

I tried to implement vpopmail IP-alias support a few months ago to no avail. I 
couldn't find where it was failing (all I should have
to do is set the TCPLOCALIP environment variable equal to SERVER_ADDR... but it didn't 
work in my tests). Hopefully I can solve the
problem before these patches make it into the next release, but if not, at least I'll 
have my fallback option and my boss won't kill
me. :-]

Yes, it's analogous to VPOPMAIL_DOMAIN, but automatic. You don't have to configure 
anything in Apache. Instead, all of the
domain->IP mappings are handled in a program called 'vipmap', and stored in an SQL 
database.

There isn't a such thing as DNS aliasing in vpopmail. It's largely unnecessary. I 
provide it in my patches as a convenience, and
because it was suggested by you to compare the second field against the HTTP_HOST 
variable, and that actually worked beautifully
without any nasty side affects. I thought, "Hey! Why not!". (The famous last words)


>
> -Kurt
>
> >
> > Can anyone think of anything else that might make a good default here?
> >
> > I'm generally looking for feedback on the idea, and how many people would
> > use it, and if anyone can think of a better way to implement it.
> >
> > Also, I'd like to note that this COULD become a compile time flag, rather
> > than a flat file, but I like being able to change my defaults without
> > recompiling, so I'm leaning toward implementing it as a flat file.
> >
> > Thanks!
> >
> > --
> > 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.
> >
> >
> >
> >
>
>
>


Reply via email to