Hmmm..... the expressed need is getting lost here. Let me try again.

Qmail (ick...) allows for multiple virtual domains, distinguished
one from the other by using a different I.P. address for each domain.

POP & IMAP (let's use POP for this example) clearly know which IP address
that is used for a login and authenticate, e.g.:
Domain #1 of Machine A
---
srv9-meb# telnet mail.boxpower.tld 110
Trying 10.1.166.100...
Connected to mail.boxpower.tldm.
Escape character is '^]'.
+OK Hello there.
--- ---------------------------------  <----- distant machine connected
Domain #2 of Machine A
---
srv2-meb# telnet webmail.rtmxyz.tld 110
Trying 10.1.160.10...
Connected to webmail.rtmxyz.tld.
Escape character is '^]'.
+OK Hello there.
---- ------------------------------  <----- distant machine connect too!

Both I.P.'s are on the same machine, but of course DNS, et. al., knows
how to resolve those names to I.P.s     WE ALL KNOW THIS.  Alos, of course,
this example is looking in from the outside. However, on the inside there
*must* be a way to determine what I.P. address was used to get in....

So, are you telling me that the 'couriertcpd' (who *could* be told to ONLY accept
 on certain I.P.'s but is usually allowed to accept connections on any)
...cannot *tell* what I.P. address was used to get into it?
If so, I find this hard to believe.

Why?

Because 'couriertcpd' already sets a shitload of ENVIRONMENT variable before
running *program* including:  TCPLOCALIP and TCPLOCALHOST (looked up in DNS).

So, I was trying to learn if anyone out there had gone to the trouble to
'enhance' authdaemond.mysql (specifically) so that it would look at these
variables, and possibly set the DEFAULT_DOMAIN env. var. to the FQDN-TCPLOCALHOST
or some such as that........

Randy






Sysop wrote:
> 
> Bill Williamson wrote:
> 
> >Someone else asked this question, and the short answer is, it's not
> >possible.
> >
> >Slightly longer version:
> >When you connect to imap/pop3/smtp, you connect via IP address.  That is
> >all.  If you look at the session, you never see "am I talking to
> >mail.bubba.com?", just "here's my user and pass, let me in."
> >
> >The reason you can do this with a web site is that in the http request
> >header is the exact url that is typed in (servername and then file
> >location).  The web server can parse that out and return the correct page.
> >In essence you're saying "Hey, i want page index.html from www.bubba.com."
> >
> >There is no way around this without making your own protocol, which nothing
> >will support, except a client you make.  The server never sees what was
> >typed in for mail server, it's resolved by the client machine into an IP
> >address, and sent off.
> >
> >----- Original Message -----
> >From: "Randy Lewis (Kenneth R. Lewis)" <[EMAIL PROTECTED]>
> >To: "Courier Users Group" <[EMAIL PROTECTED]>
> >Sent: Thursday, January 24, 2002 3:03 PM
> >Subject: [courier-users] I.P. based (virtual) multiple Domains ...
> >
> >
> >>Has anyone implemented I.P. based multi-domains.
> >>
> >>Very specifically, I want the notion of DEFAULT_DOMAIN (as optionally
> >>defined in etc/authmysqlrc) to be determined from the I.P. address
> >>locally as one of many aliased I.P. addresses.
> >>
> >>For example:
> >>
> >>If I have 10 aliased I.P. address on a machine, each DNS mapped
> >>to names like:  mail.someplace.com
> >>                mail.otherplace.com
> >>                .
> >>                .
> >>                mail.yetanother.com
> >>
> >>... I would like authentication by a user through one of those
> >>aliased I.P. addresses to be able to just authenticate
> >>as 'bob' and if he is listed in one of those domains (on the
> >>MySQL user database for that domain) then his auththentication
> >>will succeed due to the DEFAULT_DOMAIN getting set to his
> >>domain.
> >>
> >>Let me know if this is being done somewhere. I'd like to
> >>use that approach for multiple domains here.
> >>
> >>Randy
> >>
> >>_______________________________________________
> >>courier-users mailing list
> >>[EMAIL PROTECTED]
> >>Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
> >>
> >>
> >
> >
> >_______________________________________________
> >courier-users mailing list
> >[EMAIL PROTECTED]
> >Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
> >
> Easist way to fix.  Change your usernames to bob@domain or
> [EMAIL PROTECTED]  that way bob for domainA is different than bob from
> domainB.  Works great for me, I have 5 or so domains pointed to a SINGLE
> IP address, and some of the accounts on each domain have the same name...
> 
> _______________________________________________
> courier-users mailing list
> [EMAIL PROTECTED]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to