1 message in net.sourceforge.lists.courier-users[courier-users] locals plus hosteddom...
FromSent OnAttachments
chester c youngSep 27, 2004 9:17 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:[courier-users] locals plus hosteddomains - a solutionActions...
From:chester c young (ches@yahoo.com)
Date:Sep 27, 2004 9:17:10 am
List:net.sourceforge.lists.courier-users

the goals: 1. users login with account, not email address (need locals) 2. let mail be aliased based on domain (need hosteddomains) 3. be easy to impliment

for example: 1. user logs in as jdoe (not jdoeATd1.com) 2. mail delivered seperately to supportATd1.com and supportATd2.com 3. maintain with authorization, not individual maildrop's

the solution: in locals - add dummy domain dummy.xxx - no real domains in defaultdomain - none - no defaultdomain in me - the wanted name of mail host, eg, mail.mydomain.com in hosteddomains - no domain dummy.xxx - real domains in esmtpdaccecptmailfor - no domain dummy.xxx - real domains in aliases, for each user: - mail - mail, ie, "<addressee> AT <realdomain.com>" - maildrop - "<dn> AT dummy.xxx" in authldaprc: - LDAP_MAIL dn (or uid) - (mail stays as a valid reference, but is not used by courier)

the results: 1. users log in with name -ie, jdoe, not jdoeATdomain.com 2. domain based mail aliasing ie, jdoeATd1.com and jdoeATd2.com delivered correctly 3. all maintenance done through ldap one extra entry needed per user in alias 4. only problem: = if d1.com and d2.com and hosted domains = and u1 and u2 are accounts in those domains respectively = user sends to u2 (not u2 AT d2.com) = u1 assumes u2 AT d1.com = however, mail sent to u2 AT d2.com = but I think this is minor and probably acceptable

if there is a more straightforward way to solve this please forgive me, and thanks for the emailed suggestions.