date:20180205

Re: Cannot delete IMAP Mail-Folder in Trash

2018-02-05 Thread Rupert Gallagher

We have the same problem, with a twist. When Thunderbird deletes a folder, it 
is still shown by the GUI. Dovecot deleted the folder correctly, and the 
sunscriptions file is also correct. Some other times, on shared folders, 
Thunderbird refuses to delete; in this case, apple mail on iphone can delete 
successfully. This suggests that the problem is in Thunderbird's code.

R

On Mon, Feb 5, 2018 at 21:55, Remko Lodder  wrote:

>> On 5 Feb 2018, at 17:32, Aki Tuomi  wrote:
>>
>>> On February 5, 2018 at 6:16 PM Gabriel Kaufmann  
>>> wrote:
>>>
>>> Doesn't anyone have an idea?
>>>
>>> It looks like Dovecot and/or Thunderbird simply "ignore" sub-folders of
>>> IMAP-Folder in Trash/ as they are also not shown in Trash-Folder.
>>> Sub-Folder for INBOX and other IMAP-Folders work perfect (using
>>> layout=fs Mailbox).
>>>
>>> Why doesn't this work for Trash?
>>>
>>> Best regards
>>>
>>> Gabriel Kaufmann
>>
>> Can you try running this as root and provide output?
>>
>> doveadm -Dv -o mail_debug=yes mailbox delete -u username Trash/Somefolder
>>
>> Aki
>
> I had the same with Mac Mail.app. I decided to rm -rf the sdbox file on the 
> master and replica and I won.
> It was persistant though and I think it had to do with the following:
>
> I let my mail deliver in yearboxes, which have many many subfolders, some are 
> just "placeholders". They appear different in the view.
> Regular mailboxes are "dark" in colors, placeholder boxes are "white" in 
> colors (see attachment), where winkels is the "placeholder" folder and 
> "action" is the regular mailbox in which mail gets delivered.
>
> I could not get rid of those "winkels" kind of folders". Only by force 
> removing them from the filesystem hierarchie.
>
> Hope this helps a bit :)
>
> Cheers
> Remko

Dovecot and /dev/rand

2018-02-05 Thread Michael A. Peters

There's a (2014 I think) patch in dovecot rpm for Red Hat / Fedora 
ecosystem that was last update with 2.2.9 (patch last updated for that 
release)


I want to know if the problem it solves still exists in 2.3.x branch.

The patch is called "dovecot-2.2.9-nodevrand.patch" and is attached.

It allegedly addresses an issue with installation in chroot that does 
not have /dev/random


Red Hat bugzilla 1026790

I am apparently not authorized to see that bug so I don't know much 
about it, but with many code changes in 2.3.0 from 2.2.x I am wondering 
if the alleged issue was solved a different way or if the patch should 
be ported to 2.3.0 when packaged for people who might trigger it.


Thanks.




diff -up dovecot-2.2.9/src/lib-master/master-service.c.fixit dovecot-2.2.9/src/lib-master/master-service.c
--- dovecot-2.2.9/src/lib-master/master-service.c.fixit	2013-11-24 14:37:39.0 +0100
+++ dovecot-2.2.9/src/lib-master/master-service.c	2013-11-27 17:52:48.802843395 +0100
@@ -559,6 +559,11 @@ const char *master_service_get_name(stru
 	return service->name;
 }
 
+const enum master_service_flags master_service_get_flags(struct master_service *service)
+{
+	return service->flags;
+}
+
 void master_service_run(struct master_service *service,
 			master_service_connection_callback_t *callback)
 {
diff -up dovecot-2.2.9/src/lib-master/master-service.h.fixit dovecot-2.2.9/src/lib-master/master-service.h
--- dovecot-2.2.9/src/lib-master/master-service.h.fixit	2013-11-24 14:37:39.0 +0100
+++ dovecot-2.2.9/src/lib-master/master-service.h	2013-11-27 17:53:05.329705614 +0100
@@ -134,6 +134,8 @@ const char *master_service_get_version_s
 /* Returns name of the service, as given in name parameter to _init(). */
 const char *master_service_get_name(struct master_service *service);
 
+const enum master_service_flags master_service_get_flags(struct master_service *service);
+
 /* Start the service. Blocks until finished */
 void master_service_run(struct master_service *service,
 			master_service_connection_callback_t *callback)
diff -up dovecot-2.2.9/src/ssl-params/main.c.fixit dovecot-2.2.9/src/ssl-params/main.c
--- dovecot-2.2.9/src/ssl-params/main.c.fixit	2013-11-24 14:37:39.0 +0100
+++ dovecot-2.2.9/src/ssl-params/main.c	2013-11-27 17:51:06.664694558 +0100
@@ -103,7 +103,10 @@ static void sig_chld(const siginfo_t *si
 	if (waitpid(-1, , WNOHANG) < 0)
 		i_error("waitpid() failed: %m");
 	else if (status != 0)
+	{
 		i_error("child process failed with status %d", status);
+		if(master_service_get_flags(master_service) & MASTER_SERVICE_FLAG_STANDALONE) exit(1);
+	}
 	else {
 		/* params should have been created now. try refreshing. */
 		ssl_params_refresh(param);

Re: Does Dovecot LDAP auth support LDAP referral

2018-02-05 Thread Xuan Jia


Hello Sami,

Thanks.


*From:* Sami Ketola
*Sent:* Friday, Feb 2, 2018 9:17 GMT
*To:* Xuan Jia
*Cc:* dovecot@dovecot.org
*Subject:* Does Dovecot LDAP auth support LDAP referral


On 2 Feb 2018, at 10.38, Xuan Jia  wrote:

We using Dovecot with LDAP.
 From the beginning, we using GC LDAP query with port 3268 for email accounts.
For example, us...@our-organization.org (in the USA) with "base = 
dc=our-organization, dc=org" works fine.

But refer to this document:
https://wiki2.dovecot.org/AuthDatabase/LDAP
When we change the LDAP from 3268 to 389 and with TLS, the base should be 
changed like this:
"base = ou=usa, dc=our-organization, dc=org"

But if the user (user2) located in United Kingdom (ou=gbr), the user can not 
login.

When we debug with ldapsearch:
ldapsearch -ZZ -v -h dc.our-organization.org -p 389 -D 
'cn=auth_user,ou=usa,dc=our-organization,dc=org' -W -b 'dc=our-organization, 
dc=org' '(userPrincipalName=us...@our-organization.org)'
It can return user2 information with some "numReferences".

But in Dovecot, if "base = dc=our-organization, dc=org" it only reported auth 
error with timeout.

So my question is: does Dovecot LDAP auth support LDAP referral?
If Dovecot relies on OpenLDAP, it should be support.
If not, why and what is the walkthrough?

TBH, I don't think that it's supported. Looking at the source code at least it 
does not look it is.

What you could do is to have separate passdb for both ldap bases.
one that would query base = ou=usa, dc=our-organization, dc=org and one that 
would query
base = ou=gbr, dc=our-organization, dc=org

and then use skip=authenticated on the second passdb if user already found in 
first passdb.

Sami

Re: Cannot delete IMAP Mail-Folder in Trash

2018-02-05 Thread Remko Lodder

> On 5 Feb 2018, at 17:32, Aki Tuomi  > wrote:
> 
> 
>> On February 5, 2018 at 6:16 PM Gabriel Kaufmann > > wrote:
>> 
>> 
>> Doesn't anyone have an idea?
>> 
>> It looks like Dovecot and/or Thunderbird simply "ignore" sub-folders of
>> IMAP-Folder in Trash/ as they are also not shown in Trash-Folder.
>> Sub-Folder for INBOX and other IMAP-Folders work perfect (using
>> layout=fs Mailbox).
>> 
>> Why doesn't this work for Trash?
>> 
>> Best regards
>> 
>> Gabriel Kaufmann
>> 
> 
> Can you try running this as root and provide output?
> 
> doveadm -Dv -o mail_debug=yes mailbox delete -u username Trash/Somefolder
> 
> Aki

I had the same with Mac Mail.app. I decided to rm -rf the sdbox file on the 
master and replica and I won.
It was persistant though and I think it had to do with the following:

I let my mail deliver in yearboxes, which have many many subfolders, some are 
just “placeholders”. They appear different in the view.
Regular mailboxes are “dark” in colors, placeholder boxes are “white” in colors 
(see attachment), where winkels is the “placeholder” folder and “action” is the 
regular mailbox in which mail gets delivered.

I could not get rid of those “winkels” kind of folders”. Only by force removing 
them from the filesystem hierarchie.

Hope this helps a bit :)

Cheers
Remko

signature.asc
Description: Message signed with OpenPGP

Re: Cannot delete IMAP Mail-Folder in Trash

2018-02-05 Thread Aki Tuomi


> On February 5, 2018 at 6:16 PM Gabriel Kaufmann  wrote:
> 
> 
> Doesn't anyone have an idea?
> 
> It looks like Dovecot and/or Thunderbird simply "ignore" sub-folders of 
> IMAP-Folder in Trash/ as they are also not shown in Trash-Folder. 
> Sub-Folder for INBOX and other IMAP-Folders work perfect (using 
> layout=fs Mailbox).
> 
> Why doesn't this work for Trash?
> 
> Best regards
> 
> Gabriel Kaufmann
>

Can you try running this as root and provide output?

doveadm -Dv -o mail_debug=yes mailbox delete -u username Trash/Somefolder

Aki

Re: Cannot delete IMAP Mail-Folder in Trash

2018-02-05 Thread Gabriel Kaufmann


Doesn't anyone have an idea?

It looks like Dovecot and/or Thunderbird simply "ignore" sub-folders of 
IMAP-Folder in Trash/ as they are also not shown in Trash-Folder. 
Sub-Folder for INBOX and other IMAP-Folders work perfect (using 
layout=fs Mailbox).


Why doesn't this work for Trash?

Best regards

Gabriel Kaufmann

Re: Bug in dovecot 2.3 virtual plugin

2018-02-05 Thread Aki Tuomi

Yeah, sorry I forgot to report back, it's now fixed in
https://github.com/dovecot/core/commit/5c1837529e6957da3e389683c43bd006859395e5.patch

Aki


On 05.02.2018 14:04, Marco Giunta wrote:
> Hi,
> did you have time to investigate about 'Panic: file unichar.c' bug ?
> Because I have the same problem with a 2.3.0 installation without
> virtual plugin.
>
> Thanks,
>   Marco
>
>
> On 2018-01-03 16:52, Aki Tuomi wrote:
>> This is not a bug in virtual plugin, but in some email which contains
>> invalid unicode sequence somehow. Can you send me a core file? This
>> should not have occured ofc but would be nice to know how it ended up
>> here.
>>
>> Aki
>>
>>> On January 3, 2018 at 5:35 PM Jakobus Schürz
>>>  wrote:
>>>
>>>
>>> Hi there!
>>>
>>> I compiled dovecot 2.3 from git. Because there is already a bug in
>>> virtual-plugin, and i hoped, it get fixed... but it doesn't. So this
>>> is the error-message from the log
>>>
>>> Jän 03 16:27:08 aldebaran dovecot[26460]:
>>> indexer-worker(jakob)<26476>:
>>> Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion
>>> failed: (uni_is_valid_ucs4(chr))
>>> Jän 03 16:27:08 aldebaran dovecot[26460]:
>>> indexer-worker(jakob)<26476>:
>>> Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0xc6021)
>>> [0x7f8299f7a021] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xc60ed)
>>> [0x7f8299f7a0ed] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0)
>>> [0x7f8299eec481] ->
>>> /usr/local/lib/dovecot/libdovecot.so.0(uni_ucs4_to_utf8_c+0xa0)
>>> [0x7f8299fb1500] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xa75e0)
>>> [0x7f8299f5b5e0] ->
>>> /usr/local/lib/dovecot/libdovecot.so.0(mail_html2text_more+0xc5)
>>> [0x7f8299f5b775] ->
>>> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0xcfcc) [0x7f82990aefcc]
>>> -> /usr/local/lib/dovecot/lib20_fts_plugin.so(fts_parser_more+0x27)
>>> [0x7f82990aeca7] ->
>>> /usr/local/lib/dovecot/lib20_fts_plugin.so(fts_build_mail+0x5e9)
>>> [0x7f82990acc39] ->
>>> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x1122d) [0x7f82990b322d]
>>> -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0x916a)
>>> [0x7f82958e316a] ->
>>> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x10f5d) [0x7f82990b2f5d]
>>> -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0x916a)
>>> [0x7f82958e316a] ->
>>> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x10f5d) [0x7f82990b2f5d]
>>> -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x2e)
>>> [0x7f829a2641be] -> dovecot/indexer-worker [jakob
>>> Synoptic/AKTUELL](+0x2533) [0x562227882533] ->
>>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69)
>>> [0x7f8299f91bf9] ->
>>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x109)
>>>
>>> [0x7f8299f93499] ->
>>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52)
>>> [0x7f8299f91d02] ->
>>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38)
>>> [0x7f8299f91f18] ->
>>> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13)
>>> [0x7f8299f0f1e3] -> dovecot/indexer-worker [jakob
>>> Synoptic/AKTUELL](main+0xe7) [0x562227881f47] ->
>>> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)
>>> [0x7f8299b352b1] -> dovecot/indexer-worker [jakob
>>> Synoptic/AKTUELL](_start+0x2a) [0x56222788201a]
>>> Jän 03 16:27:08 aldebaran dovecot[26460]: indexer: Error: Indexer
>>> worker disconnected, discarding 1 requests for jakob
>>> Jän 03 16:27:08 aldebaran dovecot[26460]:
>>> imap(jakob)<26472>: Error: indexer failed to index
>>> mailbox Synoptic/AKTUELL
>>> Jän 03 16:27:08 aldebaran dovecot[26460]:
>>> indexer-worker(jakob)<26476>:
>>> Fatal: master: service(indexer-worker): child 26476 killed with signal
>>> 6 (core dumps disabled)
>>> Jän 03 16:27:09 aldebaran dovecot[26460]:
>>> indexer-worker(jakob)<26484>:
>>> Error: lucene index
>>> /var/lib/dovecot/db/indexes/Maildir/jakob/lucene-indexes:
>>> IndexWriter() failed (#1): Lock obtain timed out
>>> Jän 03 16:27:10 aldebaran dovecot[26460]:
>>> indexer-worker(jakob)<26484>:
>>> Error: Mailbox Synoptic/AKTUELL: Transaction commit failed: BUG:
>>> Unknown internal error (attempted to index 1488 messages (UIDs
>>> 15214..16775))
>>> Jän 03 16:27:10 aldebaran dovecot[26460]:
>>> imap(jakob)<26480>: Error: indexer failed to index
>>> mailbox Synoptic/AKTUELL
>>> Jän 03 16:27:11 aldebaran dovecot[26460]:
>>> imap(jakob)<26472>: Panic: file mail-index.c: line
>>> 793 (mail_index_close): assertion failed: (index->open_count > 0)
>>> Jän 03 16:27:11 aldebaran dovecot[26460]:
>>> imap(jakob)<26472>: Error: Raw backtrace:
>>> /usr/local/lib/dovecot/libdovecot.so.0(+0xc6021) [0x7fb0fbd3a021] ->
>>> /usr/local/lib/dovecot/libdovecot.so.0(+0xc60ed) [0x7fb0fbd3a0ed] ->
>>>

Re: Re: Bug in dovecot 2.3 virtual plugin

2018-02-05 Thread Marco Giunta


Hi,
did you have time to investigate about 'Panic: file unichar.c' bug ? 
Because I have the same problem with a 2.3.0 installation without 
virtual plugin.


Thanks,
  Marco


On 2018-01-03 16:52, Aki Tuomi wrote:

This is not a bug in virtual plugin, but in some email which contains invalid 
unicode sequence somehow. Can you send me a core file? This should not have 
occured ofc but would be nice to know how it ended up here.

Aki


On January 3, 2018 at 5:35 PM Jakobus Schürz  wrote:


Hi there!

I compiled dovecot 2.3 from git. Because there is already a bug in
virtual-plugin, and i hoped, it get fixed... but it doesn't. So this
is the error-message from the log

Jän 03 16:27:08 aldebaran dovecot[26460]:
indexer-worker(jakob)<26476>:
Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion
failed: (uni_is_valid_ucs4(chr))
Jän 03 16:27:08 aldebaran dovecot[26460]:
indexer-worker(jakob)<26476>:
Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0xc6021)
[0x7f8299f7a021] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xc60ed)
[0x7f8299f7a0ed] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7f8299eec481] ->
/usr/local/lib/dovecot/libdovecot.so.0(uni_ucs4_to_utf8_c+0xa0)
[0x7f8299fb1500] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xa75e0)
[0x7f8299f5b5e0] ->
/usr/local/lib/dovecot/libdovecot.so.0(mail_html2text_more+0xc5)
[0x7f8299f5b775] ->
/usr/local/lib/dovecot/lib20_fts_plugin.so(+0xcfcc) [0x7f82990aefcc]
-> /usr/local/lib/dovecot/lib20_fts_plugin.so(fts_parser_more+0x27)
[0x7f82990aeca7] ->
/usr/local/lib/dovecot/lib20_fts_plugin.so(fts_build_mail+0x5e9)
[0x7f82990acc39] ->
/usr/local/lib/dovecot/lib20_fts_plugin.so(+0x1122d) [0x7f82990b322d]
-> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0x916a)
[0x7f82958e316a] ->
/usr/local/lib/dovecot/lib20_fts_plugin.so(+0x10f5d) [0x7f82990b2f5d]
-> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0x916a)
[0x7f82958e316a] ->
/usr/local/lib/dovecot/lib20_fts_plugin.so(+0x10f5d) [0x7f82990b2f5d]
-> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x2e)
[0x7f829a2641be] -> dovecot/indexer-worker [jakob
Synoptic/AKTUELL](+0x2533) [0x562227882533] ->
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69)
[0x7f8299f91bf9] ->
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x109)
[0x7f8299f93499] ->
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52)
[0x7f8299f91d02] ->
/usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38)
[0x7f8299f91f18] ->
/usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13)
[0x7f8299f0f1e3] -> dovecot/indexer-worker [jakob
Synoptic/AKTUELL](main+0xe7) [0x562227881f47] ->
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)
[0x7f8299b352b1] -> dovecot/indexer-worker [jakob
Synoptic/AKTUELL](_start+0x2a) [0x56222788201a]
Jän 03 16:27:08 aldebaran dovecot[26460]: indexer: Error: Indexer
worker disconnected, discarding 1 requests for jakob
Jän 03 16:27:08 aldebaran dovecot[26460]:
imap(jakob)<26472>: Error: indexer failed to index
mailbox Synoptic/AKTUELL
Jän 03 16:27:08 aldebaran dovecot[26460]:
indexer-worker(jakob)<26476>:
Fatal: master: service(indexer-worker): child 26476 killed with signal
6 (core dumps disabled)
Jän 03 16:27:09 aldebaran dovecot[26460]:
indexer-worker(jakob)<26484>:
Error: lucene index
/var/lib/dovecot/db/indexes/Maildir/jakob/lucene-indexes:
IndexWriter() failed (#1): Lock obtain timed out
Jän 03 16:27:10 aldebaran dovecot[26460]:
indexer-worker(jakob)<26484>:
Error: Mailbox Synoptic/AKTUELL: Transaction commit failed: BUG:
Unknown internal error (attempted to index 1488 messages (UIDs
15214..16775))
Jän 03 16:27:10 aldebaran dovecot[26460]:
imap(jakob)<26480>: Error: indexer failed to index
mailbox Synoptic/AKTUELL
Jän 03 16:27:11 aldebaran dovecot[26460]:
imap(jakob)<26472>: Panic: file mail-index.c: line
793 (mail_index_close): assertion failed: (index->open_count > 0)
Jän 03 16:27:11 aldebaran dovecot[26460]:
imap(jakob)<26472>: Error: Raw backtrace:
/usr/local/lib/dovecot/libdovecot.so.0(+0xc6021) [0x7fb0fbd3a021] ->
/usr/local/lib/dovecot/libdovecot.so.0(+0xc60ed) [0x7fb0fbd3a0ed] ->
/usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fb0fbcac481] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0(+0xf39a8)
[0x7fb0fc0d99a8] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0(+0xd92d1)
[0x7fb0fc0bf2d1] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0(+0xd9363)
[0x7fb0fc0bf363] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_free+0x9)
[0x7fb0fc0b0f39] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0(+0xd05a4)
[0x7fb0fc0b65a4] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_free+0x19)
[0x7fb0fc030c99] ->

Re: Dovecot 2.3.0, Panic: file mailbox-attribute.c: line 362 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL)

2018-02-05 Thread Marco Giunta


Hi,

If I downgrade to Dovecot 2.2.33.2, there are no problems to sync users 
with ACL


Thanks,
  Marco

On 2018-02-02 14:39, Marco Giunta wrote:

Hi at all,
I have a RHEL7 server with Dovecot 2.3.0 (new installation). I've a 
problem when trying to dsync from a Dovecot 2.2.24 server.


If I try to sync any user with a folder with ACL, dsycn crash with panic:

Source server:

dsync-local(USERNAME): Debug: sieve: file storage: sync: Synchronization 
active
dovecot: dsync-local(USERNAME): Debug: acl vfile: reading file 
/var/spool/mail/U/USERNAME/dovecot-acl
dsync-local(USERNAME): Error: read(DEST_SERVER.example.com) failed: EOF 
(last sent=mail_change (EOL), last recv=mailbox)


Destination server:

Feb  2 14:15:23 DEST_SERVER dovecot: dsync-server(USERNAME): Panic: file 
mailbox-attribute.c: line 362 (mailbox_attribute_get_stream): assertion 
failed: (value_r->value != NULL || value_r->value_stream != NULL)
Feb  2 14:15:23 DEST_SERVER dovecot: dsync-server(USERNAME): Error: Raw 
backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc8cc4) [0x7fa861bc0cc4] 
-> /usr/lib64/dovecot/libdovecot.so.0(+0xc8d7e) [0x7fa861bc0d7e] -> 
/usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa861b34190] -> 
/usr/lib64/dovecot/libdovecot-storage.so.0(+0x55cbc) [0x7fa861ec1cbc] -> 
dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests 
recv:attributes](dsync_mailbox_import_attribute+0x4d) [0x55b9d4ce215d] 
-> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests 
recv:attributes](dsync_brain_sync_mails+0x2ef) [0x55b9d4cddbdf] -> 
dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests 
recv:attributes](dsync_brain_run+0x2b0) [0x55b9d4cd93e0] -> 
dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests 
recv:attributes](+0x43a10) [0x55b9d4cd9a10] -> dovecot/doveadm-server 
[10.0.11.137 USERNAME INBOX send:mail_requests 
recv:attributes](+0x5837f) [0x55b9d4cee37f] -> 
/usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) 
[0x7fa861bd82b5] -> 
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) 
[0x7fa861bd9b5f] -> 
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) 
[0x7fa861bd83b2] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) 
[0x7fa861bd85d8] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX 
send:mail_requests recv:attributes](+0x28369) [0x55b9d4cbe369] -> 
dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests 
recv:attributes](+0x29c07) [0x55b9d4cbfc07] -> dovecot/doveadm-server 
[10.0.11.137 USERNAME INBOX send:mail_requests 
recv:attributes](+0x3f969) [0x55b9d4cd5969] -> 
/usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) 
[0x7fa861bd82b5] -> 
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) 
[0x7fa861bd9b5f] -> 
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) 
[0x7fa861bd83b2] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) 
[0x7fa861bd85d8] -> 
/usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7fa861b56b23] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX 
send:mail_requests recv:attributes](main+0x1b6) [0x55b9d4cb0536] -> 
/lib64/libc.so.6(__libc_start_main+0xf5) [0x7fa861756c05] -> 
dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests 
recv:attributes](+0x1a5f5) [0x55b9d4cb05f5]
Feb  2 14:15:23 DEST_SERVER dovecot: dsync-server(USERNAME): Fatal: 
master: service(doveadm): child 2149 killed with signal 6 (core dumped)



Coredump and configuration attached.


On source server I run this command:

# doveadm -D backup -f -u USERNAME -x 'Archives*' 
tcp:DEST_SERVER.example.com


but same panic if try to sync from destination server:

# doveadm -D backup -fR -u USERNAME -x 'Archives*' 
tcp:SOURCE_SERVER.example.com



Same panic also syncing any user with acl and using different 
acl_shared_dict (file or fs:posix) in dovecot configuration.


Thanks,
   Marco




--
Marco Giunta - ITCS SysAdmin
Via Bonomea, 265
34136 - Trieste, Italy
Tel: +39-040-3787-503
Fax: +39-040-3787-244

Re: Cannot delete IMAP Mail-Folder in Trash

Dovecot and /dev/rand

Re: Does Dovecot LDAP auth support LDAP referral

Re: Cannot delete IMAP Mail-Folder in Trash

Re: Cannot delete IMAP Mail-Folder in Trash

Re: Cannot delete IMAP Mail-Folder in Trash

Re: Bug in dovecot 2.3 virtual plugin

Re: Re: Bug in dovecot 2.3 virtual plugin

Re: Dovecot 2.3.0, Panic: file mailbox-attribute.c: line 362 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL)

9 matches

Site Navigation

Mail list logo

Footer information