Re: make check (pigeonhole)

[Aki Tuomi]

I tried reproducing your problem and I only can make it happen if I run
the test suite as root, which is not supported.

Aki


On 12.09.2018 06:49, Eric Broch wrote:
>
> I'll give those a look and make change accordingly.
>
>
> On 9/11/2018 9:26 PM, Aki Tuomi wrote:
>> You know we have rpm packages for 2.3.2.1 available at
>> https://repo.dovecot.org if you are in a hurry?
>>
>>
>>
>> ---
>> Aki Tuomi
>> Dovecot oy
>>
>>  Original message 
>> From: Eric Broch 
>> Date: 12/09/2018 00:35 (GMT+02:00)
>> To: dovecot@dovecot.org
>> Subject: Re: make check (pigeonhole)
>>
>> Any news on this error on CentOS 7 ?
>>
>> Help!
>>
>>
>> On 9/10/2018 9:32 AM, Eric Broch wrote:
>>>
>>> I attempted as non-root user and got the exact same error.
>>>
>>>
>>> On 9/10/2018 9:10 AM, Aki Tuomi wrote:
 Have you attempted this as non-root user?



 ---
 Aki Tuomi
 Dovecot oy
>>>
>>> -- 
>>> Eric Broch
>>> White Horse Technical Consulting (WHTC)
>>
>> -- 
>> Eric Broch
>> White Horse Technical Consulting (WHTC)
>
> -- 
> Eric Broch
> White Horse Technical Consulting (WHTC)

Re: Letsencrypt certificate for repo.dovecot.org expired May 14th..

[Aki Tuomi]

So it seems. Guess our certbot does not support post hook directories,
since it's not executing the hooks there.

Aki


On 12.09.2018 08:56, B. Reino wrote:
>
> FYI, it happened again :)
>
> On July 15, 2018 10:49:08 AM GMT+02:00, "B. Reino"  wrote:
>> Dear Aki,
>>
>> I think the renewal failed again. The SSL certificate expired Saturday,
>>
>> 14 July 2018.
>>
>> This affects (at least) the repo.dovecot.org website and debian 
>> repository.
>>
>> Thanks,
>> Bernardo.
>>
>> On 2018-05-15 08:15, Aki Tuomi wrote:
>>> On 15.05.2018 09:14, B. Reino wrote:
 Dear all,

 Just in case you've missed it, the certificate for repo.dovecot.org
 just expired yesterday.

 This causes errors in e.g. apt-get update.

 Thanks in advance for fixing it,

 --
 B. Reino
>>> Seems something went wrong during deployment, thanks. It's fixed now.
>>>
>>> Aki

Re: Letsencrypt certificate for repo.dovecot.org expired May 14th..

[B. Reino]

FYI, it happened again :)

On July 15, 2018 10:49:08 AM GMT+02:00, "B. Reino"  wrote:
>Dear Aki,
>
>I think the renewal failed again. The SSL certificate expired Saturday,
>
>14 July 2018.
>
>This affects (at least) the repo.dovecot.org website and debian 
>repository.
>
>Thanks,
>Bernardo.
>
>On 2018-05-15 08:15, Aki Tuomi wrote:
>> On 15.05.2018 09:14, B. Reino wrote:
>>> Dear all,
>>> 
>>> Just in case you've missed it, the certificate for repo.dovecot.org
>>> just expired yesterday.
>>> 
>>> This causes errors in e.g. apt-get update.
>>> 
>>> Thanks in advance for fixing it,
>>> 
>>> --
>>> B. Reino
>> 
>> Seems something went wrong during deployment, thanks. It's fixed now.
>> 
>> Aki

Re: How to send mail to mailbox with disabled domain?

[Steffen Kaiser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 11 Sep 2018, Kai Schaetzl wrote:

Gerald Galster wrote on Tue, 11 Sep 2018 20:49:17 +0200:


Is this a dovecot problem on your side? dovecot usually accepts mail
from MTA like postfix, so it would be better to remove example1.com from
postfix relaydomains (mailbox domains, alias domains, ...). Then there
is no delivery to dovecot. Most MTAs ignore MX records - if a domain is
configured locally, it gets delivered.


Thanks for your reply.
I don't want the MTA to deliver that domain. As an email address.
But I want to deliver to the virtual mailbox of that name.
That's the point. I make a distinction. lmtp doesn't ;-)

I don't want some.addr...@example1.com getting delivered.
But I want some.otheraddr...@example2.com getting delivered.
Which just happens to be aliased to the mailbox "us...@example1.com".
And example1.com is disabled for mail.


"aliased to" seems to be a job for the MTA, hence, it will never deliver 
to Dovecot, if the domain is disabled there.



I used to have mailbox names of "user1" (system accounts), not of
"us...@example1.com" (virtual mailboxes). There doesn't seem to be a way
to have virtual mailbox names like "user1". Not a problem - until you
remove the mailbox domain from the accepted domains. Then it suddenly
doesn't deliver although it's not getting used as an email address.

Delivery is done via postfix/lmtp which actually is dovecot lmtp if I
understand correctly. And lmtp resolves "everything". I can't deliver to a
virtual mailbox named only "user1" it seems (I tried it some months ago
and hit several weird problems, so I stopped that). I have to use a
"user@domain" combination mailbox and the domain has to be in the local-
host-names table or postfix/lmtp won't understand it's local.
But then it will try to file all mail for this domain locally and it will
also accept mail for this domain from outside.


You can configure multiple userdb's in Dovecot. Also, a userdb of LDAP or 
SQL can use %u, %n and %d. Hence, you can configure Dovecot to "find" the 
user by "user1" and "us...@example1.com". However, you must ensure that 
only one entry is found.


However, can you configure Postfix to pass one kind of users without 
domain and the other kind with domain?



So far I came up with two ways to work around this problem:

1. use another domain for example1.com mailbox names (for instance
example1.localmail) and put everything in place that it resolves locally
and is in the local-host-names table. It works, I tested it. But this
requires changing all the already created mailbox names. And change the
code behind the web interface.


This depends on the userdb. You can use the dummy domain as key and return 
specific mail locations.



2. set example1.com to be deliverable again and don't setup any addresses
(aliases) for this domain. As the mailboxes are not directly deliverable
to, only if they are aliased, there is no way to send to this domain from
outside. And I have to put up a few aliases for it that forward mail
externally to some subdomain that isn't locally configured. Or just have
it sent right-away this way.

Both things are not the real deal, though.

Kai





- -- 
Steffen Kaiser

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEVAwUBW5ijTMQnQQNheMxiAQKBOQgAtxitoGR1lHLIEGi7WANWDa/N7QbrRypt
LVel1D6xrbEyDZva8eRiapuf9O0LRpjEdOCPLkxQZPu45a/kzL7/ohcYnYsP7zW+
7Xt0zKArFvQ/NS+7wrYL6gh/mYQwtpF53/R1jnOG6qvR1T6MZtvDfcTl8FTWftG5
WVdafzUka20caxicRHX/zLSYhpOBpycCoUezEm3msXb1RrTywat8qiagFhS2Ui5q
teHwwQQUPDCizhkoLi1rOrgn715oNQKI+5YkTMVgmrCygYCsURRN5M0p6uyOzJAp
GNYFGjbgbWqCtrYXPkac5/y9PCuhPQn/yUHVIraLjzGd/1OL8wyK/Q==
=Z5Mu
-END PGP SIGNATURE-

Re: make check (pigeonhole)

[Eric Broch]

I'll give those a look and make change accordingly.


On 9/11/2018 9:26 PM, Aki Tuomi wrote:
You know we have rpm packages for 2.3.2.1 available at 
https://repo.dovecot.org if you are in a hurry?




---
Aki Tuomi
Dovecot oy

 Original message 
From: Eric Broch 
Date: 12/09/2018 00:35 (GMT+02:00)
To: dovecot@dovecot.org
Subject: Re: make check (pigeonhole)

Any news on this error on CentOS 7 ?

Help!


On 9/10/2018 9:32 AM, Eric Broch wrote:


I attempted as non-root user and got the exact same error.


On 9/10/2018 9:10 AM, Aki Tuomi wrote:

Have you attempted this as non-root user?



---
Aki Tuomi
Dovecot oy


--
Eric Broch
White Horse Technical Consulting (WHTC)


--
Eric Broch
White Horse Technical Consulting (WHTC)


--
Eric Broch
White Horse Technical Consulting (WHTC)

Re: make check (pigeonhole)

[Aki Tuomi]

You know we have rpm packages for 2.3.2.1 available at https://repo.dovecot.org 
if you are in a hurry?


---Aki TuomiDovecot oy
 Original message From: Eric Broch  
Date: 12/09/2018  00:35  (GMT+02:00) To: dovecot@dovecot.org Subject: Re: make 
check (pigeonhole) 

Any news on this error on CentOS 7 ?
Help!




On 9/10/2018 9:32 AM, Eric Broch wrote:



  
  I attempted as non-root user and got the exact same error.

  
  

  On 9/10/2018 9:10 AM, Aki Tuomi
wrote:

  
  
Have you attempted this as non-root user?










  
  ---
  Aki Tuomi
  Dovecot oy

  
  

  -- 
Eric Broch
White Horse Technical Consulting (WHTC)




-- 
Eric Broch
White Horse Technical Consulting (WHTC)

  

Re: How to send mail to mailbox with disabled domain?

[Kai Schaetzl]

Gerald Galster wrote on Tue, 11 Sep 2018 20:49:17 +0200:

> Is this a dovecot problem on your side? dovecot usually accepts mail
> from MTA like postfix, so it would be better to remove example1.com from
> postfix relaydomains (mailbox domains, alias domains, ...). Then there
> is no delivery to dovecot. Most MTAs ignore MX records - if a domain is
> configured locally, it gets delivered.

Thanks for your reply.
I don't want the MTA to deliver that domain. As an email address. 
But I want to deliver to the virtual mailbox of that name.
That's the point. I make a distinction. lmtp doesn't ;-)

I don't want some.addr...@example1.com getting delivered.
But I want some.otheraddr...@example2.com getting delivered. 
Which just happens to be aliased to the mailbox "us...@example1.com". 
And example1.com is disabled for mail.

I used to have mailbox names of "user1" (system accounts), not of 
"us...@example1.com" (virtual mailboxes). There doesn't seem to be a way 
to have virtual mailbox names like "user1". Not a problem - until you 
remove the mailbox domain from the accepted domains. Then it suddenly 
doesn't deliver although it's not getting used as an email address.

Delivery is done via postfix/lmtp which actually is dovecot lmtp if I 
understand correctly. And lmtp resolves "everything". I can't deliver to a 
virtual mailbox named only "user1" it seems (I tried it some months ago 
and hit several weird problems, so I stopped that). I have to use a 
"user@domain" combination mailbox and the domain has to be in the local-
host-names table or postfix/lmtp won't understand it's local.
But then it will try to file all mail for this domain locally and it will 
also accept mail for this domain from outside.

So far I came up with two ways to work around this problem:

1. use another domain for example1.com mailbox names (for instance 
example1.localmail) and put everything in place that it resolves locally 
and is in the local-host-names table. It works, I tested it. But this 
requires changing all the already created mailbox names. And change the 
code behind the web interface.

2. set example1.com to be deliverable again and don't setup any addresses 
(aliases) for this domain. As the mailboxes are not directly deliverable 
to, only if they are aliased, there is no way to send to this domain from 
outside. And I have to put up a few aliases for it that forward mail 
externally to some subdomain that isn't locally configured. Or just have 
it sent right-away this way.

Both things are not the real deal, though.

Kai

Re: make check (pigeonhole)

[Eric Broch]

Any news on this error on CentOS 7 ?

Help!


On 9/10/2018 9:32 AM, Eric Broch wrote:


I attempted as non-root user and got the exact same error.


On 9/10/2018 9:10 AM, Aki Tuomi wrote:

Have you attempted this as non-root user?



---
Aki Tuomi
Dovecot oy


--
Eric Broch
White Horse Technical Consulting (WHTC)


--
Eric Broch
White Horse Technical Consulting (WHTC)

Log sync error

[Jakobus Schürz]

Hi there!

I get a lot of errormessages. My dovecot is: dovecot-core
2:2.3.2.1-1~stretch from Debian stable.

I found this: https://www.dovecot.org/list/dovecot/2013-July/091648.html

So the bug came back...


The Log is attached


Thanks

Jakob



Sep 11 19:18:37 mymail dovecot[29916]: 
indexer-worker(USERNAME)<30071><9VwUMO34l1t6dQAA4mbmCw:8E/PMe34l1t3dQAA4mbmCw>: 
Indexed 1 messages in INBOX/ÖBB/Fahrplan (UIDs 4..4)
Sep 11 19:18:37 mymail dovecot[29916]: Error: 
imap(USERNAME)<30015><0AmKopt1drMKAGQE>: Log synchronization error at 
seq=3,offset=4456 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 8, but next_uid = 9
Sep 11 19:18:37 mymail dovecot[29916]: imap(USERNAME)<30015><0AmKopt1drMKAGQE>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:37 mymail dovecot[29916]: imap(USERNAME)<30015><0AmKopt1drMKAGQE>: 
save: box=INBOX/Sent, uid=8, 
msgid=<1866258468.1038.1536684898270.javamail.fp...@sbepsh01p.ts-prod.oebb.at>, 
size=8253
Sep 11 19:18:37 mymail dovecot[29916]: 
indexer-worker(USERNAME)<30071><0AmKopt1drMKAGQE:OBygM+34l1t3dQAA4mbmCw>: 
Indexed 1 messages in INBOX/Sent (UIDs 8..8)
Sep 11 19:18:38 mymail dovecot[29916]: Error: 
imap(USERNAME)<30024>: Log synchronization error at 
seq=3,offset=4904 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 9, but next_uid = 10
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30024>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30024>: 
save: box=INBOX/Sent, uid=9, 
msgid=<1446477173.1001.1536684091542.javamail.fp...@sbepsh01p.ts-prod.oebb.at>, 
size=8254
Sep 11 19:18:38 mymail dovecot[29916]: 
indexer-worker(USERNAME)<30071>: 
Indexed 1 messages in INBOX/Sent (UIDs 9..9)
Sep 11 19:18:38 mymail dovecot[29916]: Error: 
imap(USERNAME)<30021>: Log synchronization error at 
seq=3,offset=4904 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 9, but next_uid = 10
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30021>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:38 mymail dovecot[29916]: Error: 
imap(USERNAME)<30018>: Log synchronization error at 
seq=3,offset=4904 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 9, but next_uid = 10
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30018>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:38 mymail dovecot[29916]: Error: 
imap(USERNAME)<30015><0AmKopt1drMKAGQE>: Log synchronization error at 
seq=3,offset=4904 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 9, but next_uid = 10
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30015><0AmKopt1drMKAGQE>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:38 mymail dovecot[29916]: Error: 
imap(USERNAME)<30015><0AmKopt1drMKAGQE>: Log synchronization error at 
seq=3,offset=5384 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 10, but next_uid = 11
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30015><0AmKopt1drMKAGQE>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30015><0AmKopt1drMKAGQE>: 
save: box=INBOX/Sent, uid=10, 
msgid=<1143759519.874.1536681766219.javamail.fp...@sbepsh01p.ts-prod.oebb.at>, 
size=8253
Sep 11 19:18:38 mymail dovecot[29916]: 
indexer-worker(USERNAME)<30071><0AmKopt1drMKAGQE:oDP4Ke74l1t3dQAA4mbmCw>: 
Indexed 1 messages in INBOX/Sent (UIDs 10..10)
Sep 11 19:18:39 mymail dovecot[29916]: Error: 
imap(USERNAME)<30024>: Log synchronization error at 
seq=3,offset=5384 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 10, but next_uid = 11
Sep 11 19:18:39 mymail dovecot[29916]: imap(USERNAME)<30024>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:39 mymail dovecot[29916]: Error: 
imap(USERNAME)<30024>: Log synchronization error at 
seq=3,offset=5816 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 11, but next_uid = 12
Sep 11 19:18:39 mymail dovecot[29916]: imap(USERNAME)<30024>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:39 mymail dovecot[29916]: imap(USERNAME)<30024>: 
save: box=INBOX/Sent, uid=11, 
msgid=<1170231472.947.1536683100471.javamail.fp...@sbepsh01p.ts-prod.oebb.at>, 
size=8256
Sep 11 19:18:39 mymail dovecot[29916]: 
indexer-worker(USERNAME)<30071>: 
Indexed 1 messages in INBOX/Sent (UIDs 11..11)
Sep 11 19:18:39 mymail dovecot[29916]: Error: 
imap(USERNAME)<30021>: Log sy

Re: How to send mail to mailbox with disabled domain?

[Gerald Galster]

Is this a dovecot problem on your side? dovecot usually accepts mail
from MTA like postfix, so it would be better to remove example1.com from
postfix relaydomains (mailbox domains, alias domains, ...). Then there
is no delivery to dovecot. Most MTAs ignore MX records - if a domain is
configured locally, it gets delivered.

Best regards
Gerald

> Am 11.09.2018 um 20:20 schrieb Kai Schaetzl :
> 
> Given the following:
> 
> mailboxes:
> us...@example1.com
> us...@example1.com
> us...@example1.com
> etc.
> 
> aliases:
> whate...@example1.com -> us...@example1.com
> whate...@example2.com -> us...@example1.com
> whate...@example3.com -> us...@example1.com
> 
> Now the problem:
> example1.com MX goes elsewhere (doesn't point to this server anymore).
> Domains example2.com and example3.com still point to that server and 
> should be able to accept mail.
> I have to disable mail acceptance for example1.com. 
> If not, mail sent *from* that server (e.g. from a web form) to that domain 
> will not leave the server. 
> However, if I disable example1.com for mail dovecot lmtp will not deliver 
> mail to this mail box anymore, although the mailbox still exists.
> 
> How can I solve this? Is there a way of solving this, but keeping the 
> domain example1.com in the name for these mailboxes?
> Or is there a way to tell dovecot to ignore domains for mailbox names? 
> e.g. deliver to "user1"? (All user localparts are unique.)
> 
> Thanks for any hints.
> 
> Kai
> 
> 

Log sync error

[Jakobus Schürz]

Hi there!

I get a lot of errormessages. My dovecot is: dovecot-core
2:2.3.2.1-1~stretch from Debian stable.

I found this: https://www.dovecot.org/list/dovecot/2013-July/091648.html

So the bug came back...


The Log is attached


Thanks

Jakob


Sep 11 19:18:37 mymail dovecot[29916]: 
indexer-worker(USERNAME)<30071><9VwUMO34l1t6dQAA4mbmCw:8E/PMe34l1t3dQAA4mbmCw>: 
Indexed 1 messages in INBOX/ÖBB/Fahrplan (UIDs 4..4)
Sep 11 19:18:37 mymail dovecot[29916]: Error: 
imap(USERNAME)<30015><0AmKopt1drMKAGQE>: Log synchronization error at 
seq=3,offset=4456 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 8, but next_uid = 9
Sep 11 19:18:37 mymail dovecot[29916]: imap(USERNAME)<30015><0AmKopt1drMKAGQE>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:37 mymail dovecot[29916]: imap(USERNAME)<30015><0AmKopt1drMKAGQE>: 
save: box=INBOX/Sent, uid=8, 
msgid=<1866258468.1038.1536684898270.javamail.fp...@sbepsh01p.ts-prod.oebb.at>, 
size=8253
Sep 11 19:18:37 mymail dovecot[29916]: 
indexer-worker(USERNAME)<30071><0AmKopt1drMKAGQE:OBygM+34l1t3dQAA4mbmCw>: 
Indexed 1 messages in INBOX/Sent (UIDs 8..8)
Sep 11 19:18:38 mymail dovecot[29916]: Error: 
imap(USERNAME)<30024>: Log synchronization error at 
seq=3,offset=4904 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 9, but next_uid = 10
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30024>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30024>: 
save: box=INBOX/Sent, uid=9, 
msgid=<1446477173.1001.1536684091542.javamail.fp...@sbepsh01p.ts-prod.oebb.at>, 
size=8254
Sep 11 19:18:38 mymail dovecot[29916]: 
indexer-worker(USERNAME)<30071>: 
Indexed 1 messages in INBOX/Sent (UIDs 9..9)
Sep 11 19:18:38 mymail dovecot[29916]: Error: 
imap(USERNAME)<30021>: Log synchronization error at 
seq=3,offset=4904 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 9, but next_uid = 10
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30021>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:38 mymail dovecot[29916]: Error: 
imap(USERNAME)<30018>: Log synchronization error at 
seq=3,offset=4904 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 9, but next_uid = 10
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30018>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:38 mymail dovecot[29916]: Error: 
imap(USERNAME)<30015><0AmKopt1drMKAGQE>: Log synchronization error at 
seq=3,offset=4904 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 9, but next_uid = 10
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30015><0AmKopt1drMKAGQE>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:38 mymail dovecot[29916]: Error: 
imap(USERNAME)<30015><0AmKopt1drMKAGQE>: Log synchronization error at 
seq=3,offset=5384 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 10, but next_uid = 11
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30015><0AmKopt1drMKAGQE>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:38 mymail dovecot[29916]: imap(USERNAME)<30015><0AmKopt1drMKAGQE>: 
save: box=INBOX/Sent, uid=10, 
msgid=<1143759519.874.1536681766219.javamail.fp...@sbepsh01p.ts-prod.oebb.at>, 
size=8253
Sep 11 19:18:38 mymail dovecot[29916]: 
indexer-worker(USERNAME)<30071><0AmKopt1drMKAGQE:oDP4Ke74l1t3dQAA4mbmCw>: 
Indexed 1 messages in INBOX/Sent (UIDs 10..10)
Sep 11 19:18:39 mymail dovecot[29916]: Error: 
imap(USERNAME)<30024>: Log synchronization error at 
seq=3,offset=5384 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 10, but next_uid = 11
Sep 11 19:18:39 mymail dovecot[29916]: imap(USERNAME)<30024>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:39 mymail dovecot[29916]: Error: 
imap(USERNAME)<30024>: Log synchronization error at 
seq=3,offset=5816 for 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index: Append with 
UID 11, but next_uid = 12
Sep 11 19:18:39 mymail dovecot[29916]: imap(USERNAME)<30024>: 
Warning: fscking index file 
/var/lib/dovecot/db/indexes/Maildir/USERNAME/Sent/dovecot.index
Sep 11 19:18:39 mymail dovecot[29916]: imap(USERNAME)<30024>: 
save: box=INBOX/Sent, uid=11, 
msgid=<1170231472.947.1536683100471.javamail.fp...@sbepsh01p.ts-prod.oebb.at>, 
size=8256
Sep 11 19:18:39 mymail dovecot[29916]: 
indexer-worker(USERNAME)<30071>: 
Indexed 1 messages in INBOX/Sent (UIDs 11..11)
Sep 11 19:18:39 mymail dovecot[29916]: Error: 
imap(USERNAME)<30021>: Log syn

How to send mail to mailbox with disabled domain?

[Kai Schaetzl]

Given the following:

mailboxes:
us...@example1.com
us...@example1.com
us...@example1.com
etc.

aliases:
whate...@example1.com -> us...@example1.com
whate...@example2.com -> us...@example1.com
whate...@example3.com -> us...@example1.com

Now the problem:
example1.com MX goes elsewhere (doesn't point to this server anymore).
Domains example2.com and example3.com still point to that server and 
should be able to accept mail.
I have to disable mail acceptance for example1.com. 
If not, mail sent *from* that server (e.g. from a web form) to that domain 
will not leave the server. 
However, if I disable example1.com for mail dovecot lmtp will not deliver 
mail to this mail box anymore, although the mailbox still exists.

How can I solve this? Is there a way of solving this, but keeping the 
domain example1.com in the name for these mailboxes?
Or is there a way to tell dovecot to ignore domains for mailbox names? 
e.g. deliver to "user1"? (All user localparts are unique.)

Thanks for any hints.

Kai

Re: Auth process sometimes stop responding after upgrade

[Timo Sirainen]

On 11 Sep 2018, at 10.57, Simone Lazzaris  wrote:
> 
> Sep 11 03:25:55 imap-front4 dovecot: director: Panic: file 
> doveadm-connection.c: line 1097 (doveadm_connection_deinit): assertion 
> failed: (conn->to_ring_sync_abort == NULL)
> Sep 11 03:25:55 imap-front4 dovecot: director: Fatal: master: 
> service(director): child 4395 killed with signal 6 (core dumps disabled)

It's crashing. Can you get gdb backtrace? First enable core dumps. 
https://dovecot.org/bugreport.html#coredumps 

Re: Auth process sometimes stop responding after upgrade

[Simone Lazzaris]

In data lunedì 10 settembre 2018 09:58:50 CEST, Timo Sirainen ha scritto:
> On 8 Sep 2018, at 15.18, Simone Lazzaris  wrote:
> > Timo, unfortunately the patch doesn't compile;  I've moved the declaration
> > of "conn" one line up to make it work.
> 
> Oops, I guess I was too much in a hurry to even compile it. Here's a new
> patch that compiles and passes our director CI tests.

Hi Timo;
after 24 hours of field testing, I can say that the issue is mostly gone. I say 
"mostly" 
because the service is working as far as the user is concerned, but I see some 
strange 
going on in the logs.

Grepping "director" in the log file, I can see that there are some panic and 
some 
comunication errors:

Sep 11 03:24:55 imap-front4 dovecot: director: doveadm: Host 192.168.1.143 
vhost count 
changed from 100 to 0
Sep 11 03:24:55 imap-front4 dovecot: director: doveadm: Host 192.168.1.219 
vhost count 
changed from 100 to 0
Sep 11 03:24:55 imap-front4 dovecot: director: doveadm: Host 192.168.1.218 
vhost count 
changed from 100 to 0
Sep 11 03:24:55 imap-front4 dovecot: director: doveadm: Host 192.168.1.216 
vhost count 
changed from 100 to 0
Sep 11 03:24:55 imap-front4 dovecot: director: 
director(212.183.164.161:9090/right): Host 
192.168.1.145 vhost count changed from 100 to 0
Sep 11 03:24:55 imap-front4 dovecot: director: doveadm: Host 192.168.1.217 
vhost count 
changed from 100 to 0
Sep 11 03:24:55 imap-front4 dovecot: director: doveadm: Host 192.168.1.144 
vhost count 
changed from 100 to 0
Sep 11 03:24:55 imap-front4 dovecot: director: doveadm: Host 192.168.1.145 
vhost count 
changed from 0 to 0
Sep 11 03:24:55 imap-front4 dovecot: director: doveadm: Host 192.168.1.142 
vhost count 
changed from 100 to 0
Sep 11 03:25:09 imap-front4 dovecot: director: 
director(212.183.164.161:9090/right): Host 
192.168.1.143 vhost count changed from 0 to 100
Sep 11 03:25:09 imap-front4 dovecot: director: Error: Director 
212.183.164.161:9090/right 
disconnected: Connection closed (bytes in=1116368, bytes out=1182555, 0+27319 
USERs 
received, last input 0.000 s ago, last output 0.000 s ago, connected 4602.589 s 
ago, 481 
peak output buffer size, 1.948 CPU secs since connected)
Sep 11 03:25:09 imap-front4 dovecot: director: Connecting to 
212.183.164.161:9090 (as 
212.183.164.164): Reconnecting after disconnection
Sep 11 03:25:09 imap-front4 dovecot: director: Error: Director 
212.183.164.161:9090/out 
disconnected: Connection closed: read(size=968) failed: Connection reset by 
peer (bytes 
in=56, bytes out=59143, 0+0 USERs received, 1556 USERs sent in handshake, last 
input 
0.002 s ago, last output 0.002 s ago, connected 0.024 s ago, 8190 peak output 
buffer size, 
0.004 CPU secs since connected, handshake DONE not received)
Sep 11 03:25:09 imap-front4 dovecot: director: Connecting to 
212.183.164.162:9090 (as 
212.183.164.164): Reconnecting after disconnection
Sep 11 03:25:09 imap-front4 dovecot: director: 
director(212.183.164.162:9090/out): 
Handshake finished in 0.006 secs (bytes in=61, bytes out=59173, 0+0 USERs 
received, 1556 
USERs sent in handshake, last input 0.000 s ago, last output 0.003 s ago, 
connected 0.006 s 
ago, 8190 peak output buffer size, 0.000 CPU secs since connected)
Sep 11 03:25:10 imap-front4 dovecot: director: Connecting to 
212.183.164.161:9090 (as 
212.183.164.164): Received CONNECT request from 212.183.164.162:9090/right - 
replacing 
current right 212.183.164.162:9090/right
Sep 11 03:25:10 imap-front4 dovecot: director: 
director(212.183.164.161:9090/out): 
Handshake finished in 0.004 secs (bytes in=61, bytes out=59332, 0+0 USERs 
received, 1561 
USERs sent in handshake, last input 0.000 s ago, last output 0.004 s ago, 
connected 0.004 s 
ago, 8190 peak output buffer size, 0.000 CPU secs since connected)
Sep 11 03:25:10 imap-front4 dovecot: director: 
director(212.183.164.161:9090/right): Host 
192.168.1.216 vhost count changed from 0 to 100
Sep 11 03:25:10 imap-front4 dovecot: director: Error: Director 
212.183.164.161:9090/right 
disconnected: Connection closed: read(size=558) failed: Connection reset by 
peer (bytes 
in=466, bytes out=60271, 0+6 USERs received, 1561 USERs sent in handshake, last 
input 
0.001 s ago, last output 0.000 s ago, connected 0.553 s ago, 8190 peak output 
buffer size, 
0.000 CPU secs since connected)
Sep 11 03:25:10 imap-front4 dovecot: director: Connecting to 
212.183.164.162:9090 (as 
212.183.164.164): Reconnecting after disconnection
Sep 11 03:25:10 imap-front4 dovecot: director: 
director(212.183.164.162:9090/out): 
Handshake finished in 0.005 secs (bytes in=61, bytes out=59372, 0+0 USERs 
received, 1562 
USERs sent in handshake, last input 0.000 s ago, last output 0.005 s ago, 
connected 0.005 s 
ago, 8192 peak output buffer size, 0.000 CPU secs since connected)
Sep 11 03:25:10 imap-front4 dovecot: director: Connecting to 
212.183.164.161:9090 (as 
212.183.164.164): Received CONNECT request from 212.183.164.162:9090/right - 
replacing 
current right 212.183.164.16