- dovecot - dovecot.org

[Dovecot] convert plugin created maildirfolder file in root maildir directory
by Justin McAleer 12 Apr '07

12 Apr '07

I've noticed that if a user's maildir gets created by deliver or pop/imap without the convert plugin running, the maildir structure is fine (no maildirfolder file). But, if a user gets converted, there is a maildirfolder file in the user's base maildir directory. As far as I can tell, that doesn't cause any problems, but I just wanted to mention it. I've looked at the code for a while but didn't find why it behaves differently.

2 1

[Dovecot] Connection refused with auth-master after upgrading to Dovecot 1.0 rc 28
by Jason Warner 12 Apr '07

12 Apr '07

Fedora pushed out an update to Dovecot 1.0 rc 28 today. After upgrading, mail isn't delivered to local recipients. My log file is full of error messages similar to the following: Apr 2 12:56:32 mail deliver(user(a)domain.com): net_connect(/var/run/dovecot/auth-master) failed: Connection refused I'm including some snippets from my dovecot.conf file that pertain to the auth-master file: protocol lda { # Address to use when sending rejection mails. postmaster_address = postmaster(a)brashers.com mail = maildir:/home/vmail/mail/%n # Hostname to use in various parts of sent mails, eg. in Message-Id. # Default is the system's real hostname. #hostname = # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/lda mail_plugins = cmusieve mail_plugin_dir = /usr/lib/dovecot/lda # Binary to use for sending mails. #sendmail_path = /usr/lib/sendmail # UNIX socket path to master authentication server to find users. auth_socket_path = /var/run/dovecot/auth-master #auth_socket_path = /home/vmail/mail/auth-master } socket listen { master { # Master socket provides access to userdb information. It's typically # used to give Dovecot's local delivery agent access to userdb so it # can find mailbox locations. path = /var/run/dovecot/auth-master #path = /home/vmail/mail/auth-master mode = 0600 # Default user/group is the one who started dovecot-auth (root) user = vmail group = mail } #client { # The client socket is generally safe to export to everyone. Typical use # is to export it to your SMTP server so it can do SMTP AUTH lookups # using it. #path = /var/run/dovecot/auth-client #mode = 0660 #} } I have been beating my head against this trying to change the permissions to 0777, changing the directory of the socket, changing the auth user, and just about anything else I can find in any thread that relates to this error. Any help would be greatly appreciated.

3 21

[Dovecot] Dovecot deliver agent - dovecot.conf permissions
by Daniel L. Miller 12 Apr '07

12 Apr '07

I started playing with deliver, and saw a permission error in the logs for dovecot.conf. Under my distro install, /etc/dovecot.conf was installed owner/group root, with only user rw rights. I added "other" read privileges and deliver is happy - is this necessary? -- Daniel

3 3

[Dovecot] Comment from OpenLDAP developer regarding "deferring operations"
by Ben Beuchler 12 Apr '07

12 Apr '07

I received this response from a member of the OpenLDAP core team when asking about meaning of the deferred operations I was seeing. Is it possible that this is what I'm seeing, Timo? -Ben --------------------------------------------- I'd note that if your client is performing search + bind on the same connection in an asynchronous manner, then the server behavior as per RFC4511 is undefined, since a server is not supposed to be willing to handle operations intermixed with binds until a bind is concluded. That is, any operation can be multiplexed on a single LDAP connection __except__ binds, which must be serialized. A more appropriate client for that type of operations would need to use at least 2 connections, one for searches and one for binds, and the one for binds should take care of either performing synchronous binds, or in any case to wait for response to a bind before performing another. In case of failure (e.g. timeout) while waiting for bind response, the connection should be trashed (see ldap_unbind_ext(3)) and recreated. This is what is done, for example, by slapd-ldap(5). p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

2 3

[Dovecot] Dovecot Assertion on mail server with POP3 and LDAP authentication
by Tim Alberts 12 Apr '07

12 Apr '07

Running two Fedora 6 systems with all the latest updates as of a week ago. One system is the mail server (sendmail, dovecot), the other is the master (open)LDAP server with the mail server running a slave LDAP instance. The problem I'm having is the client pop3 users are frequently being told their passwords aren't correct by their email clients (Outlook, Eudora). They try again, a couple times and eventually it works. I've seen it on my own account and when I test their accounts, occasionally it just doesn't take the password. I've only had this trouble since I implemented the LDAP authentication. Checking through the server maillog, I see the following entry: Apr 4 08:44:38 msi2 dovecot: auth(default): dovecot-auth: ../../../libraries/liblber/io.c:491: ber_get_next: Assertion `ber->ber_buf == ((void *)0)' failed. Apr 4 08:44:38 msi2 dovecot: auth(default): pam(secretuser,192.168.0.200): Child process died Apr 4 08:44:38 msi2 dovecot: auth(default): PAM: Child 14564 died with signal 6 Apr 4 08:44:38 msi2 dovecot: pop3-login: Aborted login: user=<secretuser>, method=PLAIN, rip=192.168.0.200, lip=192.168.0.11 This seems to point out that dovecot is the problem, but again, I didn't have this trouble until I implemented the LDAP authentication. So my question is, anyone know a solution? If not, anyone got a suggestion of where I should look for more clues or support? Or any suggestions at all? Thanks for any help. Following is the dovecot version and configuration [root@msi2 ~]# dovecot --version 1.0.rc15 [root@msi2 ~]# dovecot -n # /etc/dovecot.conf protocols: pop3 listen: login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/pop3 pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam userdb: driver: passwd [root@msi2 ~]#

2 4

[Dovecot] [PATCH] Compile cleaning against OpenLDAP 2.3.x
by Roy Marples 12 Apr '07

12 Apr '07

Hi List Looks like OpenLDAP 2.3 doesn't define LDAP_DEPRECATED [1] anymore which causes a few warnings in Gentoo [2]. Attached is a patch that re-defines this so that dovecot can continue using simple functions like ldap_bind(). Thanks Roy [1] http://www.mail-archive.com/openldap-devel@openldap.org/msg00487.html [2] http://bugs.gentoo.org/show_bug.cgi?id=162437

1 0

[Dovecot] Convert plugin mbox to maildir has no effect
by Sylvain Nemtua 12 Apr '07

12 Apr '07

Convert plugin seems to have no effect with dovecot-1.0.rc26 and my settings. When a user log, maildir creation is successful, but no mbox conversion occur. New incoming mails are dropped into maildir, but I cant access those in Mbox file. I set the following in dovecot.con as describe on wiki. mail_location: maildir:/var/mail/Maildir/%u convert_mail: mbox:/var/mail:INBOX=/var/mail/%u Any thoughts ? Is there a particular settings to use ? Anything wrong with my setup ? Logs : dovecot: [ID 107833 mail.info] pop3-login: Login: user=<sts>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: [ID 107833 mail.info] POP3(sts): Effective uid=45842, gid=10008 dovecot: [ID 107833 mail.info] POP3(sts): maildir: data=/var/mail/Maildir/sts dovecot: [ID 107833 mail.info] POP3(sts): maildir: root=/var/mail/Maildir/sts, index=/var/mail/Maildir/sts, control=, inbox= dovecot: [ID 107833 mail.info] POP3(sts): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 dovecot -n : protocols: pop3 ssl_disable: yes disable_plaintext_auth: no shutdown_clients: no login_dir: /var/run/dovecot/login login_executable: /var/mail/bin/dovecot-1.0.rc26_devsol10/libexec/dovecot/pop3-login login_greeting: ready. mail_extra_groups: mail mail_location: maildir:/var/mail/Maildir/%u mail_debug: yes mail_full_filesystem_access: yes mmap_disable: yes mbox_write_locks: fcntl mail_executable: /var/mail/bin/dovecot-1.0.rc26_devsol10/libexec/dovecot/pop3 mail_plugin_dir: /var/mail/bin/dovecot-1.0.rc26_devsol10/lib/dovecot/pop3 pop3_uidl_format: %08Xu%08Xv pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: verbose: yes passdb: driver: passwd passdb: driver: shadow userdb: driver: passwd socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 384 plugin: convert_mail: mbox:/var/mail:INBOX=/var/mail/%u convert_skip_broken_mailboxes: no

4 12

[Dovecot] Building Dovecot to link against alternative libldap
by Ben Beuchler 12 Apr '07

12 Apr '07

I'm running Dovecot on an Ubuntu (Edgy) box. I'd like to link dovecot against the latest stable version of the OpenLDAP libraries instead of the system defaults. I can't really replace the existing libraries as other packages rely on them. If this didn't use libtool, I would be able to influence the runtime linker by manipulating -rpath and -L. I can't seem to figure out how to get this to work with Dovecot's libtool-based build. The system libldap_r.so.2 lives in /usr/lib My libldap_r.so.2.3 lives in /usr/local/lib Anyone have any pointers? -Ben

1 0

[Dovecot] Problems with (probably) Dovecot
by Frank Neps 11 Apr '07

11 Apr '07

Hello altogether, I've got Dovecot 0.99 installed on a Suse Linux 9.2 system, together with Postfix. I need to upgrade that server in the near future to new hardware and new versions, but at the moment it would be great, if I could find the solution for the following problem without upgrading. Unfortunately I didn't find a solution in Google. The system has enough memory and disc space, it was running for about 4 or 5 years without problems now. Trying to access my messages on the server via IMAP protocol using Outlook (2000 or 2002 or 2003) leads to an error message "Invalid messageset: xxxxxxxx" (where xxxxxxxx is a changing number). No data is displayed, the headers are not updated. Squirrelmail says, that the messages are not available any more. And Thunderbird joins in with Outlook and also tells me something about an invalid messageset. For some reasons (and some messages, not all) Kontact / Kmail does not give me error message, however, my main system is not a Linux one and therefore I'd like to get that fixed, if possible. Somewhere in Google I found a note about IMAP index files, which may be corrupt and need to be rebuilt, but I didn't find any Index files, I must admit. Any idea how to solve that? Thanks in advance and best regards, Frank

4 4

[Dovecot] rc31 -> "deferring operation: binding"
by Ben Beuchler 11 Apr '07

11 Apr '07

I hate to bring up anything that might delay 1.0, but the behavior I'm seeing is rather... weird. I'm running rc31, using "userdb static" and "auth_bind=yes". With rc1 (what I had been running) I would occasionally get some "deferring operation" complaints from LDAP, but very rarely. Every now and then it would start to throw "deferring operation: pending operations" and stop authenticating. Digging through the Changelog indicated you've made considerable updates to the auth_bind code, apparently to eliminate just such problems, so I upgraded. Now I'm running rc31 and my OpenLDAP logs are throwing an error like this every few seconds: Apr 9 19:56:42 swizzle slapd[1626]: connection_input: conn=6696168 deferring operation: binding This appears to happen with around every 3rd or 4th bind request. Sometimes it happens with the anonymous requests, sometimes with the auth bind request. As I understand it, the new auth_bind code is extremely careful about flushing all pending operations before attempting to perform the authentication bind. If that's the case, any idea why OpenLDAP is deferring the binding operations so frequently? So far it hasn't caused any login problems, but it's quite disconcerting given the expected behavior described in the Changelog. Any thoughts? -Ben cliff:/opt/dovecot/etc root# ../sbin/dovecot -n # /opt/dovecot-1.0.rc31/etc/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/mcad.edu.rapidssl.crt ssl_key_file: /etc/ssl/private/mcad.edu.rapidssl.key disable_plaintext_auth: no shutdown_clients: no login_dir: /opt/dovecot-1.0.rc31/var/run/dovecot/login login_executable(default): /opt/dovecot-1.0.rc31/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot-1.0.rc31/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot-1.0.rc31/libexec/dovecot/pop3-login login_greeting: Line forms at the rear. login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_processes_count: 5 verbose_proctitle: yes first_valid_uid: 5000 last_valid_uid: 5000 first_valid_gid: 5000 last_valid_gid: 5000 mail_location: maildir:/mail/mcad.edu/%u/Maildir/ maildir_stat_dirs: yes maildir_copy_with_hardlinks: yes mail_executable(default): /opt/dovecot-1.0.rc31/libexec/dovecot/imap mail_executable(imap): /opt/dovecot-1.0.rc31/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot-1.0.rc31/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/dovecot-1.0.rc31/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot-1.0.rc31/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot-1.0.rc31/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain login user: dovecot-auth passdb: driver: ldap args: /opt/dovecot/etc/dovecot-ldap.conf userdb: driver: static args: uid=5000 gid=5000 socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master:

3 7