gmane.mail.imap.dovecot

Error: dict client sent broken reply

Chris Richards — 2013-05-19T21:33:52

I've been mucking about, experimenting with the expire plugin and using a
dictionary.  I've got the iteration query working when I do a normal
expunge using:

doveadm expunge -A mailbox "INBOX.Trash" savedbefore 1w

and expunging works as expected.  However, I've got over 12,000 accounts
on this server, so I was hoping using the expire plugin to could help out.
 I've configured the plugin, and things kinda work, except that somewhere
between 3700 and 3800 users, I abort with this:

doveadm(someuseraccount< at >somedomain): Error: dict client
(/var/run/dovecot/dict) sent broken reply
doveadm(someuseraccount< at >somedomain): Error: Dictionary iteration failed
doveadm: Error: Failed to iterate through some users

It consistently fails at the same user.  If I delete that user from the
expire database, then it appears to fail on the next user.

I also see this in the logs:

dovecot: dict: Error: dict client: COMMIT: Can't commit while iterating

I've absolutely no idea where to go from here to troubleshoot this.  Any
guid

Re: doveadm altmove to gzipped-mdbox

Timo Sirainen — 2013-05-19T19:34:32

I think that command should have worked, assuming zlib plugin was
loaded. But it would have compressed mails in the primary storage as
well for those files where it was moving mails away from (altmove runs
implicit purge).

Re: Configure dovecot to provide SASL authentication

Reindl Harald — 2013-05-19T16:00:53


Am 19.05.2013 17:51, schrieb Peter Skensved:

chmod 666 is always a very bad idea


service auth {
  unix_listener /var/spool/postfix/private/auth {
  mode  = 0660
  user  = postfix
  group = postfix
 }
}

Configure dovecot to provide SASL authentication

Peter Skensved — 2013-05-19T15:51:12

   Hi,
  I'm trying to get dovecot to provide SASL authentication for
postfix My setup appears to be working but I'm not 100% certain
I've got it right. I've come across several examples for dovecot
version 1 but I'm running 2.0.9.  The output of doveconf -n is here :

 2.0.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-279.2.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) 
auth_debug = yes
auth_verbose = yes
disable_plaintext_auth = no
mbox_write_locks = fcntl
passdb {
  driver = pam
}
protocols = imap
service auth {
  unix_listener /var/spool/postfix/private/auth {
    mode = 0666
  }
}
ssl_cert = </etc/pki/dovecot/certs/dovecot.pem
ssl_key = </etc/pki/dovecot/private/dovecot.pem
userdb {
  driver = passwd
}


 Specifically : are the "service auth", userdb and passdb
sections correct ? And the mode ? Or is it too permissive ?


  For completeness the postfix setup is here :

smtpd_sasl_auth_enable = yes
broken_sasl_auth_clients = yes
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
smtpd_sasl_secur

Re: Dovecot 2.2.1 LDA and sieve (lack of) errors

Jim McNamara — 2013-05-18T23:32:32

I found that LDA was not being executed from the user's .qmail-default 
file, I changed that file to call a non-existent delivery agent, and the 
message still ended up in the inbox, not sorted as it should have been, 
so vpopmail was still handling the delivery. This is a qmail issue, 
simply renaming .qmail-default to .qmail in that user's vpopmail 
directory allowed lda to begin functioning.

Now this is interesting - I do have Pigeonhole and sieve enabled 
according to doveconf -n, but the only mention of sieve is as a 
subdirectory of the user's home, no mention of the sieve module at all. 
I do see that Pigeonhole 0.4.0 is enabled. Also, there have only been 0 
mentions of lda in the current dovecot log, and that log is 6 hours old.

I'll try running dovecot-lda manually after checking out the man page.

Thanks again for the help!

Re: Pigeonhole: extprograms - pipe

Stephan Bosch — 2013-05-18T21:54:15

I must say I haven't tested the use of the script service in a while and 
it is not part of the test suite. I've tried it at my end and I can 
reproduce the error.

I'll look at this more thoroughly tomorrow.


Regards,

Stephan.

Re: Dovecot 2.2.1 LDA and sieve (lack of) errors

Stephan Bosch — 2013-05-18T21:35:13

So, mail_debug is enabled.


Are you sure this is actually being executed? What happens if you 
execute dovecot-lda manually?

This is an example of what you're supposed to see in the logs with 
mail_debug=yes:

May 18 23:28:02 klara dovecot: lda: Debug: Loading modules from 
directory: /usr/lib/dovecot/modules
May 18 23:28:02 klara dovecot: lda: Debug: Module loaded: 
/usr/lib/dovecot/modules/lib90_sieve_plugin.so
May 18 23:28:02 klara dovecot: lda(stephan): Debug: Effective uid=1000, 
gid=1000, home=/home/stephan
May 18 23:28:02 klara dovecot: lda(stephan): Debug: Namespace inbox: 
type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, 
subscriptions=yes location=maildir:~/Maildir
May 18 23:28:02 klara dovecot: lda(stephan): Debug: maildir++: 
root=/home/stephan/Maildir, index=, indexpvt=, control=, 
inbox=/home/stephan/Maildir, alt=
May 18 23:28:02 klara dovecot: lda(stephan): Debug: userdb lookup 
skipped, username taken from USER environment
May 18 23:28:02 klara dovecot: lda(stephan): Debug: non

Dovecot 2.2.1 LDA and sieve (lack of) errors

Jim McNamara — 2013-05-18T14:56:10

Hello again, all. Of course after posting yesterday that all was well 
with my setup, turns out all is not well. The problem I'm having is with 
dovecot-lda functioning and making deliveries to my mailbox, but the 
sieve scripts don't seem to have any effect. Attempts at logging what 
is/isn't happening have been total failures.

Managesieve seems to work fine, port 4190 is open on the server and it 
allows the tunderbird plugin to function, I can create and edit scripts 
with the plugin. For some reason it doesn't seem to auto-compile the 
scripts to binary form, but if I just need to do that manually I can 
live with it. I only mention the lack of auto-compiling in case that 
sheds light on what is wrong with the LDA or sieve.

I'm running the current dovecot, 2.2.1 along with pigeonhole 0.4.0. Here 
is the config:

root< at >hostname:/usr/local/dovecot-2.2.1# doveconf -n
# 2.2.1: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.0
auth_cache_size = 10 M
auth_default_realm = mail.dom

Re: How to configure ssl cert chain in dovecot 10-ssl.conf file

Gedalya — 2013-05-18T09:48:27

That should be the correct way, but I think there shouldn't be a space
after the < character.
What exactly is the error you are getting?

You can troubleshoot with openssl s_client, this is from my server:

$ openssl s_client -connect 192.168.xxx.xxx:143 -starttls imap -CApath
/etc/ssl/certs
CONNECTED(00000003)
depth=2 C = IL, O = StartCom Ltd., OU = Secure Digital Certificate
Signing, CN = StartCom Certification Authority
verify return:1
depth=1 C = IL, O = StartCom Ltd., OU = Secure Digital Certificate
Signing, CN = StartCom Class 1 Primary Intermediate Server CA
verify return:1
depth=0 description = 7t3YlXVfb6bVQ2pp, C = US, CN = mail.gedalya.net,
emailAddress = ______< at >gedalya.net
verify return:1
---
Certificate chain
0
s:/description=7t3YlXVfb6bVQ2pp/C=US/CN=mail.gedalya.net/emailAddress=postmaster< at >gedalya.net
i:/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate
Signing/CN=StartCom Class 1 Primary Intermediate Server CA
1 s:/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate
Signing/CN=StartCom Class 1

How to configure ssl cert chain in dovecot 10-ssl.conffile

Bu Xiaobing — 2013-05-18T09:06:09

Hi there,

Does anyone know how to do this:

"Put all the certificates in the ssl_cert file. For example when using a certificate signed by TDC the correct order is:

    Dovecot's public certificate
    TDC SSL Server CA
    TDC Internet Root CA
    Globalsign Partners CA "

I try to set these parameters in the conf.d/10-ssl.conf as below, but it seems doesn't work.

---
ssl_cert = </etc/pki/dovecot/certs/mail.mymailserver.com.crt
ssl_cert = </etc/ssl/certs/dovecot/sub.class1.server.ca.pem
ssl_cert = </etc/ssl/certs/dovecot/ca.pem
----

I even cat mail.mymailserver.com.crt sub.class1.server.ca.pem certs/dovecot/ca.pem into one singe file, and define ssl_cert = < /path/to/the/singcertfile.pem, but it doesn't work too.

In my apache httpd server httpd.conf file  I can define:
--
SSLCertificateChainFile /etc/pki/dovecot/certs/sub.class1.server.ca.pem
SSLCACertificateFile /etc/pki/dovecot/certs/ca.pem
--
And it well work fine.

Thinks for any suggest.
Bu Xiaobing

Re: Pigeonhole: extprograms - pipe

Anes Mukhametov — 2013-05-18T07:58:28

No result:

[root< at >backend1 scripts]# cat spam.sh
#!/bin/bash

cat > /dev/null

exit 0
[root< at >backend1 scripts]#

In the log: May 17 22:42:56 backend1 dovecot: script: Error:
write(response) failed: Broken pipe

:(

On Sat, May 18, 2013 at 2:05 AM, Ben Morrow <ben< at >morrow.me.uk> wrote:

Re: Sieve was installed but doesn't work or log

Noel Butler — 2013-05-18T01:35:10




No problems Jim, glad it's all sorted.

Re: Pigeonhole: extprograms - pipe

Ben Morrow — 2013-05-17T22:05:01

I suspect that what's happening here is that your script isn't reading
the whole mail. However, that pipe that's broken is (I think) the socket
from the script service back to the master service, so I don't quite
understand how that could happen.


Mmm, recursively-referential error logs. Always fun...


Well, you shouldn't do that: redirecting stdin from /dev/null in a shell
script will close the incoming pipe, which means you won't read the mail
at all and sieve will get upset. What you need to do instead (if you've
got data to read and nothing to do with it) is 'cat >/dev/null', which
will read it all and throw it away.


Hmm. Are you sure your real script is exitting with 0? spamc in learn
mode exits 5 or 6 depending on whether the mail was already learned or
not.

Ben

Pigeonhole: extprograms - pipe

Anes Mukhametov — 2013-05-17T15:41:53

Hello!

I've tried to use extprograms pipe feature but stuck with "Broken pipe"
errors in mail log:

May 17 15:18:57 backend1 dovecot: lmtp(20338, user< at >domain.tld): Debug:
3VMVFWFKllFyTwAArRg8UA: sieve: action pipe: running program: learn
May 17 15:18:57 backend1 dovecot: script: Error: write(response) failed:
Broken pipe
May 17 15:18:57 backend1 dovecot: lmtp(20338, user< at >domain.tld):
3VMVFWFKllFyTwAArRg8UA: sieve: execution of script
/data/mail/storage/domain/user< at >domain.tld/.dovecot.sieve;name=main script
failed, but implicit keep was successful (user logfile
/data/mail/storage/domain/buser< at >domain.tld/.dovecot.sieve.log should reveal
additional details)

/data/mail/storage/domain/buser< at >domain.tld/.dovecot.sieve.log:
error: msgid=<c7cd36f19be8164addf091a646b8b284< at >domain.tld>: pipe action:
failed to pipe message to program `learn': refer to server log for more
information. [2013-05-17 15:18:57] ham user< at >domain.tld 50796.


Sieve script contents:
require ["fileinto","copy","mailbox","vnd.dovecot.pipe"];

if a

(no subject)

Anes Mukhametov — 2013-05-17T15:40:01

Hello!

I've tried to use extprograms pipe feature but stuck with "Broken pipe"
errors in mail log:

May 17 15:18:57 backend1 dovecot: lmtp(20338, user< at >domain.tld): Debug:
3VMVFWFKllFyTwAArRg8UA: sieve: action pipe: running program: learn
May 17 15:18:57 backend1 dovecot: script: Error: write(response) failed:
Broken pipe
May 17 15:18:57 backend1 dovecot: lmtp(20338, user< at >domain.tld):
3VMVFWFKllFyTwAArRg8UA: sieve: execution of script
/data/mail/storage/domain/user< at >domain.tld/.dovecot.sieve;name=main script
failed, but implicit keep was successful (user logfile
/data/mail/storage/domain/buser< at >domain.tld/.dovecot.sieve.log should reveal
additional details)

/data/mail/storage/domain/buser< at >domain.tld/.dovecot.sieve.log:
error: msgid=<c7cd36f19be8164addf091a646b8b284< at >domain.tld>: pipe action:
failed to pipe message to program `learn': refer to server log for more
information. [2013-05-17 15:18:57] ham user< at >domain.tld 50796.


Sieve script contents:
require ["fileinto","copy","mailbox","vnd.dovecot.pipe"];

if a

Re: Sieve was installed but doesn't work or log

Jim McNamara — 2013-05-17T14:47:28

Thank you for the solid suggestion, Noel! I now have Dovecot 2.2.1 along 
with Pigeonhole 0.4.0. All is working well at present. The largest 
issues I encountered was getting the configuration changed and 
functional from my previous 1.2.8 to 2.0. Once that was accomplished 
things more or less proceeded well. Managesieve works wonderfully, can 
dovecot creates the .sieve directory and its subdirectory .sieve/tmp 
correctly, the thunderbird plugin for sieve is able to connect and 
everything works, compilation happens automatically and the sieve 
scripts are functional.

I use John Simpson's Qmail patch/setup on the server, I wasn't able to 
find a current dovecot config that worked with vpopmail without mysql. 
Here is my current config which works for me in this setup:

root< at >hostname:/home/jim# doveconf -n
# 2.2.1: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.0
auth_cache_size = 10 M
auth_default_realm = mail.domain.com
auth_mechanisms = plain login
auth_socket_path = /usr/

doveadm altmove to gzipped-mdbox

Claus — 2013-05-17T13:59:08

Hi,

im wondering if it's possible to store old messages in a compressed 
mdbox on alternate storage.
The main storage is uncompressed mdbox.

I tried something like: doveadm -Dv -o "plugin/zlib_save=gz" altmove -u 
testuser sentbefore 8d

Could someone tell me if it's possible and give me a hint how this can 
be done?

I tried this with dovecot-2.2

Claus

Re: Make install error

Ben Morrow — 2013-05-17T11:12:34

That's weird, and wrong. Also, I can't reproduce it; if I run 

    ./configure --prefix=/usr/local/dovecot
    grep ^libexec config.log

in the 2.2.1 tarball I get

    libexecdir='${exec_prefix}/libexec'

as I would have expected. Are you sure you didn't pass a --libexecdir
argument to configure?

Ben

Re: Ubuntu-12.04-LTS repos with Dovecot-2.2 and Pigeonhole

Robert Schetterer — 2013-05-17T09:31:54

Am 17.05.2013 10:13, schrieb Stephan Bosch:

Hi Stephan ,your rep ist stable enough for me since years ,so thx !!!


Best Regards
MfG Robert Schetterer

Re: Ubuntu-12.04-LTS repos with Dovecot-2.2 and Pigeonhole

Stephan Bosch — 2013-05-17T08:13:32

Hi Eric and Robert,

Op 5/17/2013 8:23 AM, Eric Kom wrote:

http://wiki2.dovecot.org/PrebuiltBinaries:

"The builder scripts automatically release a new set of Debian packages 
when they notice any changes in any of the v2.0,v2.1 or v2.2 repositories. "

and

"Needless to say: do *NOT* use these repositories for systems that need 
to be *STABLE*."

Please keep that in mind if you point people to this repository. Also, 
as you may have noticed, this repository is not particularly reliable in 
terms of uptime.

It is not the first time Rename-IT gets actual phone calls (that 
eventually get forwarded to me somehow) from some admin in dire need of 
a quick bug fix, because he's using this repository for a production 
server. I am not particularly fond of the awesome power to break a set 
of production servers with one bad commit.

On 16/05/2013 19:30, listas< at >adminlinux.com.br wrote:

The Xi repository obviously does not provide what he needs.

Regards,

Stephan.

Re: Ubuntu-12.04-LTS repos with Dovecot-2.2 and Pigeonhole

Robert Schetterer — 2013-05-17T06:35:23

Am 16.05.2013 19:30, schrieb listas< at >adminlinux.com.br:

http://xi.rename-it.nl/debian/pool/testing-auto/dovecot-2.2/
but  you can simply compile it from source on 12.04 for small testings
without any major problems

Best Regards
MfG Robert Schetterer