- dovecot - dovecot.org

[Dovecot] Default Mailbox
by Feris Thia 01 May '07

01 May '07

Hi All, What is the default mailbox for Dovecot ? Is it mbox or Maildir ? Can I set my mailbox for pop3/imapd to /var/spool/mail/USER ? Regards, Feris

1 0

[Dovecot] PAM, Active Directory, all users mapped to uid=0
by Matt Zukowski 01 May '07

01 May '07

I'm having a problem with authentication using PAM, connected on the back end to Active Directory. PAM authentication itself works fine. We can log in to the machine using AD credentials without any problems. Each user is automatically mapped to uid's in the 10000+ range. However, for some reason when the user logs in via dovecot, the user's uid and gid are showing up as 0. For example: dovecot: May 01 11:22:47 Info: auth(default): master out: USER 3 mzukowski uid=0 gid=0 home=/home/URBACON/mzukowski dovecot: May 01 11:22:47 Error: Logins with UID 0 not permitted (user mzukowski) Is there a reason why dovecot might not be resolving the uid and gid correctly? PAM itself seems to be doing this right, since when I log on to the machine as an AD user, their UID shows up correctly as 10000+. Thanks, Matt. -------------- This e-mail message is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited. Le contenu du pr'esent courriel est privil'egi'e, confidentiel et soumis `a des droits d'auteur. Il est interdit de l'utiliser ou de le divulguer sans autorisation.

1 1

[Dovecot] dovecot-ldap and ldap_result() failed.
by Tan Shao Yi 01 May '07

01 May '07

Hi, I have configured dovecot for auth_bind against an LDAP server on the localhost and I'm seeing the following error in my dovecot logs: dovecot: Apr 30 09:03:18 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Apr 30 09:03:27 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server ... and so on ... When I turned on LDAP logging, this was what slapd logged. Apr 30 09:05:00 recess3 slapd[14387]: [ID 848112 local4.debug] conn=3555 fd=11 ACCEPT from IP=127.0.0.1:47299 (IP=0.0.0.0:389) Apr 30 09:05:00 recess3 slapd[14387]: [ID 215403 local4.debug] conn=3555 op=0 BIND dn="cn=root,o=home" method=128 Apr 30 09:05:00 recess3 slapd[14387]: [ID 600343 local4.debug] conn=3555 op=0 BIND dn="cn=root,o=home" mech=SIMPLE ssf=0 Apr 30 09:05:00 recess3 slapd[14387]: [ID 588225 local4.debug] conn=3555 op=0 RESULT tag=97 err=0 text= May I know what is causing Dovecot to log that it Can't contact the LDAP server when slapd does see the incoming connection. Strangely, everything is working fine, my users are able to authenticate against LDAP; the UIDs, home directories, quotas etc are all picked up correctly. It's just the annoying auth(default) errors that keep popping up every 20 seconds or so. Thanking in advance if anyone has any ideas. Cheers.

4 5

[Dovecot] dovecot for imap
by dhottinger＠harrisonburg.k12.va.us 30 Apr '07

30 Apr '07

I have been using uw-imap on my mailserver. I tried briefly to use dovecot with the default config. It seem to work faster, but users imap folders (user accounts are in openldap) disappeared. Is there a sample config somewhere I can look at to get some idea how to configure dovecot so all the imap folders users created will appear when I make the switch? Most of my users login via Horde. Server is an FC6 box, dovecot installed via yum install. -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools

6 11

[Dovecot] Sieve notify error?
by Láďa 30 Apr '07

30 Apr '07

Hi, I am playing with Sieve, everything is working nice except notify method. Source script looks like this (generated with avelsieve): require ["fileinto","envelope","reject","vacation","imapflags","relational","compara tor-i;ascii-numeric","notify"]; if #hashed-avelsieve-source true { keep; notify :method "mailto" :options "xxx(a)xxx.xx" :low :message "Nova zpráva."; } but with no success. Message is delivered fine, but notification is not sent. Deliver logs only this: deliver(xxx(a)xxx.xx): Apr 28 20:05:23 Info: sieve runtime error: Notify: Generic Error Thanks for any ideas how to get this working. Láďa

2 2

[Dovecot] Auth(default): add one userdb - what does this mean?
by Wade Smart 30 Apr '07

30 Apr '07

I got dovecot to start but then I had to reboot and now Im receiving errors: Apr 27 19:48:18 wadesmart dovecot: auth(default): You'll need to add at least one userdb Im still following the steps from http://wiki.dovecot.org/BasicConfiguration wade

2 1

[Dovecot] Doubled subjectlines in mailfolders
by Götz Reinicke 30 Apr '07

30 Apr '07

Hi, after the upgrade from 0.99 to 1.0rc15 on our RHEL 5 Server I noticed, that some of my mailfolders do double the mails subject line in the listview of thunderbird. The mail itself isn't doubled and the second mail contains a different content from a mail that didn't show up in the list. SO it seams, that only the subject line is somehow wrong. Any ideas or tips? I haven't found anything on that googling or in the list archive; but maybe I'm searching with the wrong syntax ... Regards Götz

2 2

Re: [Dovecot] New install on Ubuntu Fiesty 7.04
by Wade Smart 29 Apr '07

29 Apr '07

Ok. I started with the example file and edited it as the Quick Start suggested and here is the final working result: wadesmart@wadesmart:~$ sudo dovecot -n Password: # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_extra_groups: mail mail_location: ~/Maildir maildir_copy_with_hardlinks: yes auth default: passdb: driver: passwd-file args: /etc/passwd.dovecot userdb: driver: passwd-file args: /etc/passwd.dovecot wadesmart@wadesmart:~$ I was able to login in via telnet like the tutorial said. In my Maildir/new I had 884 new messages. The tutorial said to access the Inbox, and I did and could. However, then my 884 messages were gone!!! I do not understand what the heck happened. Did I just loose all my messages?

4 10

[Dovecot] dovecot sendmail mysql no inbox error
by jan gestre 29 Apr '07

29 Apr '07

hi guys, we are experiencing this particular problem with one of the webmail server we manage. the server is using dovecot as pop3 and imap server while sendmail is being used as mta. when this user tries to login via telnet, this is what i've got: $ telnet localhost pop3 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. +OK dovecot ready. user user1 +OK pass password +OK Logged in. -ERR No INBOX for user. Connection closed by foreign host. when i looked at the maillog i saw this: Apr 25 20:52:32 samplemail pop3(samplemail): File isn't in mbox format: /var/mail/samplemail Apr 25 20:52:32 samplemail pop3(samplemail): File isn't in mbox format: /var/mail/samplemail Apr 25 20:52:32 samplemail pop3(samplemail): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2007-04-25 20:52:32] tried google but not much of help, they just suggested to update or replace dovecot. i already update dovecot and made some changes to default_mail_env parameter, still the same result. dovecot version is 0.99 on a fedora 4 box any idea?

2 7

[Dovecot] Shared mailbox plans
by Timo Sirainen 28 Apr '07

28 Apr '07

** Configuration ** namespace shared { prefix = user/%u/ location = maildir:/home/%u/Maildir:INDEX=~/Maildir/shared-indexes } So the only difference to how it's configured now is that %u is expanded to whatever user whose mailboxes we're accessing. ACL plugin then uses that user as the owner in the namespace's mailbox owner. Since the default ACL is to not give any access to non-owners, the mailboxes without dovecot-acl files will be invisible. If ACL plugin isn't loaded, I suppose the mailboxes can be accessed if the process has filesystem permissions to access them. ** ACL vfile speedups ** Currently it stat() the dovecot-acl file a bit too often. It doesn't do it more than once a second, but there's really no need to do it even that often. I guess it could be changed to be configurable with default being something like 5 minutes. Create a new dovecot-acl-list file which lists all the mailboxes which have dovecot-acl file with "l" right (visible in mailbox list) to any non-owner. It could be in "<timestamp> <mailbox name>" format. This allows other users to quickly get a list of mailboxes that are potentially visible to them. They still need to read the dovecot-acl file from the mailbox before knowing for sure. If the dovecot-acl-list file doesn't exist or if at any time any timestamp doesn't match dovecot-acl file's current mtime, the file is rebuilt by looking into all mailboxes' dovecot-acl files (if the reading user has write permissions to the directory, otherwise it just keeps it in memory). Whenever Dovecot modifies dovecot-acl file, it also updates the dovecot-acl-list file. This means that the file can contain stale data only if a new dovecot-acl file is created without updating dovecot-acl-list file. Even that will be fixed the next time the owner does a LIST (or select the mailbox, or anything that causes its dovecot-acl file to be stated), which causes ACL plugin to notice the desync. There exist also global ACL files. These need to be included in the dovecot-acl-list file as well. The only issue with them is that user doesn't necessarily have a mailbox even though the global ACL file exists. So these need to be marked somehow in the dovecot-acl-list file as non-existing mailboxes. Then if user creates a mailbox with such name, the mark is removed. Deleting the mailbox puts the mark back. After the visible mailbox list has been figured out once, only the dovecot-acl-list file needs to be stat()ed once in a while instead of all the mailboxes' dovecot-acl files. ** User list ** The next problem is how to quickly get a list of users whose mailboxes are visible to ourself so they can be included in mailbox list. I couldn't figure out anything new and great for this, so the options are the same as in http://dovecot.org/list/dovecot/2006- October/017082.html Although for dict backend I could make it a bit more secure. Currently dict has "private" and "shared read-write" options to store the data with. The shared users list could be done with "shared read- only". ** Virtual domains ** ACL plugin could support virtual "group=@domain" to give access to usernames ending with @domain. Or perhaps the group could support wildcards? "group=*@domain"? That way it wouldn't be required to have @ really in the username. Anyway, I think "anyone" should then be aliased to "group=*@domain". If there are multiple virtual domains and you let the users manipulate the ACLs themselves, I'd think they want anyone to mean anyone within my domain (my organization) rather than really anyone who just happens to be using the same server. I think it would also be annoying if anyone could really force their own mailboxes to be visible to a lot of people. That could be used for spamming as well.. If administrator wants to have global mailboxes that really are visible to all domains, they could be done with public namespaces (not shared). ** Quota ** This is kind of problematic. The behavior depends entirely on quota backend: - Filesystem quota of course tracks the quota based on the file's owner - Maildir++ quota counts the quota for the user whose maildir the shared mailbox exists in. This means it also requires filesystem level access to maildirsize file, otherwise the quota updating happens sometimes later when the quota is recalculated. - Dict quota.. I think it'll need a new path for each shared mailbox, which is modifiable by any user. So while your own quota would exist in private/quota/storage, the shared mailboxes' quota would exist in shared/quota/storage. This means that the dict quota needs to be able to know what mailboxes the current user has shared. It also gets a bit tricky to update the quota if mailbox is unshared. The quota could be tracked individually for each mailbox also, but I'm not sure if that's such a great idea either. Perhaps a new quota backend could be implemented to make all this easier. The mail sizes could be tracked in index file, so getting the size of a mailbox could be done simply by reading the value from the index file's header. With mailbox list indexes (in CVS HEAD) they'd all be listed in a single mailbox.list.index file, which would make summing them up really fast. This would require that users don't use private index files for shared mailboxes though. But if the users don't have shell access the shared index files are probably a good idea anyway (at least from performance point of view). ** Symlink shares ** Currently the only way to implement shared mailboxes among users is for administrator to create symlinks. This will be possible in future too with a configuration like: namespace shared { prefix = Shared/ location = maildir:~/Maildir/shared-symlinks:INDEX=~/Maildir/ shared-indexes } The "owner" ACL won't match anyone. So it'll work exactly as it does now.

6 15