- dovecot - dovecot.org

[Dovecot] Dovecot 2.1.16 doveadm purge -A segfault
by Daniel Parthey 29 Apr '13

29 Apr '13

Hi, I know that a lot of work has been done regarding doveadm server, but I'm still experiencing easily reproducible segfault crashes of doveadm-server with 2.1.16 when running the following command in a 4 node director/mailbox cluster: /usr/bin/doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A The dovecot-error.log shows the following errors (addresses anonymized): Apr 29 15:45:14 10.129.3.233 dovecot: doveadm: Error: purge: invalid option -- '' Apr 29 15:45:14 10.129.3.233 dovecot: doveadm(x.xxxxxx(a)xxx-xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.233 dovecot: doveadm: Error: purge: invalid option -- '�' Apr 29 15:45:14 10.129.3.233 dovecot: doveadm(x.xxxxxx(a)xxx-xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.249 dovecot: doveadm: Error: purge: invalid option -- '�' Apr 29 15:45:14 10.129.3.249 dovecot: doveadm(x.xxxxxx(a)xxx-xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.249 dovecot: doveadm: Error: purge: invalid option -- 'r' Apr 29 15:45:14 10.129.3.249 dovecot: doveadm(x.xxxxxx(a)xxx-xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.213 dovecot: doveadm: Error: purge: invalid option -- 'e' Apr 29 15:45:14 10.129.3.213 dovecot: doveadm(xxxxx(a)xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.213 dovecot: doveadm: Error: purge: invalid option -- 'g' Apr 29 15:45:14 10.129.3.213 dovecot: doveadm(xxxxx(a)xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.213 dovecot: doveadm: Error: purge: invalid option -- 'e' Apr 29 15:45:14 10.129.3.213 dovecot: doveadm(xxxxx(a)xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.213 dovecot: doveadm: Error: purge: invalid option -- '-' Apr 29 15:45:14 10.129.3.213 dovecot: doveadm(xxxxx(a)xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.249 dovecot: doveadm: Error: purge: invalid option -- '' Apr 29 15:45:14 10.129.3.249 dovecot: doveadm(xxxxxxxxxx(a)xxxxxxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.213 dovecot: doveadm(xxxxx(a)xxxxxx.xx): Fatal: master: service(doveadm): child 6316 killed with signal 11 (core dumped) There seems to something wrong with the doveadm command parser: # gdb /usr/lib/dovecot/doveadm-server /var/tmp/6316 (gdb) bt full #0 0x00007f52f0dc7cca in ?? () from /lib/libc.so.6 No symbol table info available. #1 0x00007f52f0dc8dab in ?? () from /lib/libc.so.6 No symbol table info available. #2 0x00007f52f0dc8e18 in getopt () from /lib/libc.so.6 No symbol table info available. #3 0x00000000004138ce in doveadm_mail_cmd_server_parse (conn=0xe09ad0) at client-connection.c:69 getopt_args = 0xdfa6b8 "AS:u:" c = <value optimized out> cmd = 0xe062c8 add_username_header = false #4 client_handle_command (conn=0xe09ad0) at client-connection.c:223 ctx = 0xe0dae0 flags = <value optimized out> cmd_name = <value optimized out> input = {module = 0x0, service = 0x4210f0 "doveadm", username = 0xdfa59a "xxxxxxx(a)xxxxxxxx.xx", session_id = 0x0, local_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0, userdb_fields = 0x0, flags_override_add = 0, flags_override_remove = 0, no_userdb_lookup = 0} argc = <value optimized out> #5 client_connection_input (conn=0xe09ad0) at client-connection.c:326 args = <value optimized out> _data_stack_cur_id = 3 line = <value optimized out> ok = <value optimized out> #6 0x00007f52f10e6166 in io_loop_call_io (io=0xe097e0) at ioloop.c:379 ioloop = 0xe026a0 t_id = 2 #7 0x00007f52f10e71ef in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:213 ctx = 0xe054f0 event = 0xe05560 list = 0xe09950 io = 0xdfa5c8 tv = {tv_sec = 2147483, tv_usec = 0} msecs = <value optimized out> ret = <value optimized out> i = 0 call = false #8 0x00007f52f10e6108 in io_loop_run (ioloop=0xe026a0) at ioloop.c:398 No locals. #9 0x00007f52f10d15a3 in master_service_run (service=0xe02550, callback=0) at master-service.c:544 No locals. #10 0x0000000000414111 in main (argc=1, argv=0xe02370) at main.c:90 set_roots = {0x422780, 0x0} error = 0x0 Regards Daniel -- https://plus.google.com/103021802792276734820

1 0

[Dovecot] Dovecot Solr Panic
by Andre Rodier 29 Apr '13

29 Apr '13

Hello Everyone, I have a small base of users (30), but a lot of emails. I have an error again when I am indexing a virtual folder with a large number of folders. I appreciate this is a special case, but I am using dovecot and solr as it is, according to the documentation, the favourite way. One user is using a large number of archives sub folders, by years, months and subfolders, since 5 years. I am convincing this user to give up this organisation, but in the mean time, I hope to solve this problem. The virtual folder, called Archives, references all the sub folders in the Archive folder. There is about 380 folders, and worst of all, 55k characters with their names concatenated. On solr, I have increased the value of headerBufferSize to a huge value, but I have still this error. Anyway, this is the error I have when I try to index this virtual folder: ---8<--------------------------------------------------------------------------------------------------------------------------------------- root@lapetus:/mnt/emails/indiefield.co.uk/jsmith/Mails/Virtual# doveadm -v index -u 'john smith' 'Search/Archives' doveadm(john smith): Info: Search/Archives: Caching mails seq=109580..127362 1800/17783doveadm(john smith): Panic: file solr-connection.c: line 416 (solr_connection_select): assertion failed: (!conn->posting) doveadm(john smith): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x4414a) [0x7fcb7b5b014a] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fcb7b5b020a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fcb7b58782a] -> /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(+0x754a) [0x7fcb790fa54a] -> /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(+0x4037) [0x7fcb790f7037] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_backend_get_last_uid+0x5a) [0x7fcb79b2f66a] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xc1fd) [0x7fcb79b341fd] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xc689) [0x7fcb79b34689] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xc51e) [0x7fcb79b3451e] -> doveadm(+0x16719) [0x7fcb7bf71719] -> doveadm(+0x13346) [0x7fcb7bf6e346] -> doveadm(+0x13e21) [0x7fcb7bf6ee21] -> doveadm(doveadm_mail_try_run+0x161) [0x7fcb7bf6f2e1] -> doveadm(main+0x3d1) [0x7fcb7bf6def1] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fcb7b200ead] -> doveadm(+0x13125) [0x7fcb7bf6e125] Aborted ---8<--------------------------------------------------------------------------------------------------------------------------------------- On the solr side: ---8<--------------------------------------------------------------------------------------------------------------------------------------- 28-Apr-2013 17:13:33 org.apache.solr.update.processor.LogUpdateProcessor finish INFO: {add=[1/70af772eafc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 2/70af772eafc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 3/70af772eafc17c51fb350000812a8a 77/john smith(a)indiefield.co.uk, 4/70af772eafc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 5/70af772eafc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 6/70af772ea fc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 7/70af772eafc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 8/70af772eafc17c51fb350000812a8a77/john smith@indiefie ld.co.uk, ... (8 added)]} 0 19141 28-Apr-2013 17:13:33 org.apache.solr.common.SolrException log SEVERE: org.apache.solr.common.SolrException: ParseError at [row,col]:[1188418,131] Message: Premature end of file. at org.apache.solr.handler.XMLLoader.load(XMLLoader.java:72) at org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:54) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131) at org.apache.solr.core.SolrCore.execute(SolrCore.java:1317) at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:338) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:241) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:943) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:843) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1188418,131] Message: Premature end of file. at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:592) at org.apache.solr.handler.XMLLoader.readDoc(XMLLoader.java:273) at org.apache.solr.handler.XMLLoader.processUpdate(XMLLoader.java:138) at org.apache.solr.handler.XMLLoader.load(XMLLoader.java:69) ... 22 more ---8<--------------------------------------------------------------------------------------------------------------------------------------- Kind regards, Andre Rodier

3 3

[Dovecot] dovecot-sql.conf - Unknown setting: driver
by jeep＠rahul.net 27 Apr '13

27 Apr '13

Im upgrading my dovecot from 2.1.14 to dovecot 2.2.1 on linux. Im using the same configuration file against my MySQL db and getting the following error: doveconf -n # 2.2.1: /opt/dovecot221/etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /opt/dovecot221/etc/dovecot/conf.d/dovecot-sql.conf line 2: Unknown setting: driver dovecot-sql.conf: # The mysqld.sock socket may be in different locations in different systems driver = mysql # Use "host= ... pass=foo#bar" if your password has '#' character connect = host=/var/run/mysqld/mysqld.sock dbname=mydb user=username password=pass password_query = SELECT userid AS username, domain, password \ FROM users WHERE userid = '%n' AND domain = '%d' user_query = SELECT home, uid, gid FROM users WHERE userid = '%n' AND domain = '%d' home=/opt/ii/%1n/%n/INBOX # For using doveadm -A: iterate_query = SELECT userid AS username, domain FROM users That file worked fine in the last version. Looking at the docs 'driver' is still a valid setting. Can someone help me figure out why its complaining? Ive even Im lost as to why this error is occuring unless the error itself is actually another problem and the wrong error is popping up. Been working on this for a day and cant figure it out. Thanks in advance! /mf/home/jeep/shell/.signature

2 3

[Dovecot] Replication fails with "Remote dsync doesn't use compatible protocol"
by Rich Wales 27 Apr '13

27 Apr '13

I can't get replication to work in Dovecot 2.2.1. I'm getting the following error on the machine where I'm initiating the replication: richatwork dovecot: doveadm: Error: dsync-remote(richatwork): Error: dsync(local): Remote dsync doesn't use compatible protocol Both the local and remote servers are running identical versions of Dovecot (2.2.1), so I don't understand why I would be having any sort of "compatible protocol" problem. Any ideas? I posted the "dovecot -n" output for both servers in my earlier e-mail on this issue, which I sent about 24 hours ago (and which I assume was too long for people to be willing to read). Rich Wales richw(a)richw.org

1 1

[Dovecot] ios clients and namespace trouble
by Kelsey Cummings 27 Apr '13

27 Apr '13

We migrated to dovecot from courier and maintained a courier compatible namespace configuration. This resulted in ios clients needing to be manually configured in order to use the special folders correctly (delete messages, save drafts, etc) either by being given the correct "Path Prefix" or by manually selecting the special folders. I can't fathom why apple has chosen not to support or can't detect namespace correctly and require manual configuration but if they haven't done it by now they must have some reason for it and aren't going to fix it any time soon. Are there any creative solutions to fixing the i-clients and preventing them from needing manual configuration? -K

2 3

[Dovecot] .dovecot.sieve/tmp)failed: Not a directory
by JC Putter 25 Apr '13

25 Apr '13

stat(/var/spool/vmail/example.com/user/.dovecot.sieve/tmp)failed: Not a directory auth_mechanisms = plain login disable_plaintext_auth = no first_valid_uid = 2000 last_valid_uid = 2000 mail_gid = 2000 mail_location = maildir:/var/spool/vmail/%d/%n mail_uid = 2000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mbox_write_locks = fcntl passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } service auth { unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } According to the Wiki "It is not wise to place this link inside your mail store, as it may be mistaken for a mail folder. Inside a maildir for instance, the default .dovecot.sieve would show up as phantom folder */dovecot/sieve* in your IMAP tree." Sorry i am a bit of a noob, the docs don't explain clearly what to do...

3 2

[Dovecot] Replication -- multiple users, three or more servers?
by Rich Wales 24 Apr '13

24 Apr '13

I'm running Dovecot 2.2.1 on an Ubuntu 12.04.2 server, with half a dozen accounts for various family members. I want to set up replication involving at least three Ubuntu servers, with different users replicated on different sets of servers. For example, I might have mail for "user1" replicated on "server1", "server2", and "server3"... while mail for "user2" would be on "server1" and "server2"... and mail for "user3" would be on "server1" and "server3". I've read the wiki page (http://wiki2.dovecot.org/Replication) but I'm still confused. I'd love to see an example that clearly shows how to set up specific individual mail users to be replicated on a different set of servers for each user, like what I described above. Rich Wales richw(a)richw.org

2 3

[Dovecot] login crashes - maybe too many simultan connections
by Frank Leonhardt 24 Apr '13

24 Apr '13

Hallo, since a few days, users sometimes have problems connecting to our mailserver, in the mail.err are many lines like this: Apr 23 11:14:25 psy2 dovecot: dovecot: child 17607 (login) killed with signal 11 (core dumps disabled) (ip=xx.xx.146.84) Users who are already logged in keep connected, but new connections are not possible.This happens only between 10 am and 3 pm, never in the early morning or at night, so i assume, maybe this is caused by too many simultaneous connections? After restarting dovecot the problem is temporary solved, new users may connect, but after one or a few days, this may happen again. # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.1 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: alle mail_location: maildir:~/Maildir fsync_disable: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 auth default: passdb: driver: pam args: dovecot userdb: driver: passwd May anybody help? Thanks in advance! Greetings from Frank.

2 1

[Dovecot] Strange issue with doveadm user
by Antoine Nguyen 24 Apr '13

24 Apr '13

Dear all, I encounter a strange issue with the *doveadm user* command. (dovecot 2.1.16) I try to retrieve information about a specific user but dovecot says it doesn't exist (whereas I just created it). The following command fails: $ sudo -u vmail doveadm user pouet(a)domain.tld userdb lookup: user pouet(a)domain.tld doesn't exist If I try a more global lookup, the user is properly found: $ sudo -u vmail doveadm user *(a)domain.tld user1(a)domain.tld *pouet(a)domain.tld* Sending a query for another user works well. For example : $ sudo -u vmail doveadm user user1(a)domain.tld userdb: user1(a)domain.tld home : /var/vmail/domain.tld/user1 uid : 500 gid : 500 quota_rule: *:bytes=100M I really don't understand what's happening... The only difference I see between the users is that user1 was created when I was using dovecot 1.2... Thanks for your help.

1 1

Re: [Dovecot] Using dsync to export mail to remote IMAP account
by Joseph Tam 24 Apr '13

24 Apr '13

Timo Sirainen writes: >> I've read the web/man pages on dsync, but it's not clear to me whether >> dsync can be used to export (rather than import) a user's mailbox to a >> remote non-dovecot IMAP account. > > It should be possible at some point, but currently probably won't work > very well. Ah, thanks for the clarification. >> dsync(localuser): Error: user localuser: Initialization failed: >> Namespace '': Unknown mail storage driver imapc >> dsync(localuser): Fatal: User init failed > > But this looks like you simply haven't compiled Dovecot with imapc > support. See if > > dovecot --build-options|grep storage > > returns imapc. Right you are. Joseph Tam <jtam.home(a)gmail.com>

1 0