Hi Andy, > The big gotcha is that although we can handle SMTP with matchers and mailets > delivering locally into different repositories depending upon recipient > address hostname we need to be able to identify the domain (and hence the > credentials) of the authenticating user during SMTP AUTH, and POP3 log-in. *nods*
> Trivially you can work around this by making some small changes which use > the full [EMAIL PROTECTED] or user.domain as the username, others have done this > sucessfully in the past. Yeah, I thought about this one, too, but somehow this isn't "nice" ;) > For completeness though we need to implement proper IP based virtual > hosting, whereby James can assume the domain from the (local)IP address of > the socket, and we can then assign user domains to IP addresses. > > I did start this, and I believe that some of the work I did in preparation > has been commited to the HEAD, but I lost it when my drive underwent a nast > head-crash :-( from what I remember there are few gotchas, but you may have > to override some of James' global settings with multiple local ones based > upon socket IPs. > > If you see what I mean. I see. I thought about setting up multiple services SMTP and POP3 services, each listening to another IP address and using it's own user repository and mail repository. For SMTP, one then would need a "master" SMTP service which has several relay entries which deliver mail for the virtual domains to the appropriate SMTP service. But this scenario breaks for local delivery and POP3. So your approach sounds a lot better. Each service has to map a specific incoming address to a virtual domain name which, in turn, has to be used to access the specific repositories. The down side on this is, that one really needs a separate IP address for every domain that is handled. So, the decision about pros and cons doesn't seem to be over yet ;) Scratching head, Lev. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
