public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] fetchmail: Update to version 6.6.6
Date: Fri,  3 Jul 2026 21:41:24 +0200	[thread overview]
Message-ID: <20260703194133.2938870-10-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20260703194133.2938870-1-adolf.belka@ipfire.org>

- Update from version 6.6.5 to 6.6.6
- No change to rootfile
- Changelog
6.6.6
CRITICAL BUGFIX FOR IMAP:
* The IMAP client, which has always used message indexes for the selected
   mailbox, did not abort when receiving an EXPUNGE response - which changes
   message numbers inside the mailbox.  Unlike UIDs, the message numbers are
   not stable and fetchmail does not have internal interfaces to track which
   messages are deleted, and adding those to a 6.6.X release would be too
   risky, and switching to UID is also too big a change, so we have no
   choice but to abort the session when seeing an EXPUNGE response without
   our own EXPUNGE request, to avoid marking the wrong message as seen/deleted
   or skip the wrong one, or assume the wrong message size.
   Earl Chew reported this versus Yahoo Mail via Gitlab Work Item #91, which
   automatically expunges messages that are marked with the \Deleted flag.
  This has one new message for which we do not have translations yet,
   it is urgent to get the fix in the field.

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 lfs/fetchmail | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/fetchmail b/lfs/fetchmail
index e3d4e1dd0..4b5fc42d7 100644
--- a/lfs/fetchmail
+++ b/lfs/fetchmail
@@ -26,7 +26,7 @@ include Config
 
 SUMMARY    = Full-Featured POP and IMAP Mail Retrieval Daemon
 
-VER        = 6.6.5
+VER        = 6.6.6
 
 THISAPP    = fetchmail-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = fetchmail
-PAK_VER    = 25
+PAK_VER    = 26
 
 DEPS       =
 
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = cceb7a0673f6aea76fe5619c0b6a4cd25566adc31b8d9a8e574b3abf8584107b882f71a63d5690ce76822044cc8a2dd431e44813002740ebcbd3cc55b4e9105f
+$(DL_FILE)_BLAKE2 = 0f7a26a2f34d902d30801d5016e67697877f7c3f41dc9d9c4a1b44420c9e08f6acd94853c298b2938b9ddf08b3aa3115a14917f42d680f3ada8daba0e5f50953
 
 install : $(TARGET)
 
-- 
2.55.0



  parent reply	other threads:[~2026-07-03 19:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03 19:41 [PATCH] core204: Ship curl Adolf Belka
2026-07-03 19:41 ` [PATCH] core204: Ship glib Adolf Belka
2026-07-03 19:41 ` [PATCH] core204: Ship json-c Adolf Belka
2026-07-03 19:41 ` [PATCH] core204: Ship libarchive Adolf Belka
2026-07-03 19:41 ` [PATCH] core204: Ship libjpeg Adolf Belka
2026-07-03 19:41 ` [PATCH] core204: Ship pango Adolf Belka
2026-07-03 19:41 ` [PATCH] core204: Ship systemd Adolf Belka
2026-07-03 19:41 ` [PATCH] core204: Ship vim Adolf Belka
2026-07-03 19:41 ` [PATCH] curl: Update to version 8.21.0 Adolf Belka
2026-07-03 19:41 ` Adolf Belka [this message]
2026-07-03 19:41 ` [PATCH] git: Update to version 2.55.0 Adolf Belka
2026-07-03 19:41 ` [PATCH] glib: Update to version 2.88.2 Adolf Belka
2026-07-03 19:41 ` [PATCH] json-c: Update to version 0.19 Adolf Belka
2026-07-03 19:41 ` [PATCH] libarchive: Update to version 3.8.8 Adolf Belka
2026-07-03 19:41 ` [PATCH] libjpeg: Update to version 3.2.0 Adolf Belka
2026-07-03 19:41 ` [PATCH] pango: Update to version 1.58.0 Adolf Belka
2026-07-03 19:41 ` [PATCH] sqlite: Update to version 3530300 Adolf Belka
2026-07-03 19:41 ` [PATCH] systemd: Update to version 261.1 Adolf Belka
2026-07-03 19:41 ` [PATCH] vim: Update to version 9.2.0769 Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260703194133.2938870-10-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox