5 messages in net.sourceforge.lists.courier-users[courier-users] hosteddomains
FromSent OnAttachments
Gordon MessmerOct 24, 2006 10:21 am 
Sam VarshavchikOct 24, 2006 3:24 pm 
charles uchuOct 26, 2006 8:23 pm 
David GomillionOct 27, 2006 6:48 am 
Alessandro VeselyOct 27, 2006 11:53 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] hosteddomainsActions...
From:Gordon Messmer (yiny@eburg.com)
Date:Oct 24, 2006 10:21:53 am
List:net.sourceforge.lists.courier-users

It's come up before that "aliased" hosteddomains sometimes don't do what users expect them to. The man page for "makehosteddomains" indicates that if "mail.domain.com" is aliased to "domain.com", then an address of the form <addr@mail.domain.com> will be rewritten as <addr@domain.com> and delivered to the local mailbox for that name. The consequence seems to be that if <addr@domain.com> is an alias, delivery fails. Additionally, if "address" has dot-courier files in their home directory, such that <addr@domain.com> is a valid address, <addr@mail.domain.com> doesn't work, either.

How much work would be required to modify courier such that when an aliased hosteddomain is found, the address is rewritten, and lookups begin over again, so that aliases and dot-courier files work? Which code would need to be modified?