Log message:
dovecot2-pigeonhole: updated to 0.5.21.1

v0.5.21.1

- sieve: When saving to local storage failed after a successful action
  in sieve (e.g. redirect, vacation), the mail was reported as
  successfully delivered, although it was lost locally.

Log message:
*: bump for openssl 3

Log message:
mail/dovecot2-pigeonhole: Update to 0.5.21

Changelog:
- sieve: Using the deleteheader action on a message with a broken/invalid
  header can cause the Sieve interpreter to crash with an assert panic.
  This can happen e.g. when the message is missing the empty EOH line
  between the headers and the body of the message. Fixes:
  Panic: file edit-mail.c: line 820 (edit_mail_headers_parse):
  assertion failed: (body_offset > 0).
- sieve: Pigeonhole added an extra Message-ID header during mail
  forwarding when the existing one was invalid. Now it adds the
  Message-ID only if it is entirely missing. Existing Message-ID(s) are
  left unchanged.

Log message:
dovecot2: updated to 2.3.20

v2.3.20

+ Add dsync_features=no-header-hashes. When this setting is enabled and
  one dsync side doesn't support mail GUIDs (i.e. imapc), there is no
  fallback to using header hashes. Instead, dsync assumes that all mails
  with identical IMAP UIDs contains the same mail contents. This can
  significantly improve dsync performance with some IMAP servers that
  don't support caching Date/Message-ID headers.
+ lua: HTTP client has more settings now, see
  https://doc.dovecot.org/admin_manual/lua/#dovecot.http.client
+ replicator: "doveadm replicator status" command now outputs when the
  next sync is expected for the user.
- LAYOUT=index: duplicate GUIDs were not cleaned out. Also the list
  recovery was not optimal.
- auth: Assert crash would occur when iterating multiple userdb
  backends.
- director: Logging into director using master user with
  auth_master_user_separator character redirected user to a wrong
  backend, unless master_user_separator setting was also set to the same
  value. Merged these into auth_master_user_separator.
- dsync: Couldn't always fix folder GUID conflicts automatically with
  Maildir format. This resulted in replication repeatedly failing
  with "Remote lost mailbox GUID".
- dsync: Failed to migrate INBOX when using namespace prefix=INBOX/,
  resulting in "Remote lost mailbox GUID" errors.
- dsync: INBOX was created too early with namespace prefix=INBOX/,
  resulting a GUID conflict. This may have been resolved automatically,
  but not always.
- dsync: v2.3.18 regression: Wrong imapc password with dsync caused
  Panic: file lib-event.c: line 506 (event_pop_global):
  assertion failed: (event == current_global_event)
- imapc: Requesting STATUS for a mailbox with imapc and INDEXPVT
  configured did not return correct (private) unseen counts.
- lib-dict: Process would crash when committing data to redis without
  dict proxy.
- lib-mail: Corrupted cached BODYSTRUCTURE caused panic during FETCH.
  Fixes: Panic: file message-part-data.c: line 579 (message_part_is_attachment):
  assertion failed: (data != NULL). v2.3.13 regression.
- lib-storage: mail_attribute_dict with dict-sql failed when it tried to
  lookup empty dict keys.
- lib: ioloop-kqueue was missing include breaking some BSD builds.
- lua-http: Dovecot Lua HTTP client could not resolve DNS names in mail
  processes, because it expected "dns-client" socket to exist in the
  current directory.
- oauth2: Using %{oauth2:name} variables could cause useless
  introspections.
- pop3: Sending POP3 command with ':' character caused an assert-crash.
  v2.3.18 regression.
- replicator: Replication queue had various issues, potentially causing
  replication requests to become stuck.
- stats: Invalid Prometheus label names were created with specific

v0.5.20 of Pigeonhole
* No changes - release done to keep version numbers synced.

Log message:
dovecot2-pigeonhole: updated to 0.5.19

This release is done to maintain parity with dovecot 2.3.19 release, so it does \ 
not contain any news-worthy changes.

Log message:
dovecot2-pigeonhole: updated to 0.5.18

v0.5.18

	- duplicate: Users without a home directory can crash with Sieve when
	  using duplicate database. v2.3.17 regression.
	- imapsieve: When mail was expunged when processing imapsieve events, a
	  crash could occur. Fixes Panic: file mail-index-map.c:
	  line 558 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
	- managesieve-login: Proxy didn't support forwarding the forward_* passdb fields.
	- redirect: Sieve would crash if redirect after keep-equivalent action failed.
	- sieve: Interpreter crashes when the Sieve index extension is used with
	  index zero.
	- vnd.dovecot.filter: Envelope sender string may become corrupted when
	  Sieve scripts are using vnd.dovecot.filter. This could end up
	  corrupting mbox's From line and return wrong envelope sender string in
	  Sieve tests.

Log message:
dovecot2-pigeonhole: updated to 0.5.17.1

0.5.17.1:
- managesieve: Dovecot failed to start if ssl_ca was too large.
- lib-sieve-tool: Binaries failed to run if ssl_ca was too large.

Log message:
dovecot2-pigeonhole: updated to 0.5.17

0.5.17:
- duplicate: The Sieve duplicate test is prone to false negatives when
  the user receives many e-mails concurrently, meaning that duplicate
  deliveries can still occur.
- fileinto: v2.3.16 regression: Sieve delivery crashes if mail is
  delivered to non-existing and existing folder.
- imap-filter-sieve: v2.3.15 regression: The CPU limits on Sieve
  execution are too easily exceeded in IMAP context (the IMAPSieve and
  FILTER=SIEVE capabilities). Changed the default to unlimited CPU time
  for IMAP context, since similar excessive resource usage can be caused
  by other means as well. The CPU limits on Sieve scripts executed at
  LDA/LMTP delivery are still enforced by default.
- redirect:  The Sieve redirect action has protections against users
  triggering mail loops. Unfortunately, the detection of a redirect mail
  loop sometimes causes the message to get lost if no other Sieve action
  is applied that delivers the message somewhere else.
- redirect: v2.3.16 regression: With certain Sieve scripts if redirect
  fails due to temporary failure, the lmtp process may crash after the
  delivery. Fixes:
  Panic: file mail-user.c: line 229 (mail_user_deinit):
  assertion failed: ((*user)->refcount == 1).