Your message dated Mon, 21 Jul 2025 11:59:56 -0700
with message-id <2785365.icZtzsIVVb@soren-desktop>
and subject line Re: Bug#185041: courier-imap: UIDNEXT response not always 
correct
has caused the Debian Bug report #185041,
regarding courier-imap: UIDNEXT response not always correct
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
185041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185041
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: courier-imap
Version: 1.6.2-4
Severity: normal
Tags: upstream

When using courier imapd with sylpheed-claws strange things happend
and while I investigated the problem i found out that courier imap does
not follow the IMAP RFC correctly. The following log was producted by
sylpheed-claws:

[19:43:43] IMAP4> 274 STATUS INBOX (MESSAGES RECENT UIDNEXT UIDVALIDITY UNSEEN)
[19:43:43] IMAP4< * STATUS "INBOX" (MESSAGES 8 RECENT 0 UIDNEXT 68 UIDVALIDITY 
1046790905 UNSEEN 1)
[19:43:43] IMAP4< 274 OK STATUS Completed.

some other commands were executed in between...

[19:43:48] IMAP4> 279 APPEND INBOX (\Seen) {7701}
[19:43:48] IMAP4< + OK
[19:43:48] IMAP4> (sende Datei...)
[19:43:48] IMAP4< 279 OK [APPENDUID 1046790905 68] APPEND Ok.

[19:43:48] IMAP4> 280 STATUS INBOX (MESSAGES RECENT UIDNEXT UIDVALIDITY UNSEEN)
[19:43:48] IMAP4< * STATUS "INBOX" (MESSAGES 8 RECENT 0 UIDNEXT 68 UIDVALIDITY 
1046790905 UNSEEN 2)
[19:43:48] IMAP4< 280 OK STATUS Completed.

First a message was added and the imap server reported that the new
message got the UID 68 as expected because the last STATUS command
reported 68 for UIDNEXT. The problem is that the STATUS command after
the APPEND command still reports a UID of 68. But the RFC say:

      UIDNEXT        The next UID value that will be assigned to a new
                     message in the mailbox.  It is guaranteed that this
                                              ----------------
                     value will not change unless new messages are added
                     to the mailbox; and that it will change when new
                                         ----------------------------
                     messages are added even if those new messages are
                     ------------------
                     subsequently expunged.

Because of the wrong value for UIDNEXT sylpheed thinks the folder was
not changed and behaves incorrectly.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux navi 2.4.20 #9 Fre Nov 29 15:03:37 CET 2002 i686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro

Versions of packages courier-imap depends on:
ii  courier-authdaemon            0.40.2-4   Courier Mail Server authentication
ii  courier-base                  0.40.2-4   Courier Mail Server Base System
ii  exim [mail-transport-agent]   3.36-4     An MTA (Mail Transport Agent)
ii  libc6                         2.3.1-14   GNU C Library: Shared libraries an
ii  libfam0c102                   2.6.9-4    client library to control the FAM 
ii  libgdbmg1                     1.7.3-27.1 GNU dbm database routines (runtime

-- debconf information:
  courier-imap/moveconfig: true



--- End Message ---
--- Begin Message ---
Christoph,

On Monday, July 21, 2025 2:50:44 AM Mountain Standard Time Christoph Hohmann 
wrote:
> Soren Stoutner wrote:
> > I have recently taken over maintenance of the courier-imap package.  I
> > apologize that nobody responded to your bug report from 2003.
> > 
> > Can you confirm if this bug still exists with the current version of
> > courier-
> > imap in Debian (5.2.11+1.4.1-3)?
> 
> I have not used courier-imap and sylpheed for a long time. So I cannot
> tell you, if courier-imap is still has this bug nor if sylpheed is still
> affected and can be used to reproduce the problem.

Thank you for your response.  I am going to close this bug report with the 
assumption that this has been fixed upstream during the past 20 years.  But if 
anyone is still experiencing this problem, please feel free to reopen the bug 
report.

-- 
Soren Stoutner
[email protected]

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to