imap-login segfaulting on 2.3.1

Hello, I have a new director ring I am setting up on centos 7 with dovecot 2.3.1. I haven't been able to replecate this in testing, but as soon as I start pushing production traffic to the new ring I see dozens of these in the logs: Apr 18 00:34:00 d.director.imapd.sonic.net kernel:

Re: dovecot sieve duplicates detection

On 23/04/18 14:18, Stephan Bosch wrote: Op 11-4-2018 om 23:58 schreef André Rodier: Hello, I have tested the sieve duplicate script with success so far, but I have a question. Sieve duplicate script? You mean the Sieve duplicate extension (RFC 7352)? I would like to know if the

Re: question about using cram-md5 login passwords

On April 23, 2018 9:45:22 AM EDT, Aki Tuomi wrote: > >> On 23 April 2018 at 16:14 "Fabian A. Santiago" > wrote: >> >> >> hello dovecot community, >> >> question; if my user database and dovecot installation is currently >setup to use plain

Re: lost connection while sending end of data error

# 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1 (d9bc6dfe) # OS: FreeBSD 11.1-RELEASE-p8 amd64 ufs # Hostname: server2.example.com auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no first_valid_gid = 0 first_valid_uid = 1001

Re: question about using cram-md5 login passwords

> On 23 April 2018 at 16:14 "Fabian A. Santiago" > wrote: > > > hello dovecot community, > > question; if my user database and dovecot installation is currently setup to > use plain login passwords, and i want to convert to cram-md5, after i > configure dovecot

Re: Sieve "redirect" changes envelope sender in 2.3. / pigeonhole 0.5

On 04/23/2018 03:22 PM, Stephan Bosch wrote: Op 20-4-2018 om 14:01 schreef Olaf Hopp: Hi (Stephan?), is it a new feature of dovecot 2.3 /pigeonhole 0.5 that a sieve "redirect" changes the envelope sender of a redirected mail or simply a bug ? A sends mail to B, B redirects to C C sees B

Re: lost connection while sending end of data error

What is your configuration (`dovecot -n`)? Op 19-4-2018 om 20:45 schreef Christos Chatzaras: I use dovecot-lmtp and postfix. When I send e-mail to 2 recipients (or more) at the same time and if one of them is over quota (or under quota and the message I send is bigger than his free space)

Re: Sieve "redirect" changes envelope sender in 2.3. / pigeonhole 0.5

Op 20-4-2018 om 14:01 schreef Olaf Hopp: Hi (Stephan?), is it a new feature of dovecot 2.3 /pigeonhole 0.5 that a sieve "redirect" changes the envelope sender of a redirected mail or simply a bug ? A sends mail to B, B redirects to C C sees B (not A!) as envelope sender. It is not a problem

Re: dovecot sieve duplicates detection

Op 11-4-2018 om 23:58 schreef André Rodier: Hello, I have tested the sieve duplicate script with success so far, but I have a question. Sieve duplicate script? You mean the Sieve duplicate extension (RFC 7352)? I would like to know if the "duplicate" sieve flag in Dovecot is global to all

question about using cram-md5 login passwords

hello dovecot community, question; if my user database and dovecot installation is currently setup to use plain login passwords, and i want to convert to cram-md5, after i configure dovecot accordingly and reset passwords into cram-md5, if anyone uses plain login method again in the future,

Re: Merging mailboxes with doveadm

The command you are looking for is doveadm import ---Aki TuomiDovecot oy Original message From: Carsten Schmitz Date: 23/04/2018 15:46 (GMT+02:00) To: dovecot@dovecot.org Subject: Merging mailboxes with doveadm Hello, I am trying to

Merging mailboxes with doveadm

Hello, I am trying to merge(=copy) all mails of all user mailboxes into one mailbox for one-time archival purposes. The command I am using is  sudo doveadm -v copy -A arch...@somedomain.net ALL The error I get for every mailbox is: doveadm(someus...@somedomain.net): Error: Can't open

Re: Sieve "redirect" changes envelope sender in 2.3. / pigeonhole 0.5

On 04/23/2018 07:28 AM, Steffen Kaiser wrote: Envelope *senders* should never ever be modified. If the domain of sender A has SPF records installed and B redirects to C, but keeps the envelope sender A, the SPF check will fail on C. That's the reason why I say SPF is broken by design.