- dovecot - dovecot.org

[Dovecot] v2.0.rc4 released
by Timo Sirainen 05 Aug '10

05 Aug '10

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc4.tar.gz.sig I'm planning to release rc5 maybe this Friday or weekend, and if there are no serious bugs just change the version number to v2.0.0 a day or two later. Largest changes since rc3: + director: Added director_doveadm_port for accepting doveadm TCP connections. + doveadm: Added client/server architecture support for running mail commands. Enable this by setting doveadm_worker_count to non-zero. + mail-log: Added support for mailbox_create event. + imap_capability = +XFOO BAR can be used to add capabilities instead of replacing the whole capability string. + virtual storage: Added support for IDLE notifications. - doveadm mailbox status: Fixed listing non-ASCII mailbox names. - doveadm fetch: Fixed output when fetching message header or body - doveadm director map/add/remove: Fixed handling IP address as parameter. - dsync: A few more fixes

3 10

[Dovecot] "listen=*, ::" broken?
by Peer Heinlein 05 Aug '10

05 Aug '10

Hi, the default: listen = *, :: should work and should open port 143 on IPv4 and IPv6. In my setup it looks broken: root@mail-archiv:/etc/dovecot# doveconf | grep ^listen listen = *, :: root@mail-archiv:/etc/dovecot# /etc/init.d/dovecot restart Restarting mail server: dovecotError: service(imap-login): listen(::, 143) failed: Address already in use Fatal: Failed to start listeners root@mail-archiv:/etc/dovecot# But it's working with "listen = *": root@mail-archiv:/etc/dovecot# doveconf | grep ^listen listen = * root@mail-archiv:/etc/dovecot# /etc/init.d/dovecot restart Restarting mail server: dovecot. root@mail-archiv:/etc/dovecot# Peer Heinlein -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030-405051-42 Fax: 030-405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

5 6

[Dovecot] 2.0...
by Ralf Hildebrandt 05 Aug '10

05 Aug '10

Hi I'm running 1.2.13 with sieve & managesieve; no problems whatsoever, but the patching & compilation process is a PITA. So I thought, why not try out 2.0rc4 for a change. But: I don't find sieve & managesieve mentioned there - what do I need to enable those? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

3 6

[Dovecot] IMAP IDLE, Virtual mailboxes
by Patrick Nagel 05 Aug '10

05 Aug '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, K-9 Mail (on Android) has been mentioned on this list multiple times recently, I think it's definitely an IMAP client "on the rise". :) It supports IMAP IDLE, and so brings "push mail" to Android mobile phone users. To bring this into the context of this mailing list: I guess a lot of people on this list are making use of server-side filtering (using sieve), so that mails from certain persons or mailing lists end up in the right mailboxes, right on delivery. Now, this is all great, but there are issues when server-side filtering and IMAP IDLE come together: Only one mailbox can be "watched" with one IMAP IDLE connection. So, people who have set up elaborate server-side filtering with say, 50 different sieve "fileinto" calls, will constantly have a *lot* of IMAP IDLE connections open, if they really want to get informed of any mail arriving in any of their mailboxes. Keeping those 50 IMAP connections open wouldn't cost much bandwidth, and who cares about the Internet router's connection tables getting unnecessarily big, anyway? But then there is the "problem" of a mobile phone being carried around constantly, switching physical connections (from WLAN access point 1 to WLAN access point 2 to 3G to 2G to no connection at all and back), every time needing to terminate* those 50 IMAP connections, and then establish 50 new ones (with SSL handshake overhead and all). So, all in all, not an optimal solution. *) (which does not always happen the way it should, see http://code.google.com/p/k9mail/issues/detail?id=1255) I see two ways to improve the situation (one of them quite dovecot-centric): 1) A new extension of the IMAP protocol: IMAP MULTI-IDLE, which somehow allows a client to get notified of changes to more than one mailbox within one IMAP connection. This conflicts with the basic IMAP design though, AFAIK, and is thus not likely to be feasible. 2) Enhancing dovecot's Virtual plugin, so virtual mailboxes do not only get updated on select and expunge, but also when anything changes that affects the set of messages shown in the virtual mailbox. I guess that would have an impact on performance, and thus should be optional. Let me explain the second one: With the help of the Virtual plugin, it is possible to pull all those 50 mailboxes that receive incoming mail together again, just like the INBOX of the pre-server-side-filtering times - the user could configure a virtual mailbox to show all unread mails from those 50 mailboxes. Now the mobile IMAP IDLE users could just watch that one virtual mailbox, needing only one IMAP IDLE connection. After having read the mail (directly in the virtual mailbox), it would disappear, but of course still be in the "real" mailbox, determined by the sieve filter on delivery. Patrick. - -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone: +86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779 PGP key E883A005 https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAku+ydsACgkQ7yMg/OiDoAXV9ACdF+BEstnjfUeJlR/JQKFf6N7n yxYAnAnuD2popWYLfZNCCtlpkAP4SQww =L33A -----END PGP SIGNATURE-----

7 19

[Dovecot] sender address of sieve vacation script
by Wolfgang Burger 05 Aug '10

05 Aug '10

Hi, not entirerly sure wether this is the right place to ask. Sorry if not. I´m running dovecot on a Mac OS X Server (10.6.4). Everything works fine. When I try to enable a vacation message, I get the following error in the log: delays=0/0.01/0.09/0.1, dsn=5.0.0, status=bounced (host XXX[x.x.x.x] said: 553 Mail to <name(a)domain.tld> not allowed; missing domain name in MAIL FROM (in reply to RCPT TO command)) Where host is the mail relay. The logs on the mail relay show matching entries. Sending mails is generally working. I´ve sniffed the network traffic and the FROM Field in the SMTP transfer contains only the following text: <> I´ve allready set the value of myorigin in /private/etc/postfix/ main.cf but to no avail. Can somebody tell me where I can set the sender address of the vacation mail? Or is there something else wrong? Thank you very much. Best regards Wolfgang

3 2

[Dovecot] mobile phone access to dovecot
by casanova99 05 Aug '10

05 Aug '10

I didn't find anything interesting in the search, so I just wanted to see what other people have done (or thought about doing). I'd like to be able to access my dovecot server via IMAP, from the Internet, using the integrated e-mail client from a smart phone. I'm very concerned about security and don't feel comfortable just poking holes into the firewall for direct access from the Internet. Is there a better way to do this? Thanks. -- View this message in context: http://old.nabble.com/mobile-phone-access-to-dovecot-tp29342338p29342338.ht… Sent from the Dovecot mailing list archive at Nabble.com.

3 3

[Dovecot] IMAP access to dovecot list archives?
by Charles Marcus 05 Aug '10

05 Aug '10

Hi Timo, Before I go file a bug for Thunderbird, can you confirm that IMAP access to the dovecot mail list archives should still be working? TB is getting stuck in the account creation screen, and this may be confirmation of a bug they are having trouble isolating in the New Account Wizard. Thanks, -- Best regards, Charles

3 11

[Dovecot] LMTP: Rejecting unknown users
by Peer Heinlein 04 Aug '10

04 Aug '10

Hi! I'm using static results in LDAP-lookups: uris = ldap://127.0.0.1 dn = xxxxxxxxxxxxx dnpass = xxxxxxxxxxxx tls = no ldap_version = 3 base = xxxxxxxxxxxxxxxxx user_attrs = =home=/mail/%d/%n,=uid=10000,=gid=10000,jpberlinMailQuota=quota_rule=*:storage=%$B user_filter = (email=%u) pass_attrs = userPassword=password pass_filter = (email=%u) default_pass_scheme = PLAIN Unfortunately, LMTP accepts mail for *all* users, even for those users, that doesn't exist in LDAP at all: 010-08-04 12:27:58 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth 2010-08-04 12:27:58 auth: Debug: auth client connected (pid=10049) 2010-08-04 12:27:58 lmtp(10054): Debug: none: root=, index=, control=, inbox= 2010-08-04 12:27:58 auth: Debug: master in: USER 1 tessdfdfgdsft(a)example.org service=lmtp lip=(null) r ip=(null) 2010-08-04 12:27:58 auth: Debug: ldap(tessdfdfgdsft(a)example.org,0.0.0.0): user search: base=xxxxxxxxxxxxxxxxxxx 2010-08-04 12:27:58 auth: Debug: ldap(tessdfdfgdsft(a)example.org,0.0.0.0): no fields returned by the server 2010-08-04 12:27:58 auth: Debug: master out: USER 1 tessdfdfgdsft(a)example.org home=/mail/example.org/tessdfdfgd sft uid=10000 gid=10000 2010-08-04 12:27:58 lmtp(10054): Debug: auth input: tessdfdfgdsft(a)example.org home=/mail/example.org/tessdfdfgdsft uid=10000 gid= 10000 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: Effective uid=10000, gid=10000, home=/mail/example.org/tessdfd fgdsft 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no , list=yes, subscriptions=yes 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: maildir++: root=/mail/example.org/tessdfdfgdsft/Maildir, index =, control=, inbox=/mail/example.org/tessdfdfgdsft/Maildir 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, h idden=no, list=children, subscriptions=no 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: shared: root=/var/run/dovecot, index=, control=, inbox= Looks like the "allow_all_users"-Problem from the static database. :-) How can I tell LMTP do reject Mails to users, that doesn't exist in the database/LDAP? It's much better to do this in Dovecot/LMTP then in Postfix-Relay (which can then use LMTP for dynamic address verification). Peer -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030-405051-42 Fax: 030-405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

4 7

Re: [Dovecot] Shared mailboxes errors
by Nikita Koshikov 04 Aug '10

04 Aug '10

On Tue, 03 Aug 2010 23:16:38 +0200 Leander S. wrote: > Hi Nikita Koshikov, > > when I googled for my SERVERBUG which I'm having right now I found your > configuration. > I'm trying to make use of the antispam plugin as you do. Unfortunately > I'm always getting a [SERVERBUG] error mesage with my MTC when I try > moving mails. The antispam debug.log doesn't really tell a lot of more: > > > ### Dovecot AntiSpam ### > # mail signature (used with any backend requiring a signature) > #antispam_signature = X-Spam-Status > #antispam_signature_missing = move > > antispam_mail_sendmail = /usr/local/bin/sa-learn > antispam_mail_sendmail_args = --username=%u;--debug;all > antispam_mail_spam = --spam > antispam_mail_notspam = --ham > antispam_mail_tmpdir = /tmp > antispam_spam = Spam > antispam_unsure = Virus > antispam_trash = Trash > First of all - what OS is this ? BSD ? And how did you install your spamassassin (ports\compiling from source)? Show your local.cf file (/etc/mail/spamassassin or /usr/local/etc/mail/spamassasin). After reading perldoc Mail::SpamAssassin::Conf add to your local.cf for debugging: bayes_file_mode 0777 bayes_path /tmp/.spamassassin/bayes Create folder /tmp/.spamassassin and set permitions 777. Restart spamd with dovecot and try it. > I also read through the sa-learn script but wasn't able to figure out > where this number 9 is coming from ;/ > ... SIGKILL 9 Term Kill signal - but where from ?! > sa-learn has lots of die() function, this should be enough for raising SIGKILL. > > > Do you maybe have any idea? I tried different Dovecot versions already - > alwys the same ... Might there maybe somethign wrong with my syntax? > > > > Any way - thanks a lot in advance & regards > If you stuck after all, remember that sa-learn has -D key, it generate tons of output. Create wrapper and run sa-learn with -D keyword from dovecot, save result and have fun.

2 1

[Dovecot] Dovecot 1.2.13 intermittent authentication failures
by C. Bensend 04 Aug '10

04 Aug '10

Hey folks, I recently upgraded my mail server from an older OpenBSD -CURRENT snapshot to the latest (Aug 1). As part of this upgrade, I updated all of my packages to their latest versions. Since this upgrade, dovecot has begun failing to authenticate intermittently. I use it primarily for web mail (Squirrelmail 1.4.20) and leave myself logged in during the day. This problem manifests itself by kicking me back to the "Username or password incorrect" screen occasionally (several times an hour) when the page refreshes. I am not using sieve, and while I have the PostgreSQL version of the OpenBSD package installed, I do not currently use it for authentication. I am authenticating against the OpenBSD system. The only error I get in the mail log is: Aug 3 11:00:09 fusion dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=<benny>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured There are no errors in the Apache error log... Squirrelmail's version wasn't upgraded, so I don't think this is a Squirrelmail problem as far as I can tell. My config is pretty simple: # 1.2.13: /etc/dovecot.conf Warning: fd limit 128 is lower than what Dovecot can use under full load (more than 640). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: OpenBSD 4.8 i386 base_dir: /var/dovecot/ listen: *, [::1] ssl_cert_file: /etc/ssl/webmail.crt ssl_key_file: /etc/ssl/private/webmail.key login_dir: /var/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: _dovecot mail_location: maildir:~/Maildir mbox_write_locks: fcntl imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmaster(a)example.com auth default: mechanisms: plain login passdb: driver: bsdauth userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: _postfix group: _postfix Everything seems to be working just fine (ie, I don't get any other IMAP errors or see any problems), it's just that it will spontaneously fail to authenticate. When this happens, it may take more than one try to get logged back in. I checked with the OpenBSD port's maintainer, and he hadn't heard of any similar issues (and he uses it himself). Can anyone please help? Thank you so much! Benny -- "Something's going on in this house - last night, I saw a face!" "Did it have a nose?" "Yes!" "That sounds like a face all right." -- Scary Movie 4

2 10