Replication issue 2.3.7
Hello!
I noticed these in the logs since upgrading from 2.3.6. to 2.3.7:
Jul 13 11:52:10 turin dovecot: doveadm: Error:
dsync-remote(r...@mrstuudio.ee): Error:
Exporting mailbox INBOX failed: Mailbox attribute
vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox
attributes not enabled
Jul 13 11:52:11 turin dovecot: doveadm: Error:
dsync-remote(r...@mrstuudio.ee): Error:
Exporting mailbox INBOX failed: Mailbox attribute
vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox
attributes not enabled
After turning on mailbox attributes these errors went away:
mail_attribute_dict = file:~/Maildir/dovecot-attributes
protocol imap {
imap_metadata = yes
}
But now the errors are replaced with (when deleting mail):
Jul 13 12:04:32 turin dovecot: imap(r...@mrstuudio.ee): Warning:
/home/vmail/mrstuudio.ee/reio/Maildir/dovecot-uidlist: Duplicate file
entry at line 2: 1563008644.M18534P25946.orc.mrstuudio.ee,S=4180,W=4262
(uid 23030 -> 23031) - retrying by re-reading from beginning
Jul 13 12:04:32 turin dovecot: imap(r...@mrstuudio.ee): Warning: Maildir
/home/vmail/mrstuudio.ee/reio/Maildir: Expunged message reappeared,
giving a new UID (old uid=23030,
file=1563008644.M18534P25946.orc.mrstuudio.ee,S=4180,W=4262:2,S)
The mail message reappears on the other side of dsync and eventually I
end up with 3 identical messages in trash after I've deleted them on
both sides.
Thanks for any advice,
Reio
Re: Replication issue 2.3.7
On 13.07.2019 12:13, Reio Remma via dovecot wrote:
Hello!
I noticed these in the logs since upgrading from 2.3.6. to 2.3.7:
Jul 13 11:52:10 turin dovecot: doveadm: Error:
dsync-remote(r...@mrstuudio.ee): Error:
Exporting mailbox INBOX failed: Mailbox attribute
vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox
attributes not enabled
Jul 13 11:52:11 turin dovecot: doveadm: Error:
dsync-remote(r...@mrstuudio.ee): Error:
Exporting mailbox INBOX failed: Mailbox attribute
vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox
attributes not enabled
After turning on mailbox attributes these errors went away:
mail_attribute_dict = file:~/Maildir/dovecot-attributes
protocol imap {
imap_metadata = yes
}
But now the errors are replaced with (when deleting mail):
Jul 13 12:04:32 turin dovecot: imap(r...@mrstuudio.ee): Warning:
/home/vmail/mrstuudio.ee/reio/Maildir/dovecot-uidlist: Duplicate file
entry at line 2:
1563008644.M18534P25946.orc.mrstuudio.ee,S=4180,W=4262 (uid 23030 ->
23031) - retrying by re-reading from beginning
Jul 13 12:04:32 turin dovecot: imap(r...@mrstuudio.ee): Warning:
Maildir /home/vmail/mrstuudio.ee/reio/Maildir: Expunged message
reappeared, giving a new UID (old uid=23030,
file=1563008644.M18534P25946.orc.mrstuudio.ee,S=4180,W=4262:2,S)
The mail message reappears on the other side of dsync and eventually I
end up with 3 identical messages in trash after I've deleted them on
both sides.
Thanks for any advice,
Reio
More info:
the issue manifests itself when I read a freshly arrived message on one
server and then delete it on the other server.
If I delete it on the same server after reading, it seems to work.
The mail client is Thunderbird.
Reio
Re: Applying Dovecot for a large / deep folder-hierarchy archive - BUG REPORTS!
Sure Adam, this makes perfect sense. And having properly reviewed the "debian-release" mailing list description, I can see that this is made quite clear: > Coordinating Debian releases > Coordination of Debian releases issues such as testing migrations, > transitions and removals. This list should not be considered a > discussion list; discussions related to releases issues should be > held on more appropriate lists such as debian-devel, debian-legal or > debian-project. Best regards, Arnold Opio Oree Chief Executive Officer Parallax Digital Technologies arnoldo...@parallaxdt.com http://www.parallaxdt.com tel : +44 (0) 333 577 8587 fax : +44 (0) 20 8711 2477 Parallax Digital Technologies is a trading name of Parallax Global Limited. U.K. Co. No. 08836288 The contents of this e-mail are confidential. If you are not the intended recipient you are to delete this e-mail immediately, disregard its contents and disclose them to no other persons. -Original Message- From: Adam D. Barratt via dovecot Reply-To: Adam D. Barratt To: arnoldo...@parallaxict.com Cc: t...@sirainen.com, debian-rele...@lists.debian.org, Dovecot Mailing List Subject: Re: Applying Dovecot for a large / deep folder-hierarchy archive - BUG REPORTS! Date: Fri, 12 Jul 2019 13:43:34 +0100 On Wed, 2019-07-10 at 12:26 +0100, Arnold Opio Oree wrote: > Understood Adam, > > My thinking is that this is a package released with Debian 10. And so > has everything to do with the release. For clarity here - debian-release is neither a support forum nor a discussion list, nor a means of reporting issues in software contained within a Debian release. Debian has support fora and a bug tracking system to handle such reports and issues, as per https://www.debian.org /support . Having a single list that discusses any issue in any piece of software shipped by Debian cannot possibly scale. Rather, this list is the contact point and team alias for the Release Team, who oversee and manage the release process. It is up to individual package maintainers to triage and deal with issues reported against their packages and then to liaise with us if required. Regards, Adam --
Re: Dovecot release v2.3.7
LMTP is broken on director:
Jul 13 13:42:41 lmtp(34824): Panic: file smtp-params.c: line 685
(smtp_params_mail_add_body_to_event): assertion failed: ((caps &
SMTP_CAPABILITY_8BITMIME) != 0)
Jul 13 13:42:41 lmtp(34824): Error: Raw backtrace:
/usr/lib64/dovecot/libdovecot.so.0(+0xdf06a) [0x7f561203806a] ->
/usr/lib64/dovecot/libdovecot.so.0(+0xdf0b1) [0x7f56120380b1] ->
/usr/lib64/dovecot/libdovecot.so.0(+0x40161) [0x7f5611f99161] ->
/usr/lib64/dovecot/libdovecot.so.0(+0x44fc4) [0x7f5611f9dfc4] ->
/usr/lib64/dovecot/libdovecot.so.0(smtp_client_transaction_start+0x78)
[0x7f5611fa7a58] -> dovecot/lmtp [172.17.165.6 MAIL
FROM](lmtp_proxy_rcpt+0xa37) [0x558eaf181d67] -> dovecot/lmtp
[172.17.165.6 MAIL FROM](client_default_cmd_rcpt+0x9e) [0x558eaf17eebe]
-> /usr/lib64/dovecot/libdovecot.so.0(smtp_server_cmd_rcpt+0x222)
[0x7f5611fafd12] ->
/usr/lib64/dovecot/libdovecot.so.0(smtp_server_command_new+0x150)
[0x7f5611fb58a0] -> /usr/lib64/dovecot/libdovecot.so.0(+0x606c8)
[0x7f5611fb96c8] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x55)
[0x7f561204f275] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x95)
[0x7f561204f3a5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38)
[0x7f561204f588] ->
/usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13)
[0x7f5611fc68f3] -> dovecot/lmtp [172.17.165.6 MAIL FROM](main+0x289)
[0x558eaf17dc19] -> /lib64/libc.so.6(__libc_start_main+0x100)
[0x7f5611be3d20] -> dovecot/lmtp [172.17.165.6 MAIL FROM](+0x5849)
[0x558eaf17d849]
---
Tom
On 2019-07-12 14:29, Aki Tuomi via dovecot wrote:
Hi!
We are pleased to release Dovecot release v2.3.7.
Tarball is available at
https://dovecot.org/releases/2.3/dovecot-2.3.7.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.7.tar.gz.sig
Binary packages are available at https://repo.dovecot.org/
Changes
---
* fts-solr: Removed break-imap-search parameter
+ Added more events for the new statistics, see
https://doc.dovecot.org/admin_manual/list_of_events/
+ mail-lua: Add IMAP metadata accessors, see
https://doc.dovecot.org/admin_manual/lua/
+ Add event exporters that allow exporting raw events to log files and
external systems, see
https://doc.dovecot.org/configuration_manual/event_export/
+ SNIPPET is now PREVIEW and size has been increased to 200 characters.
+ Add body option to fts_enforced. This triggers building FTS index
only
on body search, and an error using FTS index fails the search rather
than reads through all the mails.
- Submission/LMTP: Fixed crash when domain argument is invalid in a
second EHLO/LHLO command.
- Copying/moving mails using Maildir format loses IMAP keywords in the
destination if the mail also has no system flags.
- mail_attachment_detection_options=add-flags-on-save caused email body
to be unnecessarily opened when FETCHing mail headers that were
already cached.
- mail attachment detection keywords not saved with maildir.
- dovecot.index.cache may have grown excessively large in some
situations. This happened especially when using autoexpunging with
lazy_expunge folders. Also with mdbox format in general the cache
file
wasn't recreated as often as it should have.
- Autoexpunged mails weren't immediately deleted from the disk.
Instead,
the deletion from disk happened the next time the folder was opened.
This could have caused unnecessary delays if the opening was done by
an interactive IMAP session.
- Dovecot's TCP connections sometimes add extra 40ms latency due to not
enabling TCP_NODELAY. HTTP and SMTP/LMTP connections weren't
affected, but everything else was. This delay wasn't always visible -
only in some situations with some message/packet sizes.
- imapc: Fix various crash conditions
- Dovecot builds were not always reproducible.
- login-proxy: With shutdown_clients=no after config reload the
existing connections could no longer be listed or kicked with
doveadm.
- "doveadm proxy kick" with -f parameter caused a crash in some
situations.
- Auth policy can cause segmentation fault crash during auth process
shutdown if all auth requests have not been finished.
- Fix various minor bugs leading into incorrect behaviour in mailbox
list index handling. These rarely caused noticeable problems.
- LDAP auth: Iteration accesses freed memory, possibly crashing
auth-worker
- local_name { .. } filter in dovecot.conf does not correctly support
multiple names and wildcards were matched incorrectly.
- replicator: dsync assert-crashes if it can't connect to remote TCP
server.
- config: Memory leak in config process when ssl_dh setting wasn't
set and there was no ssl-parameters.dat file.
This caused config process to die once in a while
with "out of memory".
---
Aki Tuomi
Open-Xchange oy
Re: Dovecot release v2.3.7
Can you please put dovecot-2.3.6-2.x86_64 back in the repo so we can
downgrade?
---
Tom
On 2019-07-12 14:29, Aki Tuomi via dovecot wrote:
Hi!
We are pleased to release Dovecot release v2.3.7.
Tarball is available at
https://dovecot.org/releases/2.3/dovecot-2.3.7.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.7.tar.gz.sig
Binary packages are available at https://repo.dovecot.org/
Changes
---
* fts-solr: Removed break-imap-search parameter
+ Added more events for the new statistics, see
https://doc.dovecot.org/admin_manual/list_of_events/
+ mail-lua: Add IMAP metadata accessors, see
https://doc.dovecot.org/admin_manual/lua/
+ Add event exporters that allow exporting raw events to log files and
external systems, see
https://doc.dovecot.org/configuration_manual/event_export/
+ SNIPPET is now PREVIEW and size has been increased to 200 characters.
+ Add body option to fts_enforced. This triggers building FTS index
only
on body search, and an error using FTS index fails the search rather
than reads through all the mails.
- Submission/LMTP: Fixed crash when domain argument is invalid in a
second EHLO/LHLO command.
- Copying/moving mails using Maildir format loses IMAP keywords in the
destination if the mail also has no system flags.
- mail_attachment_detection_options=add-flags-on-save caused email body
to be unnecessarily opened when FETCHing mail headers that were
already cached.
- mail attachment detection keywords not saved with maildir.
- dovecot.index.cache may have grown excessively large in some
situations. This happened especially when using autoexpunging with
lazy_expunge folders. Also with mdbox format in general the cache
file
wasn't recreated as often as it should have.
- Autoexpunged mails weren't immediately deleted from the disk.
Instead,
the deletion from disk happened the next time the folder was opened.
This could have caused unnecessary delays if the opening was done by
an interactive IMAP session.
- Dovecot's TCP connections sometimes add extra 40ms latency due to not
enabling TCP_NODELAY. HTTP and SMTP/LMTP connections weren't
affected, but everything else was. This delay wasn't always visible -
only in some situations with some message/packet sizes.
- imapc: Fix various crash conditions
- Dovecot builds were not always reproducible.
- login-proxy: With shutdown_clients=no after config reload the
existing connections could no longer be listed or kicked with
doveadm.
- "doveadm proxy kick" with -f parameter caused a crash in some
situations.
- Auth policy can cause segmentation fault crash during auth process
shutdown if all auth requests have not been finished.
- Fix various minor bugs leading into incorrect behaviour in mailbox
list index handling. These rarely caused noticeable problems.
- LDAP auth: Iteration accesses freed memory, possibly crashing
auth-worker
- local_name { .. } filter in dovecot.conf does not correctly support
multiple names and wildcards were matched incorrectly.
- replicator: dsync assert-crashes if it can't connect to remote TCP
server.
- config: Memory leak in config process when ssl_dh setting wasn't
set and there was no ssl-parameters.dat file.
This caused config process to die once in a while
with "out of memory".
---
Aki Tuomi
Open-Xchange oy
Re: Pigeonhole-0.5.7 fails to build from sources
On Sat, 13 Jul 2019 02:34:09 +0300, Lefteris Tsintjelis via dovecot stated: >Solution is to uninstall the port and then build. If dovecot is >already installed it will not build. > >On 13/7/2019 0:08, Lefteris Tsintjelis via dovecot wrote: >> Latest update fails to build from sources in FreeBSD 12-STABLE >> >> --- lda-sieve-plugin.lo --- >> lda-sieve-plugin.c:82:27: error: variable has incomplete type >> 'struct smtp_submit_input' >> struct smtp_submit_input submit_input; I am using 'poudriere' on a FreeBSD 12.0-RELEASE-p7, and both dovecot and pigeonhole build and install correctly. You do have to restart dovecot after the update though. -- Jerry
Re: Replication issue 2.3.7
Hello,
Thanks for the info and workaround!
I found and have the same problems after read your mail :-(.
Am Samstag, 13. Juli 2019, 11:13:23 CEST schrieb Reio Remma via dovecot:
> Hello!
>
> I noticed these in the logs since upgrading from 2.3.6. to 2.3.7:
>
> Jul 13 11:52:10 turin dovecot: doveadm: Error:
> dsync-remote(r...@mrstuudio.ee): Error:
> Exporting mailbox INBOX failed: Mailbox attribute
> vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox
> attributes not enabled
> Jul 13 11:52:11 turin dovecot: doveadm: Error:
> dsync-remote(r...@mrstuudio.ee): Error:
> Exporting mailbox INBOX failed: Mailbox attribute
> vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox
> attributes not enabled
>
> After turning on mailbox attributes these errors went away:
>
> mail_attribute_dict = file:~/Maildir/dovecot-attributes
>
> protocol imap {
> imap_metadata = yes
> }
>
> But now the errors are replaced with (when deleting mail):
>
> Jul 13 12:04:32 turin dovecot: imap(r...@mrstuudio.ee): Warning:
> /home/vmail/mrstuudio.ee/reio/Maildir/dovecot-uidlist: Duplicate file
> entry at line 2: 1563008644.M18534P25946.orc.mrstuudio.ee,S=4180,W=4262
> (uid 23030 -> 23031) - retrying by re-reading from beginning
> Jul 13 12:04:32 turin dovecot: imap(r...@mrstuudio.ee): Warning: Maildir
> /home/vmail/mrstuudio.ee/reio/Maildir: Expunged message reappeared,
> giving a new UID (old uid=23030,
> file=1563008644.M18534P25946.orc.mrstuudio.ee,S=4180,W=4262:2,S)
>
> The mail message reappears on the other side of dsync and eventually I
> end up with 3 identical messages in trash after I've deleted them on
> both sides.
>
> Thanks for any advice,
> Reio
--
mit freundliche Grüßen / best regards,
Günther J. Niederwimmer
Re: Dovecot release v2.3.7
On 2019-07-13 13:44, Tom Sommer via dovecot wrote: LMTP is broken on director: Jul 13 13:42:41 lmtp(34824): Panic: file smtp-params.c: line 685 (smtp_params_mail_add_body_to_event): assertion failed: ((caps & SMTP_CAPABILITY_8BITMIME) != 0) Jul 13 13:42:41 lmtp(34824): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xdf06a) [0x7f561203806a] -> /usr/lib64/dovecot/libdovecot.so.0(+0xdf0b1) [0x7f56120380b1] -> /usr/lib64/dovecot/libdovecot.so.0(+0x40161) [0x7f5611f99161] -> /usr/lib64/dovecot/libdovecot.so.0(+0x44fc4) [0x7f5611f9dfc4] -> /usr/lib64/dovecot/libdovecot.so.0(smtp_client_transaction_start+0x78) [0x7f5611fa7a58] -> dovecot/lmtp [172.17.165.6 MAIL FROM](lmtp_proxy_rcpt+0xa37) [0x558eaf181d67] -> dovecot/lmtp [172.17.165.6 MAIL FROM](client_default_cmd_rcpt+0x9e) [0x558eaf17eebe] -> /usr/lib64/dovecot/libdovecot.so.0(smtp_server_cmd_rcpt+0x222) [0x7f5611fafd12] -> /usr/lib64/dovecot/libdovecot.so.0(smtp_server_command_new+0x150) [0x7f5611fb58a0] -> /usr/lib64/dovecot/libdovecot.so.0(+0x606c8) [0x7f5611fb96c8] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x55) [0x7f561204f275] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x95) [0x7f561204f3a5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f561204f588] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f5611fc68f3] -> dovecot/lmtp [172.17.165.6 MAIL FROM](main+0x289) [0x558eaf17dc19] -> /lib64/libc.so.6(__libc_start_main+0x100) [0x7f5611be3d20] -> dovecot/lmtp [172.17.165.6 MAIL FROM](+0x5849) [0x558eaf17d849] Downgraded to 2.3.6 (from source, because it's gone from repo) - Works. -- Tom
Re: Dovecot release v2.3.7
On 13/07/2019 15:51 Tom Sommer via dovecot < dovecot@dovecot.org> wrote: On 2019-07-13 13:44, Tom Sommer via dovecot wrote: LMTP is broken on director: Jul 13 13:42:41 lmtp(34824): Panic: file smtp-params.c: line 685 (smtp_params_mail_add_body_to_event): assertion failed: ((caps & SMTP_CAPABILITY_8BITMIME) != 0) Jul 13 13:42:41 lmtp(34824): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xdf06a) [0x7f561203806a] -> /usr/lib64/dovecot/libdovecot.so.0(+0xdf0b1) [0x7f56120380b1] -> /usr/lib64/dovecot/libdovecot.so.0(+0x40161) [0x7f5611f99161] -> /usr/lib64/dovecot/libdovecot.so.0(+0x44fc4) [0x7f5611f9dfc4] -> /usr/lib64/dovecot/libdovecot.so.0(smtp_client_transaction_start+0x78) [0x7f5611fa7a58] -> dovecot/lmtp [172.17.165.6 MAIL FROM](lmtp_proxy_rcpt+0xa37) [0x558eaf181d67] -> dovecot/lmtp [172.17.165.6 MAIL FROM](client_default_cmd_rcpt+0x9e) [0x558eaf17eebe] -> /usr/lib64/dovecot/libdovecot.so.0(smtp_server_cmd_rcpt+0x222) [0x7f5611fafd12] -> /usr/lib64/dovecot/libdovecot.so.0(smtp_server_command_new+0x150) [0x7f5611fb58a0] -> /usr/lib64/dovecot/libdovecot.so.0(+0x606c8) [0x7f5611fb96c8] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x55) [0x7f561204f275] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x95) [0x7f561204f3a5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f561204f588] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f5611fc68f3] -> dovecot/lmtp [172.17.165.6 MAIL FROM](main+0x289) [0x558eaf17dc19] -> /lib64/libc.so.6(__libc_start_main+0x100) [0x7f5611be3d20] -> dovecot/lmtp [172.17.165.6 MAIL FROM](+0x5849) [0x558eaf17d849] Downgraded to 2.3.6 (from source, because it's gone from repo) - Works. -- Tom Its not gone. Try http://repo.dovecot.org/ce-2.3.6/ --- Aki Tuomi
Re: Replication issue 2.3.7
Hello,
this sounds like the replication problem that occured after 2.2.33.2:
https://www.dovecot.nl/list/dovecot/2018-March/111422.html
As far as I remember there is no fix yet.
Best regards
Gerald
> Am 13.07.2019 um 14:18 schrieb Günther J. Niederwimmer via dovecot
> :
>
> Hello,
>
> Thanks for the info and workaround!
>
> I found and have the same problems after read your mail :-(.
>
> Am Samstag, 13. Juli 2019, 11:13:23 CEST schrieb Reio Remma via dovecot:
>> Hello!
>>
>> I noticed these in the logs since upgrading from 2.3.6. to 2.3.7:
>>
>> Jul 13 11:52:10 turin dovecot: doveadm: Error:
>> dsync-remote(r...@mrstuudio.ee): Error:
>> Exporting mailbox INBOX failed: Mailbox attribute
>> vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox
>> attributes not enabled
>> Jul 13 11:52:11 turin dovecot: doveadm: Error:
>> dsync-remote(r...@mrstuudio.ee): Error:
>> Exporting mailbox INBOX failed: Mailbox attribute
>> vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox
>> attributes not enabled
>>
>> After turning on mailbox attributes these errors went away:
>>
>> mail_attribute_dict = file:~/Maildir/dovecot-attributes
>>
>> protocol imap {
>> imap_metadata = yes
>> }
>>
>> But now the errors are replaced with (when deleting mail):
>>
>> Jul 13 12:04:32 turin dovecot: imap(r...@mrstuudio.ee): Warning:
>> /home/vmail/mrstuudio.ee/reio/Maildir/dovecot-uidlist: Duplicate file
>> entry at line 2: 1563008644.M18534P25946.orc.mrstuudio.ee,S=4180,W=4262
>> (uid 23030 -> 23031) - retrying by re-reading from beginning
>> Jul 13 12:04:32 turin dovecot: imap(r...@mrstuudio.ee): Warning: Maildir
>> /home/vmail/mrstuudio.ee/reio/Maildir: Expunged message reappeared,
>> giving a new UID (old uid=23030,
>> file=1563008644.M18534P25946.orc.mrstuudio.ee,S=4180,W=4262:2,S)
>>
>> The mail message reappears on the other side of dsync and eventually I
>> end up with 3 identical messages in trash after I've deleted them on
>> both sides.
>>
>> Thanks for any advice,
>> Reio
>
>
> --
> mit freundliche Grüßen / best regards,
>
> Günther J. Niederwimmer
>
>
Re: Pigeonhole-0.5.7 fails to build from sources
On 13/7/2019 15:02, Jerry via dovecot wrote: > I am using 'poudriere' on a FreeBSD 12.0-RELEASE-p7, and both dovecot > and pigeonhole build and install correctly. It builds ok also with standard FreeBSD's "make" but it seems for some reason you have to remove both old versions of dovecot and pigeonhole ports, if you have them installed, before you start building the new ones. pigeonhole was building against the old version of dovecot installed and this is what caused the issue. Possibly other ways to build may not have this problem. Lefteris
Re: Dovecot release v2.3.7
Michael Grimm wrote: But, replication still doesn't works as known from previous versions. I will give it a try over night, but I am seeing … | Queued 'full resync' requests 1 … after 1 minute, already. The following modifications regarding my setup made replication work again (at least for the last 8 hours): #) Re-compiling dovecot with the patch from https://dovecot.org/pipermail/dovecot/2019-July/116479.html #) Activating mailbox attributes as mentioned in https://dovecot.org/pipermail/dovecot/2019-July/116492.html Now replication is working from my point of view, besides occational error messages like: | imap-login: Error: file_ostream.net_set_tcp_nodelay(, TRUE) failed: Connection reset by peer (This has been reported before: https://dovecot.org/pipermail/dovecot/2019-July/116491.html) Regards, Michael
Getting SSL certificate/key from database
Hello, I am not finding how to read SSL keys/certificates from database. Is this possible? Or only file reads allowed? -- Regards, Yevgeny
