Re: [Exim] multiple domains (envelope-to header)

Αρχική Σελίδα
Delete this message
Reply to this message
Συντάκτης: Dave C.
Ημερομηνία:  
Προς: NOC - KP^2
Υ/ο: Exim List
Αντικείμενο: Re: [Exim] multiple domains (envelope-to header)
On Sat, 27 Apr 2002, NOC - KP^2 wrote:

> I am currently trying to setup multiple domains (real, not virtual) on a
> single exim server. I've searched through the mail list archives for


Er, well, normally the term 'virtual mail' is used to refer to one
server providing seperate email namespaces for multiple email domains.

One thing you have to sort out, is if the user/accounts are real unix
users, what do you do if you have a user in one domain, who wants his
email to be 'joe@???', you create the unix user joe, then
someone else wants 'joe@???' - you cant have two unix users
named 'joe'. Yoiu could use the full email address as the unix username,
but unfortunately, the max length for a domain name is far more than the
usual max length of a unix username.

Hence this sort of thing is normally accompished by 'virtualizing' the
address-space for each domain, so that each domain is seperate from the
others, and also seperate from the unix username space.. One can use
virtual aliasfiles to deliver to different local unix users, this only
virtualizes delivery, pop/imap/etc access would still be in a shared
namespace, or one can fully virtualize it by directly storing mail for
each domain in a different subdirectory, and arranging for the
pop/imap/etc daemons to recognize and work with this structure as well,
either by using multiple IP addresses, one for each domain, or including
the domain-part in the 'username' when accessing the account by
pop/imap/etc..

Basically, the various FAQ's/cookbooks on 'virtual' domains are exactly
what you are looking for. Your distinction of 'real' vs 'virtual'
domains is misguided..

> "multiple domains" and "envelope-to" (will be explained in a bit) but I
> didn't find anything that I could make sense of, though it's probably
> that I don't quite understand all the terminology.
>
> Usernames will NOT be duplicated across these domains. I am storing
> email in the mbox format. All users are real unix users, with nologin
> set for their shell and are hosted on a freebsd 4.5-stable server.
>
> My local_domains line looks like this:
>
> local_domains=*.kulish.com:kulish.com:*.tekengine.net:tekengine.net:loca
> lhost:[10.1.1.247]
>
> An email is then sent, from an external entity, to
> blackhole@???, it ends up in the noc@??? mailbox. I
> assume that I missed a step somewhere along the way, but I can't seem to
> pinpoint what I need to do next. I have included a snippit of the
> headers on that incoming email. It seems the envelope-to: header is the
> problem, but I don't know why it's changing and how to correct this
> behavior.
>
> Thanks for your time.
> If you need any more information, let me know.
> Chris Kulish
>
> -----HEADERS-----
> Return-path: <someone@???>
> Envelope-to: noc@???
> Delivery-date: Fri, 26 Apr 2002 22:12:23 -0500
> Received: from smtp.easydns.com ([205.210.42.50])
>             by cheese.kulish.com with esmtp (Exim 3.36 #1)
>             id 171IdL-000OM1-00
>             for noc@???; Fri, 26 Apr 2002 22:12:23 -0500
> Received: from smtp02.infoave.net (smtp02.infoave.net [165.166.0.27])
>             by smtp.easydns.com (Postfix) with ESMTP id 7E4C24BBFD
>             for <blackhole@???>; Fri, 26 Apr 2002 23:12:00
> -0400 (EDT)
> Received: from someone.rhtc.net ([204.116.1.7])
>  by SMTP00.InfoAve.Net (PMDF V6.0-25 #38777)
>  with ESMTP id <01KH1C1SXX9O9H9SHT@???> for
>  blackhole@???; Fri, 26 Apr 2002 23:11:48 -0400 (EDT)
> Date: Fri, 26 Apr 2002 23:11:49 -0400
> From: Someone <someone@???>
> Subject: msg
> X-Sender: someone@???
> To: blackhole@???
> Message-id: <5.0.2.1.2.20020426231139.00a8dbe0@???>
> MIME-version: 1.0
> X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
> Content-type: text/plain; format=flowed; charset=us-ascii
> X-UIDL: *T2!!ZpK"!g`4"!#4L"!

>
>
> --
>
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
>



--