On 11/07/2005, at 9:09 AM, Jérôme Blion wrote:
Hello,If I understood correctly the process, the belonging to a local or virtual domain is done by checking the presence of the domain in locals or hosteddomains.Am I right ?
Yes. If a domain is in hosteddomains a user account matching the full email address is looked for. If a domain is in locals the domain is stripped off and a user matching the remaining portion is looked for. A domain cannot be in both.
The thing I would like to try is to first try an authentication with a local user (name only)... if not found, try with virtual user (full address)... if not found, final error. Finally, I would only need locals file to reference all domains Courier needs to manage. So I could have virtual and locals users mixed in same domains. and local users for "virtual accounts".
Courier won't let you do this without a bit of work, it's not a really useful configuration for most people. Could be done if you write your own auth modules I suppose, ones that check the virtual domain and then checks for a normal user, you'll have to specify all domains as hosteddomains though. Defining aliases for all the 'global' users in aliasdir works for me, though I only use it for postmaster.
I didn't find the files where the differenciation is done before giving the user to the authentication module ? Could you open my eyes ? What are the consequences of this modification, except performance decrease ?
It's in there somewhere, though I can't recall where. Basically if you have test.com in locals and you get an email to [EMAIL PROTECTED] then courier will look for a user called user1, whereas if test.com is in hosteddomains courier looks for a user called [EMAIL PROTECTED]
I can't think of any consequences myself, Sam might chip in if he can see an obvious problem.
-- Phillip Hutchings [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
