September 2010 - dovecot

[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

[Dovecot] Sub-Sub-Subfolders not shown after converting from maildir to mdbox
by Patrick Westenberg 10 Sep '10

10 Sep '10

Hi again, I just recognized a problem concerning subfolders after converting from maildir to mdbox. Thunderbird and SeaMonkey don´t show folders that are subfolders of subfolders. Have a look at the filesystem: discovery:/var/mail/domain.tld/patrick/mdbox/mailboxes/Folder1/Folder2# ls -l insgesamt 8 drwx------ 2 vmail vmail 4096 5. Sep 23:42 dbox-Mails drwx------ 3 vmail vmail 4096 5. Sep 23:42 Folder3 Using Thunderbird or Seamonkey, Folder1 and Folder2 are listed and can be subscribed to but Folder3 never gets listed. If I create Folder4 as a new subfolder from Folder2 it works, so the problem only exists with existing folders from converted maildirs. I had to use a namespace for the convert from my old Courier IMAP. Any hints? Regards Patrick # 2.0.1: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.5 auth_mechanisms = plain login mail_gid = vmail mail_location = mdbox:~/mdbox mail_plugins = quota mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = maildir:User quota } protocols = imap sieve service imap-login { service_count = 1 } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } service_count = 1 } ssl = required ssl_cert = </etc/ssl/certs/imap.crt ssl_key = </etc/ssl/certs/imap.key userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol imap { mail_plugins = $mail_plugins imap_quota }

3 7

[Dovecot] Released Pigeonhole v0.2.0 for Dovecot v2.0.2
by Stephan Bosch 10 Sep '10

10 Sep '10

Hello Dovecot users, I have finally finished the first release of Pigeonhole for Dovecot v2.0. The most notable change from previous Dovecot v1.2 Sieve/ManageSieve releases is that all is now integrated in a single package and there is no need to patch Dovecot anymore to gain ManageSieve support. Changelog v0.2.0: * Merged Sieve and ManageSieve packages into a single Pigeonhole package. There is also no need to patch Dovecot anymore to gain ManageSieve support. Version numbering of previous Sieve releases is continued as v0.2.0. The sources originally branched off from Sieve v0.1.5 and ManageSieve v0.11.4, but the NEWS history of much more recent releases for Dovecot v1.2 is included since these changes are all included in this release as well. * The ManageSieve service now binds to TCP port 4190 by default due to the IANA port assignment for the ManageSieve service. When upgrading from v1.2, this should be taken into account. The service can be configured manually to listen on both 2000 and 4190. * The Dovecot configuration now calls the ManageSieve protocol 'sieve' in stead of 'managesieve' because it is registered as such with IANA. The binaries and the services are still called managesieve and managesieve-login. * The binary representation of a compiled Sieve script is updated to include source code locations of all commands and arguments. This is implemented in a similar manner as such debug information is included in some system executables and libraries (DWARF-like). Run-time errors can now always refer to the proper line number in the Sieve source script. * The Sieve plugin is adapted to work properly with the new LMTP service introduced with Dovecot v2.0. The same plugin is used for both LDA and LMTP. * The 'sieve_subaddress_sep' setting for the Sieve subaddress extension is now known as 'recipient_delimiter'. Although the deprecated sieve_subaddress_sep setting is still recognized for backwards compatibility, it is recommended to update the setting to the new name, since the new LMTP service also use the recipient_delimiter setting. * ManageSieve: changed default IMPLEMENTATION capability to from 'Dovecot' to 'Dovecot Pigeonhole'. * Renamed the sieved tool to sieve-dump. The original name was somewhat confusing. * Updated man pages to match style and structure of new Dovecot man pages. * Made testsuite commands more uniform and cleaned up many of the testsuite scripts. Some minor new tests were added in the process. + Simplified string matching API to use abstract string lists as data sources. This will also make implementing the index extension easier in the future. + Significantly improved trace debugging with the sieve-test tool. The full execution of the script can be examined, including the matched values and keys of the respective Sieve test commands. The executed statements are listed with their line number (and code address when requested). The level of detail is configurable from the command line. + The SIEVE and NOTIFY capabilities reported by the ManageSieve protocol can now be configured manually. If left unconfigured, the capabilities are determined from the default Sieve and ManageSieve configuration. User-specific capabilities aren't reported until after authentication. + Significantly improved file error handling. This means that administrators get a more useful and informative log message when file operations fail. The most notable example is that when the LDA Sieve plugin is trying to store a binary for a global script, the resulting failure message also points the administrator towards pre-compiling the script with sievec. + Added runtime argument value checking for several commands (redirect, date, vacation). When variables are used, these checks cannot be performed at compiletime. A proper runtime error now is produced when invalid data is encountered. + UTF8 validity of fileinto command argument is now checked either at compile time or at runtime. Previously, it was not checked until the store action was executed. + Validity of IMAP flags for the imap4flags extension is now checked also at runtime. Previously, it was not checked until the store action was executed. + Simplified and restructured error handling. Also made sure that user-caused errors are no longer written to the Dovecot master/LDA log. - Multiscript: fixed duplicate implicit keep caused by erroneous execution state update. - Prevented assertion failure due to currupt binary string representation. If the string was missing a final \0 character an assertion was produced in stead of a binary corruption error. - Imap4flags: fixed bug in setflag command; when parameter was a stringlist, only the last item was actually set. - Variables extension: fixed :length set modifier to recognize utf8 characters in stead of octets. - Testsuite: prevented innocent warning messages, i.e. those that are part of the test, from showing up by default. - ManageSieve/Sieve storage: fixed error handling of PUTSCRIPT commmand; save commit errors would not make the command fail. - ManageSieve: enforced protocol syntax better with some of the commands; some commands allowed spurious extra arguments. - Fixed Sieve script name checking to properly handle length limit and added 0x00ff as invalid character. - Removed spurious old stdio.h (top) includes; these caused compile issues on specific systems. - Fixed default Sieve capability (as reported by ManageSieve): extra extensions spamtest, spamtestplus and virustest were enabled by default. These should, however, only be enabled when properly configured and there is no default configuration. The release is available as follows: http://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.0.tar.gz http://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.0.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.0 wiki for more information. Have fun testing this first release and don't hesitate to notify me when there are any problems. The bugfixes above are also applied to the Dovecot v1.2 Sieve and ManageSieve sources and I'll produce new releases for those in the next few days. Oh.. and if anyone is wondering what those duplicate notifications are on the dovecot-cvs list.. well.. oops. :) Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] master user login dovecot 2.02 trouble
by Robert Schetterer 10 Sep '10

10 Sep '10

Hi , i got trouble with master login thunderbird anounces no INBOX there at master login also telnet looks strange normal user login 1 login ...... 1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA ACL RIGHTS=texk] Logged in 2 list "" "*" 2 BAD Error in IMAP command : Unknown command. 3 list "" "*" * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Junk" * LIST (\HasNoChildren) "/" "Sent" * LIST (\HasNoChildren) "/" "Drafts" * LIST (\HasNoChildren) "/" "Templates" * LIST (\HasNoChildren) "/" "Archives" * LIST (\HasNoChildren) "/" "INBOX" 3 OK List completed. 4 logout master login * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN] imap, pop ready 1 login .....*...... 1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA ACL RIGHTS=texk] Logged in 2 list "" "*" * LIST (\Unmarked) "/" "INBOX" 2 OK List completed. 3 logout * BYE Logging out 3 OK Logout completed. something broken ? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 1

[Dovecot] Question on Mail Formats
by Giovanni Giorgi 09 Sep '10

09 Sep '10

Hi, I am still tuning my dovecot, but I find myself very confortable with it. I am going to structure my imap folder with a new namespace (somthing you cannot do with GMail :) and I can choose the mailbox format. What is the difference between the two mailbox format "mbox" and "maildir"? I know mbox is older, but there is a good reason to use maildir instead? I can get for instance some performance improvement? Better archiving? Thank you! -- Senior Consultant http://gioorgi.com

2 1

[Dovecot] LMTP logging configuration
by Rainer Frey 09 Sep '10

09 Sep '10

Hi, I'm using Dovecot 2.0.1, and I log to a custom syslog facility (local0) in the main configuration (I want a separate log file, but I want to make use of rsyslogd's capabilities). I overwrite the syslog facility for LDA (mail) to have all delivery related stuff in /var/log/mail.log, and that works fine. I tried to do the same for LMTP with protocol lmtp { syslog_facility = mail } but this has no effect, LMTP logs to local0. Is this supposed to work, or is this not implemented at all? If not, is using a logfile in main config, but syslog in lmtp supported? Thanks Rainer

2 4