10 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Multible Mail Dom...
FromSent OnAttachments
tp...@netmaster.dkJun 21, 2007 12:47 am 
Sam VarshavchikJun 21, 2007 3:58 am 
tp...@netmaster.dkJun 21, 2007 5:15 am 
ScottJun 21, 2007 8:32 am 
Jeff JansenJun 21, 2007 7:50 pm 
tp...@netmaster.dkJun 22, 2007 12:26 am 
Jeff JansenJun 22, 2007 3:25 am 
tp...@netmaster.dkJun 22, 2007 3:40 am 
Jeff JansenJun 22, 2007 8:23 am 
tp...@netmaster.dkJun 24, 2007 11:07 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] Multible Mail DomainsActions...
From:Jeff Jansen (tech@sil.org)
Date:Jun 22, 2007 3:25:41 am
List:net.sourceforge.lists.courier-users

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

tp@netmaster.dk wrote:

A few questions left. I only have a locals file – I don’t have a hosteddomain file. In my locals file I have the 3 domains I host. I have a logindomainlist file with the 3 domains I host. This way sqwebmail login dialog page shows a dropdown to select domain. When a user uses brings up sqwebmail login dialog page and enters a userid and selects a domain from the dropdown I can see from the system log that the user is trying to log in to a system account that includes the domain name. How is that possible as I don’t have a hosteddomain file?

The 'locals' and 'hosteddomains' files just tell courier how to handle addresses - whether to include the domain as part of the user's name or not. They have nothing at all to with what names people use when they log in. I can go to your web site and try to log in as "lin@kernel.org". And the log will show that I tried using that username. But of course it will fail, since there is no user called "lin@kernel.org" on your box.

Since you put your three domains into the 'logindomainlist' file, sqwebmail appends which ever one you choose to the user name when you try to log in. If your domains are in 'locals' then you do not want this since your users have to log in without the domain as part of their name. Delete that file and tell all your users to log in using only their username without the domain.

So 'use@domain1.com' will log in as 'user1'. And 'use@domain2.com' will log in as 'user2'. Any user whose domain is listed in the 'locals' file will log in using only the username part of their address.

You suggest that I can alias ‘use@domain1.com’ to a system accout ‘user’ How can I do that?

There's an 'aliases' folder in your courier 'etc' directory. Create a file in there (name the file whatever you want) and list all your aliases in there in the form:

alias: account

So if you want "use@domain1.com" to deliver to a system user called 'user' then the file would put:

use@domain1.com: user

in the file. Then run the command 'makealiases'.

Now mail addressed to "use@domain1.com" will be delivered to 'user'. This user will log on simply as 'user'.

But remember, for any domains in 'locals' all the username portions need to be unique since courier will ignore the domain part of the name. If you want 'use@domain1.com' and 'use@domain2.com' to be different you need to move one of these domains to 'hosteddomains'.

HTH

Jeff Jansen

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGe6O8GfIHDMaiC9cRAvKvAJ9Sp/TM+8b25FCi/VMKL0u81tYqXgCfdZrS KwLfgoXeJctrvKquEpq2ZNY= =llfc -----END PGP SIGNATURE-----