dovecot-system-user
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| dovecot-system-user [2016-04-12 22:49:59] – Externe Bearbeitung 127.0.0.1 | dovecot-system-user [2021-06-08 18:44:34] (aktuell) – manfred | ||
|---|---|---|---|
| Zeile 1: | Zeile 1: | ||
| + | ====== Dovecot System User ====== | ||
| + | |||
| + | System users are typically defined in '/ | ||
| + | |||
| + | System users usually have their own separate user IDs (UIDs). This is good from security point of view, because it means that the kernel will also prevent users from accessing each others' | ||
| + | |||
| + | If the users have direct write access the mail files (eg. the users have shell access), they can easily cause all sorts of mailbox corruptions. That may generate all kinds of error messages to Dovecot' | ||
| + | sometimes difficult to tell if there really is a problem or if user is just doing something stupid. | ||
| + | |||
| + | If users are going to access the mailboxes with other software than Dovecot, it's important to make sure that their mailbox accesses are compatible. This mostly means that with mboxes you must make sure that everyone uses the "same locking methods in the same order" (MailboxFormat.mbox.txt). | ||
| + | |||
| + | ==== Authentifikation ==== | ||
| + | |||
| + | Admins often wish to use different passwords for IMAP and POP3 than for other | ||
| + | services (eg. SSH), because IMAP and POP3 clients often send the password | ||
| + | unencrypted over the internet without even bothering to give users any | ||
| + | warnings. Dovecot can easily support non-system passwords for system users. | ||
| + | |||
| + | If you wish to use system passwords, you'll want to use one of these passdbs: | ||
| + | |||
| + | * //PAM// [PasswordDatabase.PAM.txt]: | ||
| + | * //BSDAuth// [PasswordDatabase.BSDAuth.txt]: | ||
| + | * //Passwd// [AuthDatabase.Passwd.txt]: | ||
| + | * //Shadow// [PasswordDatabase.Shadow.txt]: | ||
| + | |||
| + | If you wish to use non-system passwords, you can use pretty much any of the | ||
| + | Dovecot' | ||
| + | installations you'll probably want to use " | ||
| + | |||
| + | "User database" | ||
| + | |||
| + | ==== Mail Location ==== | ||
| + | |||
| + | Usually UNIX systems are configured by default to deliver mails to | ||
| + | "/ | ||
| + | use these, or use " | ||
| + | |||
| + | Dovecot detects the mailbox format and location automatically if " | ||
| + | |||
| + | See (MailLocation.txt) for more information how to configure the mailbox location. Below are the highlights for mbox and maildir. | ||
| + | |||
| + | ==== mbox ==== | ||
| + | |||
| + | The "/ | ||
| + | multiple mailboxes however, so Dovecot needs some directory where to store the | ||
| + | other mailboxes. Typically they' | ||
| + | All of these locations are included in mailbox location autodetection. You can | ||
| + | specify them manually with: | ||
| + | |||
| + | mail_location = mbox: | ||
| + | |||
| + | Remember that the first path after ' | ||
| + | try to give ' | ||
| + | you really want to store mails under '/ | ||
| + | |||
| + | If you're also using other software than Dovecot to access mboxes, you should | ||
| + | try to figure out what locking methods exactly they' | ||
| + | " | ||
| + | section in " | ||
| + | |||
| + | ==== Maildir ==== | ||
| + | |||
| + | Maildir is typically stored in " | ||
| + | manually with: | ||
| + | |||
| + | mail_location = maildir: | ||
