Re: Dsync issues since 2.3.11.3.

[Reio Remma]

On 28/09/2020 11:00, Reio Remma wrote:

Hello!

I've started seeing intermittent dsync failures since upgrading 
Dovecot to 2.3.11.3-3 (CentOS 8 using the official Dovecot repo).


Sep 27 17:49:04 host dovecot[130]: 
dsync-local(user@host)<5GWFD2CmcF+TJwAAsNnMGQ>: Warning: Failed to do 
incremental sync for mailbox INBOX, retry with a full sync (Modseq 
66543 no longer in transaction log (highest=66547, 
last_common_uid=46346, nextuid=46347))
Sep 27 17:49:04 host dovecot[130]: 
dsync-local(user@host)<5GWFD2CmcF+TJwAAsNnMGQ>: Error: Remote command 
returned error 75: ssh  doveadm dsync-server -u user@host


It seems to happen at random times to random users.

My setup has 2 servers - users are connecting to the main server and 
the secondary server is just for backup - noone is actually connecting 
to it.


Today I encountered a new error amidst the previous ones:

dsync-local(user@host): Error: Mailbox 
INBOX.Trash: /var/vmail/domain/user/Maildir/.Trash/dovecot.index.log: 
Transaction log modseq tracking is corrupted - fixing


Reio

Sieve not exists

[@lbutlr]

I thought this was working as intended, but I have recently been getting some 
random messages put into this mailbox that definitely have list-ip headers 
(including some messages from this list) and that do not have multiple 
addresses. I believe this started happening on 20200922, which would hav been 
when I applied the most recent update to dovecot, as that is when the listCC 
box seemed to explode, but I do not have traces over 7 days old.

if allof (address :count "ge" :comparator "i;ascii-numeric" ["to", "cc"] ["2"],
  not exists ["list-id","mailing-list", "x-loop"] )
{
fileinto :create "listCC";
stop;}

Headers of a message that triggered this (minus Received and signature headers, 
just removed for length)

This is the trace:

  23: address test
  23:   starting `:count-ge' match with `i;ascii-numeric' comparator:
  23:   extracting `to' headers from message
  23:   parsing address header value `Kurt Jaeger , 
dovecot@dovecot.org'
  23:   address value `dove...@opsec.eu'
  23:   address value `dovecot@dovecot.org'
  23:   extracting `cc' headers from message
  23:   matching count value `2'
  23: with key `2' => 1
  23:   finishing match with result: matched

So, it looks like it is matching Reply-To and/or X-Original-To as well as To? 
Or is something else happening here?

  23: jump if result is false
  23:   not jumping
  24: exists test
  24:   header `list-id' exists
  24:   header `mailing-list' is missing
  24:   headers are missing
  24: jump if result is true
  24:   not jumping

Or the logic of "not exists" has changed from AND (meaning none of those 
headers exist)?

  26: fileinto action
  26:   store message in mailbox `listCC'
  27: stop command; end all script execution
  ## Finished executing script '.active_sieve'

Headers of that message (minute received and signature headers, elided just for 
length)

Reply-To: dovecot@dovecot.org
Return-Path: 
X-Original-To: dovecot@dovecot.org
Delivered-To: dovecot@dovecot.org
Date: Wed, 30 Sep 2020 17:06:54 +0200
From: Kurt Jaeger 
To: dovecot@dovecot.org
Subject: debugging TLS with wireshark and a custom application ?
Message-ID: <20200930150654.gt53...@home.opsec.eu>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-BeenThere: dovecot@dovecot.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Dovecot Mailing List 
List-Unsubscribe: ,
 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: ,
 
Errors-To: dovecot-boun...@dovecot.org
Sender: "dovecot" 

There is one address in the To and no CC header at all, so why was this filed 
into listCC?

(This is the only incidence of listCC in the sieve file for the list user)



-- 
"I used to hate the sun, because it'd shone on everything I'd done.
Made me feel that all that I had done was overfill the ashtray of
my life."

dovecot lda deliver_log_format question

[rudolf]

Hey,

 

i have an question about the deliver_log_format.

 

My log looks sometimes like:  

Oct 1 09:38:01 dd44414 dovecot: lda(user)<20009><9MYzGVmHdV8pTgAA+v7NQw>:
msgid=<20201001073801.628713ac0...@myserver.com>: saved mail to INBOX

 

The deliver_log_format settings are still on default. Are somebody able to
explain me this part of the log message? <20009><9MYzGVmHdV8pTgAA+v7NQw>: 

 

What want dovecot to say with this?

 

Mit freundlichen Grüßen

Yours sincerely

 

Pascal Rudolf

 

Re: dovecot lda deliver_log_format question

[Sami Ketola]

> On 1. Oct 2020, at 11.18, rud...@padaru.de wrote:
> 
> Hey,
>  
> i have an question about the deliver_log_format.
>  
> My log looks sometimes like:  
> Oct 1 09:38:01 dd44414 dovecot: lda(user)<20009><9MYzGVmHdV8pTgAA+v7NQw>: 
> msgid=<20201001073801.628713ac0...@myserver.com 
> >: saved mail to INBOX
>  
> The deliver_log_format settings are still on default. Are somebody able to 
> explain me this part of the log message? <20009><9MYzGVmHdV8pTgAA+v7NQw>: 
> 

deliver_log_format is prefixed with mail_log_prefix. default setting is 
"%s(%u)<%{pid}><%{session}>:"

so service, userid, process id, session id.

deliver_log_format part then starts from msgid.

Sami
 

replication flag default setting?

[Norman King]

Hello.

I'm playing with dovecot replication. I have a working replication 
config on a test server and would like to copy that to production but i 
don't know what's going to happen with existing accounts. Will they 
automatically start replicating without any further input from me? Is 
there a flag on the account somewhere that can tell me what the 
replication status is?


Any thoughts on this would be appreciated.


dovecot version 2.3.7.2
--

regards
Norman King
Compass Foundation sysadmin/tech support

Phone, 856-974-5335 ext 221

supp...@compassfoundation.io 

Website 

Re: BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."

[PGNet Dev]

hi,

On 10/1/20 12:21 AM, JEAN-PAUL CHAPALAIN wrote:
> I had the same problem when migrating from Dovecot V2.2.36 on, Centos-7 to 
> Dovecot v2.3.8 on Centos-8

My report is specifically/solely about the addition/use of the 

Options = ServerPreference

parameter.

I don't see that in your configuration.

Are you using it? In a config using Dovecot's submission proxy?

Re: BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."

[PGNet Dev]

On 10/1/20 8:52 AM, JEAN-PAUL CHAPALAIN wrote:
> In my Centos-8 server, it was not necessary using  "Options = 
> ServerPreference" parameter.

sry, then i'm unclear re: the point you're trying to make.

this issue is ONLY about the problem re: THAT parameter's use, not re: general 
SSL error messages/causes.