- dovecot - dovecot.org

[Dovecot] upgrading from 1.0 to 1.1
by Daniel 13 Apr '07

13 Apr '07

Hi! I've been using 1.0 cvs always. Now that 1.0 is final, I would like to continue testing the future dovecot, and thought I'd ask if there is anything I must be aware of, if I'm trying to upgrade to 1.1 cvs. Thanks! Daniel

2 1

[Dovecot] dovecot + ima
by aza zel 13 Apr '07

13 Apr '07

hi... ¿dovecot uses imap4? can anybody explain diferences between imap4 and imap. -- Salu2 ;)

2 6

[Dovecot] dovecot forward multipart problem
by Samuel HAMEAU 13 Apr '07

13 Apr '07

Hi, I experience problems everytime i forward a mail (basically, when forwarding an email containing an attachement). I'm using thunderbird (it does the same with outlook clients) with the forward parameter "as attachement" instead of "inline". (Using the inline parameters works fine). When i forward a mail with attachements (eg a jpeg file), the attachements file is displayed in base64 instead, and is impossible to detach/save. I'm using dovecot 1.0.rc22-1 (debian package) on debian etch, x86 SMP box with maildir format on a ext3 partition. I'm using postfix currently 2.3.4-3, i have tried different version of dovecot (from rc16 i think) and postfix (from 2.2.?) and i suspect the deliver to be the origin of the problem. I think it is the same problem than here http://dovecot.org/pipermail/dovecot/2006-July/014786.html , my "From" headers are badly duplicated. Could this be fixed before the dovecot 1.0 release ? Regards, Samuel HAMEAU

3 7

[Dovecot] LDA sieve plugin [patch]
by Uldis Pakuls 13 Apr '07

13 Apr '07

Hi all. I spent some time testing Dovecot's LDA sieve plugin and found problem with "notify" method. In fact it always returns "generic sieve error"... and thus produces bounce messages like this: ----- Your message was automatically rejected by Dovecot Mail Delivery Agent. The following reason was given: Unknown error ---- Deliver logs error: "generic sieve error", but otherwise server reports "notify" method as supported. The problem is: original code was taken from curys sieve and requires "notifyd", as sieve runs 'chrooted' and can't access external binaries like "sendmail". communications with notifyd is done via socket. Thus I wrote pacth, which ads "notify" functionality to dovecot's sieve plugin, at less "notify:mailto" method. cyrus originally contains null, log and zephyr methods. null and log is useless with dovecot, zephur is cyrus specific... RFC docs says there is 3 available methods SMS, XMPP and MAILTO: ------ method can be an SMS URI [SMS-URI <http://ietfreport.isoc.org/idref/draft-ietf-sieve-notify/#ref-SMS-URI>] containing a phone number, or an XMPP [XMPP <http://ietfreport.isoc.org/idref/draft-ietf-sieve-notify/#ref-XMPP>] URI containing an XMPP identifier [XMPP-URI <http://ietfreport.isoc.org/idref/draft-ietf-sieve-notify/#ref-XMPP-URI>] The supported URI values will be site-specific, but support for the [MailTo <http://ietfreport.isoc.org/idref/draft-ietf-sieve-notify/#ref-MailTo>] method is REQUIRED in order to insure interoperability. If a URI schema is specified that the implementation does not support, the notification MUST cause an error condition. Sieve scripts can check the supported methods using the "valid_notify_method" test to be sure that they only use supported ones, to avoid such error conditions. ------ as SMS-URI and XMPP methods are not included in cyrus sieve version, they are not available in dovecots plugin too. [any ideas, sample code how to implement them?] BUT... WARNING All this will not work if you have "mail_chroot" setting enabled in dovecot.conf; chrooted process can't access required external binaries. DOT USE THIS PLUGIN WITH "mail_chroot" SENTIG ENABLED! Actualy it is not sieve plugin problem only - its LDA problem... it can't send bonce messages, do forwards etc. Question to Timo: Do You have ideas how to fix it? My be disable chroting for LDA at all? or do it "cyrus way" - move all calls to external binaries to sepreate, non chrooted process? For delivery agent it is requred to be able send bounces and notifications... do forwards. Uldis

1 0

[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