Re: Email blocking emails

[Aki Tuomi via dovecot]

On 4.12.2019 20.22, Peter Nabbefeld via dovecot wrote:
>
> Hello,
>
> I had troubles getting emails, because this one caused a Sig 6:
> https://p.ip.fi/DGSP
>
> It might be important that I'm using SOLR.
>
> After I removed this mail, I could fetch emails again.
>
> Kind regards
>
> Peter
>
Hi!

I was not able to reproduce this issue with the details we had. Also the
core file was bit of a disappointment, because arch linux compiles
things without debugging symbols and I was not able to come up with a
way to actually see the debugging symbols.

Would it be possible for you to rebuild dovecot package with debugging
symbols, so if this happens again, we could get a backtrace with symbols?

Aki

Re: [2.3.8] possible replication issue

[Piper Andreas via dovecot]

Hello,

upgrading to 2.3.9 unfortunately does *not* solve this issue:

I upgraded one of my replicators from 2.3.7.2 to 2.3.9 and after some 
seconds replication stopped. The other replicator remained with 2.3.7.2. 
After downgrading to 2.3.7.2 replication is again working fine.


I did not try to upgrade both replicators up to now, as this is a live 
production system. Is there a chance, that upgrading both replicators 
will solve the problem?


The machines are running Ubuntu 18.04

Any help is appreciated.

Thanks,
Andreas

Am 18.10.19 um 13:52 schrieb Carsten Rosenberg via dovecot:

Hi,

some of our customers have discovered a replication issue after
upgraded from 2.3.7.2 to 2.3.8.

Running 2.3.8 several replication connections are hanging until defined
timeout. So after some seconds there are $replication_max_conns hanging
connections.
Other replications are running fast and successful.

Also running a doveadm sync tcp:... is working fine for all users.

I can't see exactly, but I haven't seen mailboxes timeouting again and
again. So I would assume it's not related to the mailbox.

 From the logs:

server1:
Oct 16 08:29:25 server1 dovecot[5715]:
dsync-local(userna...@domain.com): Error:
dsync(172.16.0.1): I/O has stalled, no activity for 600 seconds (version
not received)
Oct 16 08:29:25 server1 dovecot[5715]:
dsync-local(userna...@domain.com): Error:
Timeout during state=master_recv_handshake

server2:

Oct 16 08:29:25 server2 dovecot[8113]: doveadm: Error: read(server1)
failed: EOF (last sent=handshake, last recv=handshake)

There aren't any additional logs regarding the replication.

I have tried increasing vsz_limit or reducing replication_max_conns.
Nothing changed.

--

Both customers have 10k+ users. Currently I couldn't reproduce this on
smaller test systems.

Both installation were downgraded to 2.3.7.2 to fix the issue for now

--

I've attached a tcpdump showing the client showing the client stops
sending any data after the mailbox_guid table headers.



Any idea what could be wrong here or the debug this issue?

Thanks.

Carsten Rosenberg




--

Dr. Andreas Piper, Hochschulrechenzentrum der Philipps-Univ. Marburg
  Hans-Meerwein-Straße 6, 35032 Marburg, Germany
Phone: +49 6421 28-23521  Fax: -26994  E-Mail: pi...@hrz.uni-marburg.de



smime.p7s
Description: S/MIME Cryptographic Signature

Solaris crash again (was v2.3.9 released)

[Joseph Tam via dovecot]

On Wed, 4 Dec 2019, Aki Tuomi wrote:


We are pleased to release v2.3.9 of Dovecot. Please find it from
locations below


I compiled this and ran into the same crash problem I reported as
Issue 3 (v2.3.6) in

https://dovecot.org/pipermail/dovecot/2019-July/116413.html

The last 2 messages in the thread contains Timo's analysis of
the problem, and my contributed patch which fixed it.  However,
this patch was not applied to subsequent versions.

https://dovecot.org/pipermail/dovecot/2019-July/116619.html

Is this problem peculiar to Solaris (requiring me to re-apply this
patch for all future versions) or should this patch be applied in
all cases?

Joseph Tam 

How do I set all my mailboxes to "subscribed"

[Steve Litt via dovecot]

Hi all,

I've had a great deal of trouble accessing my Dovecot IMAP from most
supposedly IMAP aware email clients, and have been advised that it
might be because some of my email folders are not subscribed. Is there
s way I can subscribe all my folders? I see no reason to have a folder
not subscribed.

Thanks,

SteveT

Steve Litt 
December 2019 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21

Re: dovecot sieve duplicates detection

[James Cassell via dovecot]

On Wed, Dec 4, 2019, at 1:14 PM, Stephan Bosch via dovecot wrote:
> 
> 
> On 17/08/2018 09:14, Stephan Bosch wrote:
> >
> >
> > Op 14/05/2018 om 23:03 schreef James Cassell:
> >>
> >> On Mon, May 14, 2018, at 4:52 PM, Stephan Bosch wrote:
> >>>
> >>> Op 25/04/2018 om 22:49 schreef James Cassell:
>  On Wed, Apr 25, 2018, at 3:20 PM, Stephan Bosch wrote:
> > Specify the ID used for duplicate checking explicitly using the
> > :uniqueid argument (https://tools.ietf.org/html/rfc7352#section-3.1).
> > Using the variables extenion, compose the uniqueid from the 
> > message-id
> > and the mailbox name.
> >
>  In my experience with dovecot's implementation, you can set the ID 
>  only once in a script.  If you try to filter duplicates based on 
>  multiple IDs, only the first (or last, I don't remember) takes effect.
> 
> >>> Do you have a detailed example of the supposed wrong behavior?
> >>>
> >> I don't have them readily available. Basically, the result of the 
> >> first duplicate test in a script is taken as the result of any future 
> >> duplicate test, even if the parameters to that future duplicate test 
> >> in the same script are different and would otherwise result in a 
> >> different output. The duplicate test is only evaluated once and its 
> >> results are substituted everywhere.
> >>
> >> For example, I might want to flag a message as a new conversation if 
> >> I have not seen another message with the same subject. In the same 
> >> script, I might want to discard messages that are exactly identical 
> >> including message ID among others. The dovecot behavior would be to 
> >> discard all messages that match a subject of previously received 
> >> message.
> >
> > I finally managed to review this issue and I can confirm that this is 
> > a bug.
> 
> Fix released in 2.3.9.
> 

Awesome! Thanks for the followup!

V/r,
James Cassell

Re: dovecot sieve duplicates detection

[Stephan Bosch via dovecot]

On 17/08/2018 09:14, Stephan Bosch wrote:



Op 14/05/2018 om 23:03 schreef James Cassell:


On Mon, May 14, 2018, at 4:52 PM, Stephan Bosch wrote:


Op 25/04/2018 om 22:49 schreef James Cassell:

On Wed, Apr 25, 2018, at 3:20 PM, Stephan Bosch wrote:

Specify the ID used for duplicate checking explicitly using the
:uniqueid argument (https://tools.ietf.org/html/rfc7352#section-3.1).
Using the variables extenion, compose the uniqueid from the 
message-id

and the mailbox name.

In my experience with dovecot's implementation, you can set the ID 
only once in a script.  If you try to filter duplicates based on 
multiple IDs, only the first (or last, I don't remember) takes effect.



Do you have a detailed example of the supposed wrong behavior?

I don't have them readily available. Basically, the result of the 
first duplicate test in a script is taken as the result of any future 
duplicate test, even if the parameters to that future duplicate test 
in the same script are different and would otherwise result in a 
different output. The duplicate test is only evaluated once and its 
results are substituted everywhere.


For example, I might want to flag a message as a new conversation if 
I have not seen another message with the same subject. In the same 
script, I might want to discard messages that are exactly identical 
including message ID among others. The dovecot behavior would be to 
discard all messages that match a subject of previously received 
message.


I finally managed to review this issue and I can confirm that this is 
a bug.


Fix released in 2.3.9.

Regards,

Stephan.

Re: Dovecot 2.3.9 fails on FreeBSD

[Larry Rosenman via dovecot]

yes, larry...@gmail.com == l...@freebsd.org.



On Wed, Dec 4, 2019 at 11:55 AM Pascal Christen via dovecot <
dovecot@dovecot.org> wrote:

> He's the maintainer ;)
>
> > The official FreeBSD ports system does not even have the Dovecot 2.3.9
> > port available yet. I think it is a little premature to start making
> > changes or modifications until the port maintainer has had a chance to
> > avail himself of the problem, if one exists.
> >
>


-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

Re: Dovecot 2.3.9 fails on FreeBSD

[Pascal Christen via dovecot]

He's the maintainer ;)

> The official FreeBSD ports system does not even have the Dovecot 2.3.9
> port available yet. I think it is a little premature to start making
> changes or modifications until the port maintainer has had a chance to
> avail himself of the problem, if one exists.
>

Re: Dovecot 2.3.9 fails on FreeBSD

[Jerry via dovecot]

On Wed, 4 Dec 2019 18:06:58 +0100, Pascal Christen via dovecot stated:
>Hi
>
>I've just tried to build the latest Dovecot 2.3.9 on FreeBSD 11.3.
>Without success...It fails on the following commit which was introduced
>in 2.3.9:
>https://github.com/dovecot/core/commit/c85f1bc3ce612c736c9d2c468cc08306db1b5851
>
>Following output is the build log: https://pastebin.com/3nvSeDn8
>
>So I guess it has to do with some changes FreeBSD made:
>https://reviews.freebsd.org/D18630
>
>
>What do you guys think?
>
>
>Greetings Pascal

The official FreeBSD ports system does not even have the Dovecot 2.3.9
port available yet. I think it is a little premature to start making
changes or modifications until the port maintainer has had a chance to
avail himself of the problem, if one exists.

-- 
Jerry

Re: Dovecot 2.3.9 fails on FreeBSD

[Larry Rosenman via dovecot]

Ignore me, I'm talking about the FreeBSD port, not the actual upstream
sources.

Sorry for the noise.


On Wed, Dec 4, 2019 at 11:40 AM Larry Rosenman  wrote:

> I'm working on the port as we type.  I've already done this patch (will
> add the comments).
>
>
>
> On Wed, Dec 4, 2019 at 11:29 AM Josef 'Jeff' Sipek via dovecot <
> dovecot@dovecot.org> wrote:
>
>> On Wed, Dec 04, 2019 at 12:19:35 -0500, Josef 'Jeff' Sipek via dovecot
>> wrote:
>> > On Wed, Dec 04, 2019 at 18:06:58 +0100, Pascal Christen via dovecot
>> wrote:
>> > > Hi
>> > >
>> > > I've just tried to build the latest Dovecot 2.3.9 on FreeBSD 11.3.
>> > > Without success...It fails on the following commit which was
>> introduced
>> > > in 2.3.9:
>> > >
>> https://github.com/dovecot/core/commit/c85f1bc3ce612c736c9d2c468cc08306db1b5851
>> > >
>> > > Following output is the build log: https://pastebin.com/3nvSeDn8
>> > >
>> > > So I guess it has to do with some changes FreeBSD made:
>> > > https://reviews.freebsd.org/D18630
>> >
>> > As far as I can tell, dovecot should be checking for the existence of
>> > EAI_ADDRFAMILY and EAI_NODATA.
>> >
>> > The good news is, a quick workaround is to remove the two lines that use
>> > these two constants.  (A correct patch would do the proper checks.)
>>
>> Ok.  That was easy.  I'm going to get the following patch reviewed and
>> committed.
>>
>> Jeff.
>>
>> diff --git a/src/lib/net.c b/src/lib/net.c
>> --- a/src/lib/net.c
>> +++ b/src/lib/net.c
>> @@ -1068,13 +1068,17 @@ enum net_hosterror_type net_get_hosterro
>> int error;
>> enum net_hosterror_type type;
>> } error_map[] = {
>> +#ifdef EAI_ADDRFAIMILY /* Obsoleted by RFC 2553bis-02 */
>> { EAI_ADDRFAMILY, NET_HOSTERROR_TYPE_NOT_FOUND },
>> +#endif
>> { EAI_AGAIN, NET_HOSTERROR_TYPE_NAMESERVER },
>> { EAI_BADFLAGS, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
>> { EAI_FAIL, NET_HOSTERROR_TYPE_NAMESERVER },
>> { EAI_FAMILY, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
>> { EAI_MEMORY, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
>> +#ifdef EAI_NODATA /* Obsoleted by RFC 2553bis-02 */
>> { EAI_NODATA, NET_HOSTERROR_TYPE_NOT_FOUND },
>> +#endif
>> { EAI_NONAME, NET_HOSTERROR_TYPE_NOT_FOUND },
>> { EAI_SERVICE, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
>> { EAI_SOCKTYPE, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
>>
>
>
> --
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com
> US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
>


-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

Re: Dovecot 2.3.9 fails on FreeBSD

[Josef 'Jeff' Sipek via dovecot]

On Wed, Dec 04, 2019 at 18:41:45 +0100, Pascal Christen wrote:
> Thanks, build passed on FreeBSD 11.3

It turns out I had a typo in the patch I posted on the mailing list.  I
corrected the typo and it builds fine on 12.1.

Jeff.

   -#ifdef EAI_ADDRFAIMILY /* Obsoleted by RFC 2553bis-02 */
   +#ifdef EAI_ADDRFAMILY /* Obsoleted by RFC 2553bis-02 */

Re: Dovecot 2.3.9 fails on FreeBSD

[Pascal Christen via dovecot]

Thanks, build passed on FreeBSD 11.3

Greetings Pascal

Re: Dovecot 2.3.9 fails on FreeBSD

[Larry Rosenman via dovecot]

I'm working on the port as we type.  I've already done this patch (will add
the comments).



On Wed, Dec 4, 2019 at 11:29 AM Josef 'Jeff' Sipek via dovecot <
dovecot@dovecot.org> wrote:

> On Wed, Dec 04, 2019 at 12:19:35 -0500, Josef 'Jeff' Sipek via dovecot
> wrote:
> > On Wed, Dec 04, 2019 at 18:06:58 +0100, Pascal Christen via dovecot
> wrote:
> > > Hi
> > >
> > > I've just tried to build the latest Dovecot 2.3.9 on FreeBSD 11.3.
> > > Without success...It fails on the following commit which was introduced
> > > in 2.3.9:
> > >
> https://github.com/dovecot/core/commit/c85f1bc3ce612c736c9d2c468cc08306db1b5851
> > >
> > > Following output is the build log: https://pastebin.com/3nvSeDn8
> > >
> > > So I guess it has to do with some changes FreeBSD made:
> > > https://reviews.freebsd.org/D18630
> >
> > As far as I can tell, dovecot should be checking for the existence of
> > EAI_ADDRFAMILY and EAI_NODATA.
> >
> > The good news is, a quick workaround is to remove the two lines that use
> > these two constants.  (A correct patch would do the proper checks.)
>
> Ok.  That was easy.  I'm going to get the following patch reviewed and
> committed.
>
> Jeff.
>
> diff --git a/src/lib/net.c b/src/lib/net.c
> --- a/src/lib/net.c
> +++ b/src/lib/net.c
> @@ -1068,13 +1068,17 @@ enum net_hosterror_type net_get_hosterro
> int error;
> enum net_hosterror_type type;
> } error_map[] = {
> +#ifdef EAI_ADDRFAIMILY /* Obsoleted by RFC 2553bis-02 */
> { EAI_ADDRFAMILY, NET_HOSTERROR_TYPE_NOT_FOUND },
> +#endif
> { EAI_AGAIN, NET_HOSTERROR_TYPE_NAMESERVER },
> { EAI_BADFLAGS, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
> { EAI_FAIL, NET_HOSTERROR_TYPE_NAMESERVER },
> { EAI_FAMILY, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
> { EAI_MEMORY, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
> +#ifdef EAI_NODATA /* Obsoleted by RFC 2553bis-02 */
> { EAI_NODATA, NET_HOSTERROR_TYPE_NOT_FOUND },
> +#endif
> { EAI_NONAME, NET_HOSTERROR_TYPE_NOT_FOUND },
> { EAI_SERVICE, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
> { EAI_SOCKTYPE, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
>


-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

Re: Dovecot 2.3.9 fails on FreeBSD

[Josef 'Jeff' Sipek via dovecot]

On Wed, Dec 04, 2019 at 12:19:35 -0500, Josef 'Jeff' Sipek via dovecot wrote:
> On Wed, Dec 04, 2019 at 18:06:58 +0100, Pascal Christen via dovecot wrote:
> > Hi
> > 
> > I've just tried to build the latest Dovecot 2.3.9 on FreeBSD 11.3.
> > Without success...It fails on the following commit which was introduced
> > in 2.3.9:
> > https://github.com/dovecot/core/commit/c85f1bc3ce612c736c9d2c468cc08306db1b5851
> > 
> > Following output is the build log: https://pastebin.com/3nvSeDn8
> > 
> > So I guess it has to do with some changes FreeBSD made:
> > https://reviews.freebsd.org/D18630
> 
> As far as I can tell, dovecot should be checking for the existence of
> EAI_ADDRFAMILY and EAI_NODATA.
> 
> The good news is, a quick workaround is to remove the two lines that use
> these two constants.  (A correct patch would do the proper checks.)

Ok.  That was easy.  I'm going to get the following patch reviewed and
committed.

Jeff.

diff --git a/src/lib/net.c b/src/lib/net.c
--- a/src/lib/net.c
+++ b/src/lib/net.c
@@ -1068,13 +1068,17 @@ enum net_hosterror_type net_get_hosterro
int error;
enum net_hosterror_type type;
} error_map[] = {
+#ifdef EAI_ADDRFAIMILY /* Obsoleted by RFC 2553bis-02 */
{ EAI_ADDRFAMILY, NET_HOSTERROR_TYPE_NOT_FOUND },
+#endif
{ EAI_AGAIN, NET_HOSTERROR_TYPE_NAMESERVER },
{ EAI_BADFLAGS, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
{ EAI_FAIL, NET_HOSTERROR_TYPE_NAMESERVER },
{ EAI_FAMILY, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
{ EAI_MEMORY, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
+#ifdef EAI_NODATA /* Obsoleted by RFC 2553bis-02 */
{ EAI_NODATA, NET_HOSTERROR_TYPE_NOT_FOUND },
+#endif
{ EAI_NONAME, NET_HOSTERROR_TYPE_NOT_FOUND },
{ EAI_SERVICE, NET_HOSTERROR_TYPE_INTERNAL_ERROR },
{ EAI_SOCKTYPE, NET_HOSTERROR_TYPE_INTERNAL_ERROR },

Re: Dovecot 2.3.9 fails on FreeBSD

[Josef 'Jeff' Sipek via dovecot]

On Wed, Dec 04, 2019 at 18:06:58 +0100, Pascal Christen via dovecot wrote:
> Hi
> 
> I've just tried to build the latest Dovecot 2.3.9 on FreeBSD 11.3.
> Without success...It fails on the following commit which was introduced
> in 2.3.9:
> https://github.com/dovecot/core/commit/c85f1bc3ce612c736c9d2c468cc08306db1b5851
> 
> Following output is the build log: https://pastebin.com/3nvSeDn8
> 
> So I guess it has to do with some changes FreeBSD made:
> https://reviews.freebsd.org/D18630

As far as I can tell, dovecot should be checking for the existence of
EAI_ADDRFAMILY and EAI_NODATA.

The good news is, a quick workaround is to remove the two lines that use
these two constants.  (A correct patch would do the proper checks.)

Jeff.

-- 
Bad pun of the week: The formula 1 control computer suffered from a race
condition

Dovecot 2.3.9 fails on FreeBSD

[Pascal Christen via dovecot]

Hi

I've just tried to build the latest Dovecot 2.3.9 on FreeBSD 11.3.
Without success...It fails on the following commit which was introduced
in 2.3.9:
https://github.com/dovecot/core/commit/c85f1bc3ce612c736c9d2c468cc08306db1b5851

Following output is the build log: https://pastebin.com/3nvSeDn8

So I guess it has to do with some changes FreeBSD made:
https://reviews.freebsd.org/D18630


What do you guys think?


Greetings Pascal

Re: Dovecot 2.3.8 - How to force index creation for user/mailbox?

[Sami Ketola via dovecot]

> On 4 Dec 2019, at 17.15, Tomek Lutelmowski via dovecot  
> wrote:
> 
> Someone who have mailbox in different directory than indexes, can confirm if 
> doveadm can recreate index (after deleting dovecot.index* files) or these 
> files can be created only by connecting with IMAP client? 
> 


[root@example .INBOX]# pwd
/vmail/s...@example.com/index/.INBOX
[root@example .INBOX]# ls
dovecot.index  dovecot.index.cache  dovecot.index.log
[root@example .INBOX]# rm dovecot.index.log 
rm: remove regular file ‘dovecot.index.log’? y
[root@example .INBOX]# doveadm force-resync -u sami INBOX
[root@example .INBOX]# ls -al
total 8228
drwx--  2 vmail vmail  76 Dec  4 15:22 .
drwx-- 13 vmail vmail4096 Nov 25 08:58 ..
-rw---  1 vmail vmail  164080 Dec  4 15:22 dovecot.index
-rw---  1 vmail vmail 8247872 Dec  4 15:21 dovecot.index.cache
-rw---  1 vmail vmail 252 Dec  4 15:22 dovecot.index.log

[root@example .INBOX]# rm dovecot.index.*
rm: remove regular file ‘dovecot.index.cache’? y 
rm: remove regular file ‘dovecot.index.log’? y

[root@example .INBOX]# doveadm index -u sami INBOX
[root@example .INBOX]# doveadm force-resync -u sami INBOX

[root@example .INBOX]# ls -al
total 180
drwx--  2 vmail vmail 76 Dec  4 15:27 .
drwx-- 13 vmail vmail   4096 Nov 25 08:58 ..
-rw---  1 vmail vmail 164080 Dec  4 15:27 dovecot.index
-rw---  1 vmail vmail   5748 Dec  4 15:27 dovecot.index.cache
-rw---  1 vmail vmail308 Dec  4 15:27 dovecot.index.log

[root@example .INBOX]# doveconf -n | grep mail_location
mail_location = Maildir:/vmail/%u/Maildir:INDEX=/vmail/%u/index

[root@ketola .INBOX]# doveadm user sami | grep home
home/vmail/s...@example.com

Sami

Re: Dovecot 2.3.8 - How to force index creation for user/mailbox?

[Tomek Lutelmowski via dovecot]

Someone who have mailbox in different directory than indexes, can confirm
if doveadm can recreate index (after deleting dovecot.index* files) or
these files can be created only by connecting with IMAP client?

śr., 4 gru 2019 o 15:45 Sami Ketola  napisał(a):

>
>
> > On 4 Dec 2019, at 11.48, Tomek Lutelmowski via dovecot <
> dovecot@dovecot.org> wrote:
> >
> > mail_location = maildir:~
> >
>
> can't spot anything obvious wrong. Just spotted that you are storing mails
> in users home root along with all other files such as index files.
>
> Maybe you should store the mailbox contents into Maildir:~/Maildir under
> the users home and index to ~/index/
>
> Sami
>
>
>

Re: Dovecot 2.3.8 - How to force index creation for user/mailbox?

[Sami Ketola via dovecot]

> On 4 Dec 2019, at 11.48, Tomek Lutelmowski via dovecot  
> wrote:
> 
> mail_location = maildir:~
> 

can't spot anything obvious wrong. Just spotted that you are storing mails in 
users home root along with all other files such as index files.

Maybe you should store the mailbox contents into Maildir:~/Maildir under the 
users home and index to ~/index/

Sami

Rootless wiki page is not up to date?

[Marc Roos via dovecot]

If I run a docker image with the mesos containerizer and altering the 
dovecot config mentioned here[1] 

I think the root detection is incorrect because it looks like dovecot is 
still thinking it is root. I still get errors like:


>> log(829825): Fatal: We couldn't drop root group privileges 
(wanted=10053(dovecot), gid=0(root), egid=0(root))

Why does it want to drop to root, if we are not even running as root?

>> Error: service(ipc): chown(/var/dovecot/login/ipc-proxy, 91, 
4294967295) failed: Operation not permitted

Why does it want to chown, when it is not root?


pop3-login: Fatal: setgid(101(dovenull)) failed with 
euid=10053(dovecot), gid=10053(dovecot), egid=10053(dovecot): Operation 
not permitted (This binary should probably be called with process group 
set to 101(dovenull) instead of 10053(dovecot))



[1]
https://wiki.dovecot.org/HowTo/Rootless?action=edit=text

Re: Can't see a specific mail in thunderbird but with mobile mail client

[@lbutlr via dovecot]

On 04 Dec 2019, at 02:36, Sami Ketola  wrote:
> did not notice that you have imap_zlib enabled for protocol imap, can you 
> disable that temporarily and re-record the rawlog.

Is it possible that is the source of the issue? It seems like when I tried to 
test that it did not work with a lot of clients, but I might be thinking of 
something else.


-- 
A Clean House Is A Sign Of A Misspent Life

Re: About "received" header when using Dovecot proxy

[Riku via dovecot]

Hello.

Sorry.
Organize and describe what I want to do.
There may be no unity, but please forgive me.
Also, I'm not good at English, so I'm sorry if it's difficult to understand.

1. I had to create a proxy server for an external SMTP server (here, 
“smtp.example.com” as an example).
So I decided to use Dovecot installed on my server (in this example, 
“my-server.com”).
2. Therefore, the following settings were created.

- /etc/dovecot/conf.d/10-auth.conf -
auth_mechanisms = plain login cram-md5 apop
!include auth-static.conf.ext


- /etc/dovecot/conf.d/auth-static.conf.ext -
passdb {
  driver = static
  args = proxy=y nopassword=y
  default_fields = destuser=%u nologin=y starttls=any-cert
}

userdb {
  driver = static
  args = uid=mail gid=mail /home=/dev/null
}


- /etc/dovecot/conf.d/10-ssl.conf -
ssl = yes
ssl_cert = ]) ...

I want the IP address of the sender (my computer here) to be displayed properly 
in the contents of this "received" like this.

Received: from riku22.net (x.bbtec.net [126.125.xxx.xxx])


Is there any way?

Best regards.

Re: About "received" header when using Dovecot proxy

[Aki Tuomi via dovecot]

On 4.12.2019 15.33, Riku via dovecot wrote:
> Hello.
>
> Sorry.
> Since 2.3.9 was released, I installed it immediately and tried to set 
> "lmtp_add_received_header" to "no".
> But it seems different from what I wanted to do.
> The following is my configuration file.
> Please let me know if there are any other configuration files that need to be 
> listed.
> Is there any way to avoid adding it to the “received” header?
>
> - 20-submission.conf -
> submission_client_workarounds = whitespace-before-path mailbox-for-path
>
> protocol submission {
>   passdb {
> driver = static
> args = proxy=y host=smtp.example.com nopassword=y
>   }
> }
> 
>
> Best regards.


So... what did it do and what did you expect it to do?

Aki

Re: About "received" header when using Dovecot proxy

[Riku via dovecot]

Hello.

Sorry.
Since 2.3.9 was released, I installed it immediately and tried to set 
"lmtp_add_received_header" to "no".
But it seems different from what I wanted to do.
The following is my configuration file.
Please let me know if there are any other configuration files that need to be 
listed.
Is there any way to avoid adding it to the “received” header?

- 20-submission.conf -
submission_client_workarounds = whitespace-before-path mailbox-for-path

protocol submission {
  passdb {
driver = static
args = proxy=y host=smtp.example.com nopassword=y
  }
}


Best regards.

Re: Environment variables in pgsql connect string

[Eirik Rye via dovecot]

I figured this out just moments after writing to this list, actually.

libpq, the Postgresql Library used by Dovecot, will actually use the 
environment variables listed below if their corresponding parameters are 
not provided in the connection string:


  https://www.postgresql.org/docs/8.1/libpq-envars.html

As such, these modifications will allow postgres connection using 
environment variables.


dovecot.conf:

  import_environment = PGUSER PGDATABASE PGPASSWORD

dovecot-sql.conf.ext:

  connect = host=mail-passdb.mail.svc.cluster.local

Then, set the env variables PGUSER, PGDATABASE, PGPASSWORD in the container.

Best regards,
Eirik Rye

On 04/12/2019 13:22, Eirik Rye via dovecot wrote:

Hi,

We are trying to set up a Dovecot Docker image with dynamic database 
configuration based on environment variables, however the variables do 
not appear to be expanded in the "connect=" string of the SQL config.


The documentation states that environment variables, being listed under 
global variables, work "everywhere":



https://doc.dovecot.org/configuration_manual/config_file/config_variables/#variables-global 



However, the source code for driver-pgsql.c indicates that the connect 
string is never expanded:



https://github.com/dovecot/core/blob/master/src/lib-sql/driver-pgsql.c#L297

For reference, this is my configuration. dovecot.conf:

   import_environment = PASSDB_USER PASSDB_DBNAME PASSDB_PASSWORD
   passdb {
     override_fields = proxy=y
     driver = sql
     args = /etc/dovecot/dovecot-sql.conf.ext
   }

/etc/dovecot/dovecot-sql.conf.ext:

   driver = pgsql
   connect = host=mail-passdb dbname=%{env:PASSDB_DBNAME} 
user=%{env:PASSDB_USER} password=%{env:PASSDB_PASSWORD}


Does anyone have any suggestions for how to connect to a database 
without hardcoding the connection parameters in the Dovecot config, 
which does not involve patching driver-pgsql.c to make the variable 
expansion?


Best regards,
Eirik Rye



--
Eirik

Environment variables in pgsql connect string

[Eirik Rye via dovecot]

Hi,

We are trying to set up a Dovecot Docker image with dynamic database 
configuration based on environment variables, however the variables do 
not appear to be expanded in the "connect=" string of the SQL config.


The documentation states that environment variables, being listed under 
global variables, work "everywhere":



https://doc.dovecot.org/configuration_manual/config_file/config_variables/#variables-global

However, the source code for driver-pgsql.c indicates that the connect 
string is never expanded:



https://github.com/dovecot/core/blob/master/src/lib-sql/driver-pgsql.c#L297

For reference, this is my configuration. dovecot.conf:

  import_environment = PASSDB_USER PASSDB_DBNAME PASSDB_PASSWORD
  passdb {
override_fields = proxy=y
driver = sql
args = /etc/dovecot/dovecot-sql.conf.ext
  }

/etc/dovecot/dovecot-sql.conf.ext:

  driver = pgsql
  connect = host=mail-passdb dbname=%{env:PASSDB_DBNAME} 
user=%{env:PASSDB_USER} password=%{env:PASSDB_PASSWORD}


Does anyone have any suggestions for how to connect to a database 
without hardcoding the connection parameters in the Dovecot config, 
which does not involve patching driver-pgsql.c to make the variable 
expansion?


Best regards,
Eirik Rye

Re: some error about dovecot when compile

[Aki Tuomi via dovecot]

Also compiling dovecot is lot easier if you use the tarballs instead of
git sources.

Aki

On 4.12.2019 13.00, Magiczero via dovecot wrote:
> when i build dovecot in my computer, something has occured like below:
>
> root@2030c8624e88:/dovecot-2.3.9# ./autogen.sh
> --2019-12-04 10:49:53--  https://www.dovecot.org/tmp/wiki2-export.tar.gz
> Resolving www.dovecot.org  (www.dovecot.org
> )... 94.237.12.234,
> 2a04:3545:1000:720:acc1:5bff:fe5e:4e9
> Connecting to www.dovecot.org 
> (www.dovecot.org )|94.237.12.234|:443...
> connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 446263 (436K) [application/x-gzip]
> Saving to: 'wiki2-export.tar.gz'
>
> wiki2-export.tar.gz 100%[===>]
> 435.80K   152KB/s    in 2.9s
>
> 2019-12-04 10:49:59 (152 KB/s) - 'wiki2-export.tar.gz' saved
> [446263/446263]
>
> configure.ac:298: warning: macro 'AM_ICONV' not found in library
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> configure.ac:298: warning: macro 'AM_ICONV' not found in library
> configure.ac:22: error: possibly undefined macro: AC_DEFINE
>   If this token and others are legitimate, please use
> m4_pattern_allow.
>   See the Autoconf documentation.
> configure.ac:127: error: possibly undefined macro: dnl
> configure.ac:298: error: possibly undefined macro: AM_ICONV
> configure.ac:429: error: possibly undefined macro: AC_CHECK_HEADER
> configure:24018: error: possibly undefined macro: AC_CHECK_LIB
> configure:25593: error: possibly undefined macro: AC_CHECK_FUNC
> autoreconf: /usr/bin/autoconf failed with exit status: 1
>
> from the information, i think the problem is macro 'AM_ICONV', there
> are any problem in the setup script? i want you help me to solve this
> issue. Thank you.
>
> Best
> MagicZero
>
>
> Sent with ProtonMail  Secure Email.
>

Re: some error about dovecot when compile

[Aki Tuomi via dovecot]

Install gettext

Aki

On 4.12.2019 13.00, Magiczero via dovecot wrote:
> when i build dovecot in my computer, something has occured like below:
>
> root@2030c8624e88:/dovecot-2.3.9# ./autogen.sh
> --2019-12-04 10:49:53--  https://www.dovecot.org/tmp/wiki2-export.tar.gz
> Resolving www.dovecot.org  (www.dovecot.org
> )... 94.237.12.234,
> 2a04:3545:1000:720:acc1:5bff:fe5e:4e9
> Connecting to www.dovecot.org 
> (www.dovecot.org )|94.237.12.234|:443...
> connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 446263 (436K) [application/x-gzip]
> Saving to: 'wiki2-export.tar.gz'
>
> wiki2-export.tar.gz 100%[===>]
> 435.80K   152KB/s    in 2.9s
>
> 2019-12-04 10:49:59 (152 KB/s) - 'wiki2-export.tar.gz' saved
> [446263/446263]
>
> configure.ac:298: warning: macro 'AM_ICONV' not found in library
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> configure.ac:298: warning: macro 'AM_ICONV' not found in library
> configure.ac:22: error: possibly undefined macro: AC_DEFINE
>   If this token and others are legitimate, please use
> m4_pattern_allow.
>   See the Autoconf documentation.
> configure.ac:127: error: possibly undefined macro: dnl
> configure.ac:298: error: possibly undefined macro: AM_ICONV
> configure.ac:429: error: possibly undefined macro: AC_CHECK_HEADER
> configure:24018: error: possibly undefined macro: AC_CHECK_LIB
> configure:25593: error: possibly undefined macro: AC_CHECK_FUNC
> autoreconf: /usr/bin/autoconf failed with exit status: 1
>
> from the information, i think the problem is macro 'AM_ICONV', there
> are any problem in the setup script? i want you help me to solve this
> issue. Thank you.
>
> Best
> MagicZero
>
>
> Sent with ProtonMail  Secure Email.
>

some error about dovecot when compile

[Magiczero via dovecot]

when i build dovecot in my computer, something has occured like below:

root@2030c8624e88:/dovecot-2.3.9# ./autogen.sh
--2019-12-04 10:49:53--  https://www.dovecot.org/tmp/wiki2-export.tar.gz
Resolving www.dovecot.org (www.dovecot.org)... 94.237.12.234, 
2a04:3545:1000:720:acc1:5bff:fe5e:4e9
Connecting to www.dovecot.org (www.dovecot.org)|94.237.12.234|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 446263 (436K) [application/x-gzip]
Saving to: 'wiki2-export.tar.gz'

wiki2-export.tar.gz 100%[===>] 435.80K   
152KB/sin 2.9s

2019-12-04 10:49:59 (152 KB/s) - 'wiki2-export.tar.gz' saved [446263/446263]

configure.ac:298: warning: macro 'AM_ICONV' not found in library
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:298: warning: macro 'AM_ICONV' not found in library
configure.ac:22: error: possibly undefined macro: AC_DEFINE
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
configure.ac:127: error: possibly undefined macro: dnl
configure.ac:298: error: possibly undefined macro: AM_ICONV
configure.ac:429: error: possibly undefined macro: AC_CHECK_HEADER
configure:24018: error: possibly undefined macro: AC_CHECK_LIB
configure:25593: error: possibly undefined macro: AC_CHECK_FUNC
autoreconf: /usr/bin/autoconf failed with exit status: 1

from the information, i think the problem is macro 'AM_ICONV', there are any 
problem in the setup script? i want you help me to solve this issue. Thank you.

Best
MagicZero

Sent with [ProtonMail](https://protonmail.com) Secure Email.

Pigeonhole v0.5.9 released

[Aki Tuomi via dovecot]

Hi all!

We are pleased to release v0.5.9 of Pigeonhole. Please find it from
locations below

---

Aki Tuomi
Open-Xchange oy

https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.9.tar.gz
https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.9.tar.gz.sig
Binary packages in https://repo.dovecot.org/
Docker images in https://hub.docker.com/r/dovecot/dovecot

---

+ Added events for Sieve and ManageSieve, see
  https://doc.dovecot.org/admin_manual/list_of_events/#pigeonhole
+ Pigeonhole: Implement the Sieve "special-use" extension described in
  RFC 8579.
- duplicate: Test only compared the handles which would cause
  different values to be cached as the same duplicate test. Fix to also
  compare the actual hashes.
- imap_sieve_filter: IMAP FILTER Command had various bugs in error
  handling. Errors may have been duplicated for each email, errors
  may have been missing entirely, command tag and ERRORS/WARNINGS
  parameters were swapped.




signature.asc
Description: OpenPGP digital signature

v2.3.9 released

[Aki Tuomi via dovecot]

Hi all!

We are pleased to release v2.3.9 of Dovecot. Please find it from
locations below

---

Aki Tuomi
Open-Xchange oy

https://dovecot.org/releases/2.3/dovecot-2.3.9.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.9.tar.gz.sig
Binary packages in https://repo.dovecot.org/
Docker images in https://hub.docker.com/r/dovecot/dovecot

---

* Changed several event field names for consistency and to avoid
  conflicts in parent-child event relationships:
   * SMTP server command events: Renamed "name" to "cmd_name"
   * Events inheriting from a mailbox: Renamed "name" to "mailbox"
   * Server connection events have only "remote_ip", "remote_port",
 "local_ip" and "local_port".
   * Removed duplicate "client_ip", "ip" and "port".
   * Mail storage events: Removed "service" field.
 Use "service:" category instead.
   * HTTP client connection events: Renamed "host" to "dest_host" and
 "port" to "dest_port"
* auth: Drop Postfix socketmap support. It hasn't been working
  with recent Postfix versions for a while now.
* push-notification-lua: The "subject" field is now decoded to UTF8
  instead of kept as MIME-encoded.
+ push-notification-lua: Added new "from_address", "from_display_name",
  "to_address" and "to_display_name" fields. The display names are
  decoded to UTF8.
+ Added various new fields to existing events.
  See http://doc.dovecot.net/admin_manual/list_of_events.html
+ Add lmtp_add_received_header setting. It can be used to prevent LMTP
  from adding "Received:" headers.
+ doveadm: Support SSL/STARTTLS for proxied doveadm connections based on
  doveadm_ssl setting and proxy ssl/tls settings.
+ Log filters support now "service:", which matches all events for
  the given service. It can also be used as a category.
+ lib: Use libunwind to get abort backtraces with function names
  where available.
+ lmtp: When the LMTP proxy changes the username (from passdb lookup)
  add an appropriate ORCPT parameter.
- lmtp: Add lmtp_client_workarounds setting to implement workarounds for
  clients that send MAIL and RCPT commands with additional spaces before
  the path and for clients that omit <> brackets around the path.
  See example-config/conf.d/20-lmtp.conf.
- lda/lmtp: Invalid MAIL FROM addresses were rejcted too aggressively.
  Now mails from addresses with unicode characters are delivered, but
  their Return-Path header will be <> instead of the given MAIL FROM
  address.
- lmtp: The lmtp_hdr_delivery_address setting is ignored.
- imap: imap_command_finished event's "args" and "human_args" parameters
  were always empty.
- mbox: Seeking in zlib and bzip2 compressed input streams didn't work
  correctly.
- imap-hibernate: Process crashed when client got destroyed while it was
  attempted to be unhibernated, and the unhibernation fails.
- *-login: Proxying may have crashed if SSL handshake to the backend
  failed immediately. This was unlikely to happen in normal operation.
- *-login: If TLS handshake to upstream server failed during proxying,
  login process could crash due to invalid memory access.
- *-login: v2.3 regression: Using SASL authentication without initial
  response may have caused SSL connections to hang. This happened often
  at least with PHP's IMAP library.
- *-login: When login processes are flooded with authentication attempts
  it starts logging errors about "Authentication server sent unknown id".
  This is still expected. However, it also caused the login process to
  disconnect from auth server and potentially log some user's password
  in the error message.
- dict-sql: SQL prepared statements were not shared between sessions.
  This resulted in creating a lot of prepared statements, which was
  especially inefficient when using Cassandra backend with a lot of
  Cassandra nodes.
- auth: auth_request_finished event didn't have success=yes parameter
  set for successful authentications.
- auth: userdb dict - Trying to list users crashed.
- submission: Service could be configured to allow anonymous
  authentication mechanism and anonymous user access.
- LAYOUT=index: Corrupted dovecot.list.index caused folder creation to
  panic.
- doveadm: HTTP server crashes if request target starts with double "/".
- dsync: Remote dsync started hanging if the initial doveadm
  "dsync-server" command was sent in the same TCP packet as the
  following dsync handshake. v2.3.8 regression.
- lib: Several "input streams" had a bug that in some rare situations
  might cause it to access freed memory. This could lead to crashes or
  corruption.
  The only currently known effect of this is that using zlib plugin with
  external mail attachments (mail_attachment_dir) could cause fetching
  the mail to return a few bytes of garbage data at the beginning of the
  header. Note that the mail wasn't saved corrupted, but fetching it
  caused corrupted mail to be sent to the client.
- lib-storage: If a mail only has quoted content, use the quoted text
  for generating message snippet (IMAP PREVIEW) 

[Dovecot-news] Pigeonhole v0.5.9 released

[Aki Tuomi via Dovecot-news]

Hi all!

We are pleased to release v0.5.9 of Pigeonhole. Please find it from
locations below

---

Aki Tuomi
Open-Xchange oy

https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.9.tar.gz
https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.9.tar.gz.sig
Binary packages in https://repo.dovecot.org/
Docker images in https://hub.docker.com/r/dovecot/dovecot

---

+ Added events for Sieve and ManageSieve, see
  https://doc.dovecot.org/admin_manual/list_of_events/#pigeonhole
+ Pigeonhole: Implement the Sieve "special-use" extension described in
  RFC 8579.
- duplicate: Test only compared the handles which would cause
  different values to be cached as the same duplicate test. Fix to also
  compare the actual hashes.
- imap_sieve_filter: IMAP FILTER Command had various bugs in error
  handling. Errors may have been duplicated for each email, errors
  may have been missing entirely, command tag and ERRORS/WARNINGS
  parameters were swapped.




signature.asc
Description: OpenPGP digital signature
___
Dovecot-news mailing list
Dovecot-news@dovecot.org
https://dovecot.org/mailman/listinfo/dovecot-news

[Dovecot-news] v2.3.9 released

[Aki Tuomi via Dovecot-news]

Hi all!

We are pleased to release v2.3.9 of Dovecot. Please find it from
locations below

---

Aki Tuomi
Open-Xchange oy

https://dovecot.org/releases/2.3/dovecot-2.3.9.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.9.tar.gz.sig
Binary packages in https://repo.dovecot.org/
Docker images in https://hub.docker.com/r/dovecot/dovecot

---

* Changed several event field names for consistency and to avoid
  conflicts in parent-child event relationships:
   * SMTP server command events: Renamed "name" to "cmd_name"
   * Events inheriting from a mailbox: Renamed "name" to "mailbox"
   * Server connection events have only "remote_ip", "remote_port",
 "local_ip" and "local_port".
   * Removed duplicate "client_ip", "ip" and "port".
   * Mail storage events: Removed "service" field.
 Use "service:" category instead.
   * HTTP client connection events: Renamed "host" to "dest_host" and
 "port" to "dest_port"
* auth: Drop Postfix socketmap support. It hasn't been working
  with recent Postfix versions for a while now.
* push-notification-lua: The "subject" field is now decoded to UTF8
  instead of kept as MIME-encoded.
+ push-notification-lua: Added new "from_address", "from_display_name",
  "to_address" and "to_display_name" fields. The display names are
  decoded to UTF8.
+ Added various new fields to existing events.
  See http://doc.dovecot.net/admin_manual/list_of_events.html
+ Add lmtp_add_received_header setting. It can be used to prevent LMTP
  from adding "Received:" headers.
+ doveadm: Support SSL/STARTTLS for proxied doveadm connections based on
  doveadm_ssl setting and proxy ssl/tls settings.
+ Log filters support now "service:", which matches all events for
  the given service. It can also be used as a category.
+ lib: Use libunwind to get abort backtraces with function names
  where available.
+ lmtp: When the LMTP proxy changes the username (from passdb lookup)
  add an appropriate ORCPT parameter.
- lmtp: Add lmtp_client_workarounds setting to implement workarounds for
  clients that send MAIL and RCPT commands with additional spaces before
  the path and for clients that omit <> brackets around the path.
  See example-config/conf.d/20-lmtp.conf.
- lda/lmtp: Invalid MAIL FROM addresses were rejcted too aggressively.
  Now mails from addresses with unicode characters are delivered, but
  their Return-Path header will be <> instead of the given MAIL FROM
  address.
- lmtp: The lmtp_hdr_delivery_address setting is ignored.
- imap: imap_command_finished event's "args" and "human_args" parameters
  were always empty.
- mbox: Seeking in zlib and bzip2 compressed input streams didn't work
  correctly.
- imap-hibernate: Process crashed when client got destroyed while it was
  attempted to be unhibernated, and the unhibernation fails.
- *-login: Proxying may have crashed if SSL handshake to the backend
  failed immediately. This was unlikely to happen in normal operation.
- *-login: If TLS handshake to upstream server failed during proxying,
  login process could crash due to invalid memory access.
- *-login: v2.3 regression: Using SASL authentication without initial
  response may have caused SSL connections to hang. This happened often
  at least with PHP's IMAP library.
- *-login: When login processes are flooded with authentication attempts
  it starts logging errors about "Authentication server sent unknown id".
  This is still expected. However, it also caused the login process to
  disconnect from auth server and potentially log some user's password
  in the error message.
- dict-sql: SQL prepared statements were not shared between sessions.
  This resulted in creating a lot of prepared statements, which was
  especially inefficient when using Cassandra backend with a lot of
  Cassandra nodes.
- auth: auth_request_finished event didn't have success=yes parameter
  set for successful authentications.
- auth: userdb dict - Trying to list users crashed.
- submission: Service could be configured to allow anonymous
  authentication mechanism and anonymous user access.
- LAYOUT=index: Corrupted dovecot.list.index caused folder creation to
  panic.
- doveadm: HTTP server crashes if request target starts with double "/".
- dsync: Remote dsync started hanging if the initial doveadm
  "dsync-server" command was sent in the same TCP packet as the
  following dsync handshake. v2.3.8 regression.
- lib: Several "input streams" had a bug that in some rare situations
  might cause it to access freed memory. This could lead to crashes or
  corruption.
  The only currently known effect of this is that using zlib plugin with
  external mail attachments (mail_attachment_dir) could cause fetching
  the mail to return a few bytes of garbage data at the beginning of the
  header. Note that the mail wasn't saved corrupted, but fetching it
  caused corrupted mail to be sent to the client.
- lib-storage: If a mail only has quoted content, use the quoted text
  for generating message snippet (IMAP PREVIEW) 

Re: Dovecot 2.3.8 - How to force index creation for user/mailbox?

[Tomek Lutelmowski via dovecot]

Here is doveconf -n output:

# 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.8 (b7b03ba2)
# OS: Linux 5.4.1-gentoo x86_64 Gentoo Base System release 2.6
# Hostname: mail..com
auth_cache_negative_ttl = 0
auth_cache_size = 10 M
auth_cache_ttl = 4 hours
auth_default_realm = .com
auth_master_user_separator = *
auth_verbose = yes
auth_verbose_passwords = plain
default_vsz_limit = 1 G
disable_plaintext_auth = no
listen = *
login_greeting = IMAP ready.
mail_gid = mail
mail_location = maildir:~
mail_plugins = zlib fts fts_lucene virtual acl
mailbox_idle_check_interval = 3 secs
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 index ihave
duplicate mime foreverypart extracttext
namespace {
  list = children
  location = maildir:/e/.com/mail-shared:INDEXPVT=~/Maildir/public/
  mailbox poczta {
auto = no
  }
  prefix = Wspólne/
  separator = /
  subscriptions = no
  type = shared
}
namespace inbox {
  inbox = yes
  list = yes
  location =
  mailbox "Elementy usunięte" {
auto = subscribe
special_use = \Trash
  }
  mailbox "Elementy wysłane" {
auto = subscribe
special_use = \Sent
  }
  mailbox "Wersje robocze" {
auto = subscribe
special_use = \Drafts
  }
  mailbox Wiadomości-śmieci {
auto = subscribe
special_use = \Junk
  }
  prefix =
  separator = /
  type = private
}
passdb {
  args = /etc/dovecot/dovecot-sql-master.conf.ext
  driver = sql
  master = yes
  pass = yes
}
passdb {
  args = /etc/dovecot/dovecot-sql.conf.ext
  driver = sql
}
plugin {
  acl = vfile
  fts = lucene
  fts_autoindex = yes
  fts_lucene = whitespace_chars="@.-_()[]{}<>/\\+"
  mail_log_fields = uid box msgid from subject size
  sieve = file:~/sieve;active=~/sieve/sieve.active
  sieve_before = /etc/dovecot/sieve/global.sieve
  sieve_global = /etc/dovecot/sieve
  sieve_vacation_dont_check_recipient = yes
  sieve_vacation_use_original_recipient = yes
  zlib_save = xz
  zlib_save_level = 9
}
pop3_uidl_format = %v.%u
protocols = imap lmtp sieve
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
  }
}
service imap-login {
  process_min_avail = 10
  service_count = 1
  unix_listener imap {
mode = 0666
  }
}
service imap-postlogin {
  executable = script-login /usr/local/bin/postlogin.sh
  user = $default_internal_user
}
service imap {
  client_limit = 1
  executable = imap imap-postlogin
}
service lmtp {
  unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
  }
  vsz_limit = 4 G
}
service managesieve-login {
  inet_listener sieve {
address = 127.0.0.1
port = 4190
  }
}
ssl_ca =  napisał(a):

> Hi,
>
> then please post doveconf -n
>
> Sami
>
>
> On 3 Dec 2019, at 21.31, Tomek Lutelmowski via dovecot <
> dovecot@dovecot.org> wrote:
>
> Neither of dovecot.index files are created (.cache, .log, .thread) - these
> files are created when I open the folder with IMAP client. When mailbox is
> not used for long time, the indexing takes very long time. So I'm looking
> for any solution (preferably with doveadm) to manually reindex folders in
> background.
>
> wt., 3 gru 2019 o 20:23 Aki Tuomi  napisał(a):
>
>> Wait, did you mean 'dovecot.index' file? That file is only created
>> occasionally, the actual index is kept in dovecot.index.log.
>>
>> Aki
>>
>> > On 03/12/2019 21:20 Tomek Lutelmowski via dovecot 
>> wrote:
>> >
>> >
>> > Thanks, but both commands didn't create dovecot.index. Only when I open
>> folder with IMAP client, the dovecot.index is created.
>> >
>> >
>> > wt., 3 gru 2019 o 18:16 Aki Tuomi 
>> napisał(a):
>> > >
>> > >  > On 03/12/2019 18:30 Tomek Lutelmowski via dovecot <
>> dovecot@dovecot.org> wrote:
>> > >  >
>> > >  >
>> > >  > Hello,
>> > >  >
>> > >  > I'm using maildirs, and I have problems with big mailboxes (~
>> 2 emails, 30-50GB) - sometimes access to such mailbox takes very long
>> (~10 minutes), I would like to be able to create index for mailbox in
>> background, but I couldn't find any way to do it. So far I tried:
>> > >  >
>> > >  > doveadm -D -vvv index -u user 'Folder'
>> > >  >
>> > >  > But even if this folder have no dovecot.index* files - I always
>> get:
>> > >  >
>> > >  > doveadm(user): Info: Wersje robocze: Cache is already up to date
>> > >  >
>> > >  > It seems that doveadm doesn't actually checks if the index is
>> present. The index is created only when I log with IMAP client and check
>> the folder.
>> > >  >
>> > >  > So i tried:
>> > >  > doveadm mailbox cache purge -u user 'Folder'
>> > >  >
>> > >  > No joy either:
>> > >  > doveadm(user): Error: Cache is unusable
>> > >  >
>> > >  > And command below doesn't actually do anything to index:
>> > >  > doveadm -vvv force-resync -u user 'Folder'
>> > >  >

Re: Can't see a specific mail in thunderbird but with mobile mail client

[Sami Ketola via dovecot]

Hi,

did not notice that you have imap_zlib enabled for protocol imap, can you 
disable that temporarily and re-record the rawlog.

Sami


> On 4 Dec 2019, at 11.22, J. Echter via dovecot  wrote:
> 
> Hi,
> 
> i did but it seems to contain garbage to me.
> 
> here's the .in file:
> 
> 1575450806.299222 2 COMPRESS DEFLATE
> 1575450806.300114 2V�tQЧPʧĶMURP
> 1575450806.300114 
> �(�KI-J�,J^A��R��3���,3^K=#=#%M^.^@^@^@^@��2Q(N�IM.QP��s��P��^B^@^@^@��2U^H^E^Z��Z���`h���^^^LT
> 1575450806.304341 
> ^@^@^@��2^C^Z^E^@^@^@��r��^C�^@^@^@^@��2W���/��^B^@^@^@���@Rnafibi��^G^@^@^@��d��^N�
>  ^XE_�^[u��H�k��?qh�gS��^@&��ݜ{sr�^?-̜&"˜b�eT�3�Ϝ^V�^$
> 1575450825.607399 �e*��}Bm�Аk
> jl��_�^D�^]z�tH��r�u}�p$�(��^N�F^O{|���q� ^L�8<"���^D4��q@���5=^?^C^@^@��24 
> ��^HG��^@^@^@^@��24��^P^@^@^@^P^@^@^@��24R(�LQ(.�/J���
> ���_~�Wi^6P^S^@^@^@��24�j^B^@^@^@���h^B^@^@^@��24��+^@^@^@��24E��^L9`^A^@^@^@��2��^F^@^@^@���h^C^@^@^@��2�E^G^@^@^@��2Ĉ^O^Tm^@^@^@^@��2Ĉ^P3+
>  ej`0T�^E^@^@^@��2^È^WKB�^$
> �
> 
> ^P^F^@^@^@^@��2�(^W ^Y`iff`�0^@^@^@^@��2�(9 
> ^X`dfdhb�0^@^@^@^@��2�@O�^VX^R1^@^@^@��2�%+^@^@^@^@���$+^@^@^@^@%+^@^@^@^@HV���
> 1575451333.497661 ^@^@^@HVX^Zƃ3Y^A^@^@^@HV^Dۃ�^@^@^@^@���0A^OJK,A 
>   ^@^@^@���0�^F%^@^@^@��
> 
> 
> Am 04.12.19 um 09:49 schrieb Sami Ketola via dovecot:
>> Hi,
>> 
>> please record IMAP rawlog from the client session to see what the client 
>> requests and what dovecot responds.
>> 
>> https://wiki2.dovecot.org/Debugging/Rawlog 
>> 
>> 
>> Sami
>> 
>> 
>>> On 4 Dec 2019, at 10.44, J. Echter via dovecot >> > wrote:
>>> 
>>> 
>>> Am 03.12.19 um 12:32 schrieb J. Echter via dovecot:
 Hi,
 
 i've seen a strange behaviour in our system (centos 7, dovecot 2.2.36
 (1f10bfa63) today.
 
 We got a mail and it got delivered.
 
 Dec  3 07:56:25 mail postfix/lmtp[4013]: 915B0CEF4C2: to=,
 relay=mail[private/dovecot-lmtp], delay=1.5, delays=1.3/0.03/0.02/0.19,
 dsn=2.0.0, status=sent (250 2.0.0  AOhCNBgH5l2vDwAAtnFApQ:2
 Saved)
 Dec  3 07:56:25 mail dovecot: lmtp(user@domain):
 AOhCNBgH5l2vDwAAtnFApQ:2: sieve:
 msgid=<289913405.81.1575356173625.JavaMail.SYSTEM@EUWS0716>: stored mail
 into mailbox 'INBOX'
 
 I also see this mail on the filesystem in the users cur dir:
 
 -rw-r--r--.  1 vmail vmail  448818  3. Dez 07:56
 1575356184.M937345P4015.mail,S=611100,W=619338:2,Sae
 
 But i don't see this single mail in thunderbird and not in sogo
 (http://www.sogo.nu ), but i can see it in the mobile 
 mail client.
 
 Does anyone have a suggfestion what may be wrong here?
 
 I paste my dovecot -n output here:
 
 # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf
 # Pigeonhole version 0.4.24 (124e06aa)
 # OS: Linux 3.10.0-1062.4.3.el7.x86_64 x86_64 CentOS Linux release
 7.7.1908 (Core) xfs
 # Hostname: mail.workgroup.local
 auth_master_user_separator = *
 auth_verbose = yes
 base_dir = /var/run/dovecot/
 default_vsz_limit = 2 G
 imap_id_log = *
 imap_id_send = *
 log_timestamp = "%Y-%m-%d %H:%M:%S "
 login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k
 mail_gid = 5000
 mail_home = /DATEN/vmail/%Ld/%Ln
 mail_location = maildir:/DATEN/vmail/%Ld/%Ln/mail/
 mail_plugins = " zlib fts fts_solr mail_log notify"
 mail_uid = 5000
 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 ihave
 namespace inbox {
   inbox = yes
   location =
   mailbox Archive {
 auto = no
 special_use = \Archive
   }
   mailbox Archives {
 auto = subscribe
 special_use = \Archive
   }
   mailbox Drafts {
 auto = subscribe
 special_use = \Drafts
   }
   mailbox Junk {
 auto = subscribe
 special_use = \Junk
   }
   mailbox Sent {
 auto = subscribe
 special_use = \Sent
   }
   mailbox "Sent Messages" {
 special_use = \Sent
   }
   mailbox Spam {
 auto = no
 special_use = \Junk
   }
   mailbox Trash {
 auto = subscribe
 special_use = \Trash
   }
   prefix =
 }
 passdb {
   args = /etc/dovecot/passwd.masterusers
   driver = passwd-file
   master = yes
 }
 passdb {
   args = /etc/dovecot/dovecot-ldap.conf
   driver = ldap
 }
 plugin {
   fts = solr
   fts_autoindex = yes
   fts_solr = break-imap-search url=http://localhost:8983/solr/dovecot/ 
 
   imapsieve_mailbox1_before = file:/etc/dovecot/sieve/learn-spam.sieve 

Re: Can't see a specific mail in thunderbird but with mobile mail client

[Benny Pedersen via dovecot]

On 2019-12-04 10:22, J. Echter via dovecot wrote:


here's the .in file:


not possible to decode binariers from 7bit content

Re: Can't see a specific mail in thunderbird but with mobile mail client

[J. Echter via dovecot]

Hi,

i did but it seems to contain garbage to me.

here's the .in file:

1575450806.299222 2 COMPRESS DEFLATE
1575450806.300114 2V�tQЧPʧĶMURP
1575450806.300114
�(�KI-J�,J^A��R��3���,3^K=#=#%M^.^@^@^@^@��2Q(N�IM.QP��s��P��^B^@^@^@��2U^H^E^Z��Z���`h���^^^LT
1575450806.304341
^@^@^@��2^C^Z^E^@^@^@��r��^C�^@^@^@^@��2W���/��^B^@^@^@���@Rnafibi��^G^@^@^@��d��^N�
^XE_�^[u��H�k��?qh�gS��^@&��ݜ{sr�^?-̜&"˜b�eT�3�Ϝ^V�^$
1575450825.607399 �e*��}Bm�Аk
jl��_�^D�^]z�tH��r�u}�p$�(��^N�F^O{|���q�
^L�8<"���^D4��q@���5=^?^C^@^@��24
��^HG��^@^@^@^@��24��^P^@^@^@^P^@^@^@��24R(�LQ(.�/J���
���_~�Wi^6P^S^@^@^@��24�j^B^@^@^@���h^B^@^@^@��24��+^@^@^@��24E��^L9`^A^@^@^@��2��^F^@^@^@���h^C^@^@^@��2�E^G^@^@^@��2Ĉ^O^Tm^@^@^@^@��2Ĉ^P3+
ej`0T�^E^@^@^@��2^È^WKB�^$
�

^P^F^@^@^@^@��2�(^W ^Y`iff`�0^@^@^@^@��2�(9
^X`dfdhb�0^@^@^@^@��2�@O�^VX^R1^@^@^@��2�%+^@^@^@^@���$+^@^@^@^@%+^@^@^@^@HV���
1575451333.497661
^@^@^@HVX^Zƃ3Y^A^@^@^@HV^Dۃ�^@^@^@^@���0A^OJK,A  
^@^@^@���0�^F%^@^@^@��

Am 04.12.19 um 09:49 schrieb Sami Ketola via dovecot:
> Hi,
>
> please record IMAP rawlog from the client session to see what the
> client requests and what dovecot responds.
>
> https://wiki2.dovecot.org/Debugging/Rawlog
>
> Sami
>
>
>> On 4 Dec 2019, at 10.44, J. Echter via dovecot > > wrote:
>>
>>
>> Am 03.12.19 um 12:32 schrieb J. Echter via dovecot:
>>> Hi,
>>>
>>> i've seen a strange behaviour in our system (centos 7, dovecot 2.2.36
>>> (1f10bfa63) today.
>>>
>>> We got a mail and it got delivered.
>>>
>>> Dec  3 07:56:25 mail postfix/lmtp[4013]: 915B0CEF4C2: to=,
>>> relay=mail[private/dovecot-lmtp], delay=1.5, delays=1.3/0.03/0.02/0.19,
>>> dsn=2.0.0, status=sent (250 2.0.0  AOhCNBgH5l2vDwAAtnFApQ:2
>>> Saved)
>>> Dec  3 07:56:25 mail dovecot: lmtp(user@domain):
>>> AOhCNBgH5l2vDwAAtnFApQ:2: sieve:
>>> msgid=<289913405.81.1575356173625.JavaMail.SYSTEM@EUWS0716>: stored mail
>>> into mailbox 'INBOX'
>>>
>>> I also see this mail on the filesystem in the users cur dir:
>>>
>>> -rw-r--r--.  1 vmail vmail  448818  3. Dez 07:56
>>> 1575356184.M937345P4015.mail,S=611100,W=619338:2,Sae
>>>
>>> But i don't see this single mail in thunderbird and not in sogo
>>> (http://www.sogo.nu), but i can see it in the mobile mail client.
>>>
>>> Does anyone have a suggfestion what may be wrong here?
>>>
>>> I paste my dovecot -n output here:
>>>
>>> # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf
>>> # Pigeonhole version 0.4.24 (124e06aa)
>>> # OS: Linux 3.10.0-1062.4.3.el7.x86_64 x86_64 CentOS Linux release
>>> 7.7.1908 (Core) xfs
>>> # Hostname: mail.workgroup.local
>>> auth_master_user_separator = *
>>> auth_verbose = yes
>>> base_dir = /var/run/dovecot/
>>> default_vsz_limit = 2 G
>>> imap_id_log = *
>>> imap_id_send = *
>>> log_timestamp = "%Y-%m-%d %H:%M:%S "
>>> login_log_format_elements = user=<%u> method=%m rip=%r lip=%l
>>> mpid=%e %c %k
>>> mail_gid = 5000
>>> mail_home = /DATEN/vmail/%Ld/%Ln
>>> mail_location = maildir:/DATEN/vmail/%Ld/%Ln/mail/
>>> mail_plugins = " zlib fts fts_solr mail_log notify"
>>> mail_uid = 5000
>>> 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 ihave
>>> namespace inbox {
>>>   inbox = yes
>>>   location =
>>>   mailbox Archive {
>>>     auto = no
>>>     special_use = \Archive
>>>   }
>>>   mailbox Archives {
>>>     auto = subscribe
>>>     special_use = \Archive
>>>   }
>>>   mailbox Drafts {
>>>     auto = subscribe
>>>     special_use = \Drafts
>>>   }
>>>   mailbox Junk {
>>>     auto = subscribe
>>>     special_use = \Junk
>>>   }
>>>   mailbox Sent {
>>>     auto = subscribe
>>>     special_use = \Sent
>>>   }
>>>   mailbox "Sent Messages" {
>>>     special_use = \Sent
>>>   }
>>>   mailbox Spam {
>>>     auto = no
>>>     special_use = \Junk
>>>   }
>>>   mailbox Trash {
>>>     auto = subscribe
>>>     special_use = \Trash
>>>   }
>>>   prefix =
>>> }
>>> passdb {
>>>   args = /etc/dovecot/passwd.masterusers
>>>   driver = passwd-file
>>>   master = yes
>>> }
>>> passdb {
>>>   args = /etc/dovecot/dovecot-ldap.conf
>>>   driver = ldap
>>> }
>>> plugin {
>>>   fts = solr
>>>   fts_autoindex = yes
>>>   fts_solr = break-imap-search url=http://localhost:8983/solr/dovecot/
>>>   imapsieve_mailbox1_before = file:/etc/dovecot/sieve/learn-spam.sieve
>>>   imapsieve_mailbox1_causes = COPY
>>>   imapsieve_mailbox1_name = Junk
>>>   imapsieve_mailbox2_before = file:/etc/dovecot/sieve/learn-ham.sieve
>>>   imapsieve_mailbox2_causes = COPY
>>>   imapsieve_mailbox2_from = Junk
>>>   imapsieve_mailbox2_name = *
>>>   mail_log_events = delete undelete expunge copy mailbox_delete
>>> mailbox_rename
>>>   mail_log_fields = uid box msgid size
>>>   mailbox_alias_new = Sent Messages
>>>   mailbox_alias_new2 = Sent Items
>>>   mailbox_alias_new3 = Deleted 

Re: Can't see a specific mail in thunderbird but with mobile mail client

[Sami Ketola via dovecot]

Hi,

please record IMAP rawlog from the client session to see what the client 
requests and what dovecot responds.

https://wiki2.dovecot.org/Debugging/Rawlog 


Sami


> On 4 Dec 2019, at 10.44, J. Echter via dovecot  wrote:
> 
> 
> Am 03.12.19 um 12:32 schrieb J. Echter via dovecot:
>> Hi,
>> 
>> i've seen a strange behaviour in our system (centos 7, dovecot 2.2.36
>> (1f10bfa63) today.
>> 
>> We got a mail and it got delivered.
>> 
>> Dec  3 07:56:25 mail postfix/lmtp[4013]: 915B0CEF4C2: to=,
>> relay=mail[private/dovecot-lmtp], delay=1.5, delays=1.3/0.03/0.02/0.19,
>> dsn=2.0.0, status=sent (250 2.0.0  AOhCNBgH5l2vDwAAtnFApQ:2
>> Saved)
>> Dec  3 07:56:25 mail dovecot: lmtp(user@domain):
>> AOhCNBgH5l2vDwAAtnFApQ:2: sieve:
>> msgid=<289913405.81.1575356173625.JavaMail.SYSTEM@EUWS0716>: stored mail
>> into mailbox 'INBOX'
>> 
>> I also see this mail on the filesystem in the users cur dir:
>> 
>> -rw-r--r--.  1 vmail vmail  448818  3. Dez 07:56
>> 1575356184.M937345P4015.mail,S=611100,W=619338:2,Sae
>> 
>> But i don't see this single mail in thunderbird and not in sogo
>> (http://www.sogo.nu), but i can see it in the mobile mail client.
>> 
>> Does anyone have a suggfestion what may be wrong here?
>> 
>> I paste my dovecot -n output here:
>> 
>> # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf
>> # Pigeonhole version 0.4.24 (124e06aa)
>> # OS: Linux 3.10.0-1062.4.3.el7.x86_64 x86_64 CentOS Linux release
>> 7.7.1908 (Core) xfs
>> # Hostname: mail.workgroup.local
>> auth_master_user_separator = *
>> auth_verbose = yes
>> base_dir = /var/run/dovecot/
>> default_vsz_limit = 2 G
>> imap_id_log = *
>> imap_id_send = *
>> log_timestamp = "%Y-%m-%d %H:%M:%S "
>> login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k
>> mail_gid = 5000
>> mail_home = /DATEN/vmail/%Ld/%Ln
>> mail_location = maildir:/DATEN/vmail/%Ld/%Ln/mail/
>> mail_plugins = " zlib fts fts_solr mail_log notify"
>> mail_uid = 5000
>> 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 ihave
>> namespace inbox {
>>   inbox = yes
>>   location =
>>   mailbox Archive {
>> auto = no
>> special_use = \Archive
>>   }
>>   mailbox Archives {
>> auto = subscribe
>> special_use = \Archive
>>   }
>>   mailbox Drafts {
>> auto = subscribe
>> special_use = \Drafts
>>   }
>>   mailbox Junk {
>> auto = subscribe
>> special_use = \Junk
>>   }
>>   mailbox Sent {
>> auto = subscribe
>> special_use = \Sent
>>   }
>>   mailbox "Sent Messages" {
>> special_use = \Sent
>>   }
>>   mailbox Spam {
>> auto = no
>> special_use = \Junk
>>   }
>>   mailbox Trash {
>> auto = subscribe
>> special_use = \Trash
>>   }
>>   prefix =
>> }
>> passdb {
>>   args = /etc/dovecot/passwd.masterusers
>>   driver = passwd-file
>>   master = yes
>> }
>> passdb {
>>   args = /etc/dovecot/dovecot-ldap.conf
>>   driver = ldap
>> }
>> plugin {
>>   fts = solr
>>   fts_autoindex = yes
>>   fts_solr = break-imap-search url=http://localhost:8983/solr/dovecot/
>>   imapsieve_mailbox1_before = file:/etc/dovecot/sieve/learn-spam.sieve
>>   imapsieve_mailbox1_causes = COPY
>>   imapsieve_mailbox1_name = Junk
>>   imapsieve_mailbox2_before = file:/etc/dovecot/sieve/learn-ham.sieve
>>   imapsieve_mailbox2_causes = COPY
>>   imapsieve_mailbox2_from = Junk
>>   imapsieve_mailbox2_name = *
>>   mail_log_events = delete undelete expunge copy mailbox_delete
>> mailbox_rename
>>   mail_log_fields = uid box msgid size
>>   mailbox_alias_new = Sent Messages
>>   mailbox_alias_new2 = Sent Items
>>   mailbox_alias_new3 = Deleted Messages
>>   mailbox_alias_new4 = Papierkorb
>>   mailbox_alias_new5 = Spam
>>   mailbox_alias_old = Sent
>>   mailbox_alias_old2 = Sent
>>   mailbox_alias_old3 = Trash
>>   mailbox_alias_old4 = Trash
>>   mailbox_alias_old5 = Junk
>>   mailbox_list_index = yes
>>   recipient_delimiter = +
>>   sieve = /DATEN/vmail/%Ld/%Ln/.dovecot.sieve
>>   sieve_after = /etc/dovecot/sieve-after
>>   sieve_global_extensions = +vnd.dovecot.pipe
>>   sieve_pipe_bin_dir = /usr/bin
>>   sieve_plugins = sieve_imapsieve sieve_extprograms
>>   zlib_save = gz
>>   zlib_save_level = 6
>> }
>> protocols = sieve imap lmtp
>> service auth {
>>   unix_listener /var/spool/postfix/private/auth {
>> group = postfix
>> mode = 0660
>> user = postfix
>>   }
>>   unix_listener auth-userdb {
>> group = vmail
>> mode = 0660
>> user = vmail
>>   }
>>   user = root
>> }
>> service imap-login {
>>   chroot = login
>>   executable = /usr/libexec/dovecot/imap-login
>>   inet_listener imap {
>> port = 0
>>   }
>>   process_min_avail = 4
>>   user = dovecot
>> }
>> service imap {
>>   executable = /usr/libexec/dovecot/imap
>> }
>> service lmtp {
>>   unix_listener 

Re: Can't see a specific mail in thunderbird but with mobile mail client

[J. Echter via dovecot]

Am 03.12.19 um 12:32 schrieb J. Echter via dovecot:
> Hi,
>
> i've seen a strange behaviour in our system (centos 7, dovecot 2.2.36
> (1f10bfa63) today.
>
> We got a mail and it got delivered.
>
> Dec  3 07:56:25 mail postfix/lmtp[4013]: 915B0CEF4C2: to=,
> relay=mail[private/dovecot-lmtp], delay=1.5, delays=1.3/0.03/0.02/0.19,
> dsn=2.0.0, status=sent (250 2.0.0  AOhCNBgH5l2vDwAAtnFApQ:2
> Saved)
> Dec  3 07:56:25 mail dovecot: lmtp(user@domain):
> AOhCNBgH5l2vDwAAtnFApQ:2: sieve:
> msgid=<289913405.81.1575356173625.JavaMail.SYSTEM@EUWS0716>: stored mail
> into mailbox 'INBOX'
>
> I also see this mail on the filesystem in the users cur dir:
>
> -rw-r--r--.  1 vmail vmail  448818  3. Dez 07:56
> 1575356184.M937345P4015.mail,S=611100,W=619338:2,Sae
>
> But i don't see this single mail in thunderbird and not in sogo
> (http://www.sogo.nu), but i can see it in the mobile mail client.
>
> Does anyone have a suggfestion what may be wrong here?
>
> I paste my dovecot -n output here:
>
> # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.4.24 (124e06aa)
> # OS: Linux 3.10.0-1062.4.3.el7.x86_64 x86_64 CentOS Linux release
> 7.7.1908 (Core) xfs
> # Hostname: mail.workgroup.local
> auth_master_user_separator = *
> auth_verbose = yes
> base_dir = /var/run/dovecot/
> default_vsz_limit = 2 G
> imap_id_log = *
> imap_id_send = *
> log_timestamp = "%Y-%m-%d %H:%M:%S "
> login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k
> mail_gid = 5000
> mail_home = /DATEN/vmail/%Ld/%Ln
> mail_location = maildir:/DATEN/vmail/%Ld/%Ln/mail/
> mail_plugins = " zlib fts fts_solr mail_log notify"
> mail_uid = 5000
> 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 ihave
> namespace inbox {
>   inbox = yes
>   location =
>   mailbox Archive {
>     auto = no
>     special_use = \Archive
>   }
>   mailbox Archives {
>     auto = subscribe
>     special_use = \Archive
>   }
>   mailbox Drafts {
>     auto = subscribe
>     special_use = \Drafts
>   }
>   mailbox Junk {
>     auto = subscribe
>     special_use = \Junk
>   }
>   mailbox Sent {
>     auto = subscribe
>     special_use = \Sent
>   }
>   mailbox "Sent Messages" {
>     special_use = \Sent
>   }
>   mailbox Spam {
>     auto = no
>     special_use = \Junk
>   }
>   mailbox Trash {
>     auto = subscribe
>     special_use = \Trash
>   }
>   prefix =
> }
> passdb {
>   args = /etc/dovecot/passwd.masterusers
>   driver = passwd-file
>   master = yes
> }
> passdb {
>   args = /etc/dovecot/dovecot-ldap.conf
>   driver = ldap
> }
> plugin {
>   fts = solr
>   fts_autoindex = yes
>   fts_solr = break-imap-search url=http://localhost:8983/solr/dovecot/
>   imapsieve_mailbox1_before = file:/etc/dovecot/sieve/learn-spam.sieve
>   imapsieve_mailbox1_causes = COPY
>   imapsieve_mailbox1_name = Junk
>   imapsieve_mailbox2_before = file:/etc/dovecot/sieve/learn-ham.sieve
>   imapsieve_mailbox2_causes = COPY
>   imapsieve_mailbox2_from = Junk
>   imapsieve_mailbox2_name = *
>   mail_log_events = delete undelete expunge copy mailbox_delete
> mailbox_rename
>   mail_log_fields = uid box msgid size
>   mailbox_alias_new = Sent Messages
>   mailbox_alias_new2 = Sent Items
>   mailbox_alias_new3 = Deleted Messages
>   mailbox_alias_new4 = Papierkorb
>   mailbox_alias_new5 = Spam
>   mailbox_alias_old = Sent
>   mailbox_alias_old2 = Sent
>   mailbox_alias_old3 = Trash
>   mailbox_alias_old4 = Trash
>   mailbox_alias_old5 = Junk
>   mailbox_list_index = yes
>   recipient_delimiter = +
>   sieve = /DATEN/vmail/%Ld/%Ln/.dovecot.sieve
>   sieve_after = /etc/dovecot/sieve-after
>   sieve_global_extensions = +vnd.dovecot.pipe
>   sieve_pipe_bin_dir = /usr/bin
>   sieve_plugins = sieve_imapsieve sieve_extprograms
>   zlib_save = gz
>   zlib_save_level = 6
> }
> protocols = sieve imap lmtp
> service auth {
>   unix_listener /var/spool/postfix/private/auth {
>     group = postfix
>     mode = 0660
>     user = postfix
>   }
>   unix_listener auth-userdb {
>     group = vmail
>     mode = 0660
>     user = vmail
>   }
>   user = root
> }
> service imap-login {
>   chroot = login
>   executable = /usr/libexec/dovecot/imap-login
>   inet_listener imap {
>     port = 0
>   }
>   process_min_avail = 4
>   user = dovecot
> }
> service imap {
>   executable = /usr/libexec/dovecot/imap
> }
> service lmtp {
>   unix_listener /var/spool/postfix/private/dovecot-lmtp {
>     group = postfix
>     mode = 0600
>     user = postfix
>   }
> }
> service managesieve-login {
>   chroot = login
>   user = dovecot
> }
> service pop3-login {
>   chroot = login
>   user = dovecot
> }
> ssl = required
> ssl_cert =  ssl_key =  # hidden, use -P to show it
> userdb {
>   args = /etc/dovecot/dovecot-ldap.conf
>   driver = ldap
> }
> valid_chroot_dirs = /var/spool/vmail
> protocol lda {