2 messages in net.sourceforge.lists.courier-usersRe: [courier-users] locals vs. hosted...
FromSent OnAttachments
chester c youngSep 23, 2004 10:11 am 
Gordon MessmerSep 23, 2004 11:26 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] locals vs. hosteddomainsActions...
From:Gordon Messmer (yiny@eburg.com)
Date:Sep 23, 2004 11:26:43 am
List:net.sourceforge.lists.courier-users

chester c young wrote:

trying to understand locals and hosteddomains, is the following correct?

locals is a single file; hosteddomains is a directory whose files are catenated together.

Yes.

hosteddomains is a superset of locals.

No. A domain is either one or the other, not both.

However, "esmtpacceptmailfor.dir" contains all of the domains in both as well as domains for which that instance of Courier will accept and relay mail (backup MX, for example), so it's a superset of locals and hosteddomains.

the format of each is the same, typically mydomain.com .mydomain.com the second representing all subdomains of mydomain.com

I'm not sure if hosteddomains accepts the second example.

hosteddomains must include each hostname with DNS AAAA, A or MX to this machine. (locals, if no hosteddomains).

Also no, explained above.

the primary difference is that mail accounts using local domains do not need to specify the domain as part of the mail address. conversely, there cannot be two local domains having the same mail user, eg, there cannot be use@domain1.com and use@domain2.com.

For clarity: if both domain1.com and domain2.com are listed in the "locals" file, then use@domain1.com and use@domain2.com are the same account.

hosteddomains is sync'd with makehosteddomains; locals is sync'd with makealiases.

Nothing syncs locals, AFAIK. You do, however, have to add any new domain to esmtpacceptmailfor.dir and run "makeacceptmailfor".