 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
7 messages in net.sourceforge.lists.courier-users[courier-users] Re: Let the users man...| From | Sent On | Attachments |
|---|---|---|
| Florian Lindner | Apr 8, 2003 8:55 am | |
| Sam Varshavchik | Apr 8, 2003 10:21 am | |
| Florian Lindner | Apr 8, 2003 4:28 pm | |
| Sam Varshavchik | Apr 8, 2003 5:03 pm | |
| Florian Lindner | Apr 9, 2003 2:07 am | |
| Sam Varshavchik | Apr 9, 2003 7:29 am | |
| Markus Gebert | Apr 9, 2003 10:24 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [courier-users] Re: Let the users manange email boxes... | Actions... |
|---|---|---|
| From: | Sam Varshavchik (mrs...@courier-mta.com) | |
| Date: | Apr 9, 2003 7:29:16 am | |
| List: | net.sourceforge.lists.courier-users | |
Florian Lindner writes:
Am Mittwoch, 9. April 2003 02:01 schrieb Sam Varshavchik:
Florian Lindner writes:
The IMAP server has nothing to do with any of the above. When the IMAP server receives a userid and a password, they are checked, and the corresponding maildir is opened.
How mail manages to arrive in those mail accounts, and how those accounts are created in the first place, is not something that the IMAP server really cares about.
Configure Courier-IMAP to use LDAP or MySQL. Write your own scripts that create maildirs, and insert the corresponding account records into LDAP or MySQL. That's it.
There is a big misunderstanding. The mail is already in the maildir and I want to make the user able to configure accounts to fetch these emails.
Any message in a maildir may be retrieved to whoever logs into that maildir. There is no magical fairy that allows one login to download only some messages in the maildir, and prevents him from downloading other messages, and another login to download the other messages.
If you want to only create another login id that opens the same maildir, and sees, essentially, the same thing, then just go ahead and do it. But, then again, this has nothing to do with the IMAP server.
So it seems to be impossible to make authentification where one file for is responsible for only one virtual domain?
No, it's not, but once again this has nothing to do with the IMAP server. If you want to write some account management script that allows someone to create and remove login IDs, again that's something that the IMAP server does not care about. All it cares about are: here's a list of login ids, passwords, and maildirs. That's it. Who creates those login ids, and how they are created, is not something the server cares about.
I know that I can edit the global user access lists with some scripts. But I don't want to to do that. I just want to know if this is possible with Courier.
There are no scripts to do that with Courier. This is not exactly a commonly-used configuration. Every system is different. You need to write your own scripts.
That's got something to do with the IMAP server, at least with the authentification mechanism.
Only as far as "is the login id, and the password valid". That's all the IMAP server cares about.
Now a user tries to log with the username "name" at the domains "example.com".
There is "username X in domain Y", as far as IMAP is concerned. The only thing you have is "login A, password B". Login "A" may, in fact, be "userC@domainD", however as far as the IMAP server is concerned it is an arbitrary login ID, that's not interpreted in any way.
The IMAP server looks up the user which is associates with example.com. Now
No it doesn't. It looks up login "A", password "B".
it reads the config file in the users homedir and opens the maildir which is associated to "name".
No it doesn't.
Do you understand?
Do you?