- dovecot - dovecot.org

[Dovecot] v2.0.2 released
by Timo Sirainen 13 Sep '10

13 Sep '10

http://dovecot.org/releases/2.0/dovecot-2.0.2.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.2.tar.gz.sig Many small fixes and logging improvements, but most importantly fixes LMTP with Maildir. * vpopmail support is disabled for now, since it's broken. You can use it via checkpassword support or its sql/ldap database directly. - maildir: Fixed "duplicate uidlist entry" errors that happened at least with LMTP when mail was delivered to multiple recipients - Deleting ACLs didn't cause entries to be removed from acl_shared_dict - mail_max_lock_timeout setting wasn't working with all locks - auth_cache_size setting's old-style value wasn't autoconverted and it usually also caused a crash

3 4

[Dovecot] Upgraded dovecot - now it insists on imap TLS
by Alan Brown 13 Sep '10

13 Sep '10

This is definitely an operator error issue, but I'm under a bit of pressure. I updated our 1.1.20 installation to 2.0.1 over the weekend and discovered this morning that it's insisting on TLS imap on port 143 as well as port 993 What am I missing? Thanks in advance Alan

2 1

[Dovecot] SSHA256 password too short
by Osvaldo Alvarez Pozo 13 Sep '10

13 Sep '10

Hi all I am upgrading a mail system. So I installed aside a new server with debian lenny dovecot 1.2 from backports , postfix 2.5, mysql 5. I recovered the database from the actual production system with a dump. But when i started testing I found this in my logs Sep 13 09:45:07 auth-worker(default): Info: sql(user(a)domain.tld,127.0.0.1): Password mismatch Sep 13 09:45:07 auth-worker(default): Error: ssha256_verify(user(a)domain.tld): SSHA256 password too short Sep 13 09:45:07 auth-worker(default): Warning: Invalid OTP data in passdb Sep 13 09:45:07 auth-worker(default): Warning: Invalid OTP data in passdb But the same users gets connected normally to the production system. I use mysql as driver and my default_schema is md5 Any ideas ?? Thanks in advance

3 2

[Dovecot] Proper use of convert plugin?
by Donny Brooks 13 Sep '10

13 Sep '10

I am trying to convert from mbox to maildir on our mail server here at work. The specs are as follows: Fedora 11 x86-64 dovecot-1.2.11-3.fc11.x86_64 postfix-2.5.6-3.fc11.x86_64 dovecot-managesieve-1.2.11-3.fc11.x86_64 We are currently using mbox format with the users INBOX set to /var/spool/mail/username and other mail is in /home/username/Mail. I would like to migrate to maildir format. I tried using the convert plugin as the wiki suggested: mail_location = maildir:~/Maildir protocol imap { mail_plugins = convert } protocol pop3 { mail_plugins = convert } plugin { convert_mail = mbox:/home/%u/Mail:INBOX=/var/spool/mail/%u } When doing this I get this scrolling in the /var/log/maillog... Sep 11 14:41:38 roark dovecot: IMAP(username): Mailbox conversion: Lock creation timeouted Sep 11 14:41:39 roark dovecot: IMAP(username): Fatal: Mailbox conversion failed, exiting Sep 11 14:56:53 roark dovecot: POP3(otheruser): Mailbox conversion: rename(/home/otheruser/Mail, /home/otheruser/Mail-converted) failed: Directory not empty it does this for some users only. Mine for instance never errored and completed perfectly from what I can tell (other than the new mail issue below). The server load has skyrocketed though, so that is most likely part of it. Also, while testing this, new mail was not delivered to the maildir but rather to the old mbox in /var/spool/mail/username. The new mail never showed up until I switched the config back over to the mbox settings. Am I missing something here? Thanks for any insight -- Donny B.

2 1

[Dovecot] Question about LDA+spamassassin
by Javier de Miguel Rodríguez 13 Sep '10

13 Sep '10

Hello I am using dovecot 1.2.11 (openexchange not still fully supported with dovecot 2.0). In my setup I use ldap to store quota information, and I want to accomplish the following: per-user spamassassin rules (MDA style), but my setup has the following requeriments: mail_uid= entrega mail_gid= entrega LDA & SIEVE: sieve_dir=/buzones/my_domain/%2.26Hn/%2.200Hn/%n/sieve/ mail_location=maildir:/buzones/my_domain/%2.26Hn/%2.200Hn/%n I have been reading in the wiki, but I am not sure how I can have in $mail_location/user1 a .spamassassin directory per-user and lda+sieve work together to make spam rules by user Regards Javier

1 0

[Dovecot] Dovecot 2.0.2 and Pigeonhole-0.2.0
by Matthias Quernheim 12 Sep '10

12 Sep '10

I upgraded today to Dovecot 2.0.2 and Pigeonhole-0.2.0 based on debian lenny. Looked not to bad, but when I activated sieve in the lda section the following error appeared for each delivery Sep 11 18:13:11 lda: Error: dlopen(/usr/local/lib/dovecot/lda/lib90_sieve_plugin.so) failed: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so: undefined symbol: tried_default_save Sep 11 18:13:11 lda: Fatal: Couldn't load required plugins I found some hints regarding on old versoin of deliver, but it is the current one. Any ideas? Thanks Matthias

2 1

Re: [Dovecot] lda: internal error
by Dirk Heinrichs 11 Sep '10

11 Sep '10

Am 11.09.2010 12:53, schrieb axel Egal: > all files in /etc/dovecot have already 0666 permission. What about the directory? Bye... Dirk

1 0

[Dovecot] lda: internal error
by axel Egal 11 Sep '10

11 Sep '10

Hi, i'm trying to relay local post from Postfix to Dovecot-lda. It's running on opensuse11.3-64bit with postfix V2.7.1 and dovecot V2.01. sending local message like: echo foo | /usr/sbin/sendmail -f root root gets no logdata in dovecot.err, -.info,-.debug. but the postfix-logfile tells: Sep 11 10:56:12 server postfix/cleanup[3027]: 94027A65BC: message-id=<20100911085612.94027A65BC(a)Server.Firma> Sep 11 10:56:12 server postfix/qmgr[1544]: 94027A65BC: from=<root(a)Server.Firma>, size=277, nrcpt=1 (queue active) Sep 11 10:56:12 server postfix/local[3029]: 94027A65BC: to=<root(a)Server.Firma>, orig_to=<root>, relay=local, delay=0.22, delays=0.14/0.01/0/0.06, dsn=4.3.0, status=deferred (temporary failure. Command output: lda: Error: user root: Error reading configuration: net_connect_unix(/etc/dovecot/dovecot.conf) failed: Permission denied lda: Fatal: Internal error occurred. Refer to server log for more information. ) There is no further loginfo in any other logfiles Is the internal-error a result of wrong parameters?

2 1

[Dovecot] Dovecot 2.0.1 Quota dict timeout
by David Jonas 10 Sep '10

10 Sep '10

Since an upgrade to 2.0.1 from 1.2.x we're seeing this on (mostly) large mailboxes (Maildir) Sep 4 11:27:25 dovecot: dict: mysql: Connected to 192.168.dd.dd (accounts) ... Sep 4 11:27:46 kelly-a dovecot: lda(u1(a)example.com):) msgid=<123@xxx>: saved mail to INBOX Sep 4 11:27:47 dovecot: dict: Error: sql dict: commit failed: Not connected to database Sep 4 11:27:47 dovecot: imap(u1(a)example.com): Error: dict quota: Quota update failed, it's now desynced The dict is MySQL on another server, same switch. It does appear that the quota gets out of sync. From the entries I checked an email is often being delivered shortly before the error (as above). But I also see it happen with the lda: Sep 4 08:27:11 dovecot: pop3(u2(a)example.com): Disconnected: Logged out... Sep 4 08:42:48 dovecot: lda(u2(a)example.com): msgid=<123@aaa>: saved mail to INBOX Sep 4 08:43:26 dovecot: lda(u2(a)example.com): msgid=<123@bbb>: saved mail to INBOX Sep 4 08:43:26 dovecot: dict: Error: sql dict: commit failed: Not connected to database Sep 4 08:43:26 dovecot: lda(u2(a)example.com): Error: dict quota: Quota update failed, it's now desynced Sep 4 08:46:14 dovecot: pop3-login: Login: user=<u2(a)example.com>,... This is happening on two different dovecot servers. The only thing they share is the MySQL server, but it has a load of 0.5 at peak. Is there something that can be tuned to keep this from happening? Possibly relevant entries from `doveconf -n`. Any tuning regarding dict can be assumed as default: maildir_very_dirty_syncs = yes mail_plugins = quota plugin { quota = dict:user:%LTd-%LTn:proxy::quota } Thanks! David

2 6

[Dovecot] nfs director
by Edward avanti 10 Sep '10

10 Sep '10

Halo, Please can you explain why this is advantage over a hardware load balancer. I fail to see advantage if anything it add in more point of failure, with several hundred thousand user, we can ill afford to mess around or add to complexity, sometime keeping it simple is simply way to be, when use qmail/vpopmail, we never had one failure or problem, ever, we very proud of this record so our users. if director service assign 60K user to each front end, how it handle if 5K simultaneous user login, but all 5K happen to be assign to that one machine, it do all work whilst other 7 server sit there do nothing negating what the LB is design for? Is it really worth it? Do we really need this, or just let foundry switch handle it as it does now. We also have 24 front end SMTP server, these deliver mail to netapp filer, all 24 plus 8 pop3 server and 2 webmail imap server all mount /vmail, so all access same maildir. it seem work very effective thus far and for many many year when we use qmail and vpopmail. Thaks

16 48