<<< Date Index >>>     <<< Thread Index >>>

bug#1716: marked as done (mutt-1.5.5.1i: reply flag is not set when reply-mail was postponed)



Your message dated Sun, 4 Jan 2004 11:20:14 +0100
with message-id <20040104102013.GF9799@xxxxxxxxxxxxxxxxxxxxxxxxxx>
and subject line bug#1716: mutt-1.5.5.1i: reply flag is not set when reply-mail 
was postponed
has caused the attached bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Herr der Kaefer
(administrator, GUUG bugs database)

--------------------------------------
Received: (at submit) by bugs.guug.de; 23 Nov 2003 21:53:14 +0000
>From wilde@xxxxxxxxxxx Sun Nov 23 22:53:12 2003
Received: from mail1.kontent.de ([81.88.34.36] ident=30)
        by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian))
        id 1AO2AK-00019y-00
        for <submit@xxxxxxxxxxxx>; Sun, 23 Nov 2003 22:53:12 +0100
Received: from kenny.sha-bang.de (xdsld099.osnanet.de [212.95.103.99])
        by Mail1.KONTENT.De (Postfix) with ESMTP
        id 260082123E8; Sun, 23 Nov 2003 22:55:58 +0100 (CET)
Received: from wilde by kenny.sha-bang.de with local (Kenny MUA v.0307044.20)
        ID 1AO2Cm-0005FU-W2; Sun, 23 Nov 2003 22:55:44 +0100
From: wilde@xxxxxxxxxxx
Subject: mutt-1.5.5.1i: reply flag is not set when reply-mail was postponed
To: submit@xxxxxxxxxxxx
Message-Id: <E1AO2Cm-0005FU-W2@xxxxxxxxxxxxxxxxx>
Date: Sun, 23 Nov 2003 22:55:44 +0100
X-Spam-Status: No, hits=-4.3 required=5.0
        tests=BAYES_01,NO_REAL_NAME
        version=2.55
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)

Package: mutt
Version: mutt-1.5.5.1-1
Severity: normal

-- Please type your report below this line

When a reply to an OpenPGP encrypted mail is postponed and then later
send, after sending it there is no r-Flag set on the original Mail.

This I would consider a bug.  The same procedure with an unencrypted
original works as expected: after sending the postponed answer the
original gets marked with the r-Flag.


The same behavior occures when the originale Mail is unencrypted, but
subsequently moved to another mailbox.

I understand that this would be problematic to fix for _every_
mailbox would have to be scanned for the referenced MsgID.  But I
think it shoul be possible to configure something like:

postponed-reply-check= [ none | aktive-mailbox | mbox1,mbox2, ... mboxN ]


cheers
sascha

-- System Information
System Version: Linux kenny 2.4.22 #2 Sam Nov 15 19:45:02 CET 2003 i686 unknown

-- Build environment information

This _is_ the actual building environement! (sw)

- gcc version information
gcc
Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/specs
Konfiguriert mit: ../gcc-3.3.2/configure 
Thread model: posix
gcc-Version 3.3.2

- CFLAGS
-Wall -pedantic -march=athlon -O3

-- Mutt Version Information

Mutt 1.5.5.1i (2003-11-05)
Copyright (C) 1996-2002 Michael R. Elkins und andere.
Mutt übernimmt KEINERLEI GEWÄHRLEISTUNG. Starten Sie `mutt -vv', um
weitere Details darüber zu erfahren. Mutt ist freie Software. 
Sie können es unter bestimmten Bedingungen weitergeben; starten Sie
`mutt -vv' für weitere Details.

System: Linux 2.4.22 (i686) [using ncurses 5.0]
Einstellungen bei der Compilierung:
-DOMAIN
-DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  
+USE_FCNTL  -USE_FLOCK
-USE_POP  -USE_IMAP  -USE_GSS  -USE_SSL  -USE_SASL  -USE_SASL2  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  -CRYPT_BACKEND_GPGME  
-BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  -LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET  
+HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  -HAVE_LIBIDN  +HAVE_GETSID  -HAVE_GETADDRINFO  
ISPELL="/usr/bin/ispell"
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/spool/mail"
PKGDATADIR="/usr/local/share/mutt"
SYSCONFDIR="/usr/local/etc"
EXECSHELL="/bin/sh"
-MIXMASTER
Um die Entwickler zu kontaktieren, schicken Sie bitte
eine Nachricht (in englisch) an <mutt-dev@xxxxxxxx>.
Um einen Bug zu melden, verwenden Sie bitte das Programm flea(1).


--- Begin /usr/local/etc/Muttrc
ignore "from " received content- mime-version status x-status message-id
ignore sender references return-path lines
macro index \eb '/~b ' 'search in message bodies'
macro index \cb |urlview\n 'call urlview to extract URLs out of a message'
macro pager \cb |urlview\n 'call urlview to extract URLs out of a message'
macro generic <f1> "!less /usr/local/doc/mutt/manual.txt\n" "Show Mutt 
documentation"
macro index   <f1> "!less /usr/local/doc/mutt/manual.txt\n" "Show Mutt 
documentation"
macro pager   <f1> "!less /usr/local/doc/mutt/manual.txt\n" "Show Mutt 
documentation"
--- End /usr/local/etc/Muttrc


---------------------------------------
Received: (at 1716-done) by bugs.guug.de; 4 Jan 2004 10:17:41 +0000
>From roessler+bounce@xxxxxxxxxxxxxxxxxx Sun Jan 04 11:17:37 2004
Received: from does-not-exist.info ([217.160.221.198] 
helo=kamino.does-not-exist.org)
        by trithemius.gnupg.org with esmtp (Exim 3.35 #1 (Debian))
        id 1Ad5KD-0004SR-00
        for <1716-done@xxxxxxxxxxxx>; Sun, 04 Jan 2004 11:17:37 +0100
Received: from voyager.does-not-exist.org (p3E9B9DFA.dip0.t-ipconnect.de 
[62.155.157.250])
        (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
        (No client certificate requested)
        by kamino.does-not-exist.org (Postfix) with ESMTP
        id E4C693140D5; Sun,  4 Jan 2004 11:20:16 +0100 (CET)
Received: by voyager.does-not-exist.org (Postfix, from userid 500)
        id 3935A8076; Sun,  4 Jan 2004 11:20:14 +0100 (CET)
Date: Sun, 4 Jan 2004 11:20:14 +0100
From: Thomas Roessler <roessler@xxxxxxxxxxxxxxxxxx>
To: 1716-done@xxxxxxxxxxxx, Sascha Wilde <wilde@xxxxxxxxxxx>
Subject: Re: bug#1716: mutt-1.5.5.1i: reply flag is not set when reply-mail was 
postponed
Message-ID: <20040104102013.GF9799@xxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <E1AO2Cm-0005FU-W2@xxxxxxxxxxxxxxxxx> 
<20031128145224.GB20489@xxxxxxx> <20031128221833.GC4038@kenny> 
<20031202193513.GA2070@xxxxxxx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031202193513.GA2070@xxxxxxx>
User-Agent: Mutt/1.5.5.1i
X-Spam-Status: No, hits=-109.0 required=4.0
        tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
              REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_MUTT,
              USER_IN_WHITELIST
        autolearn=ham version=2.55
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)

This patch has made it to the CVS on 2003-12-03.  Closing the bug
report.


On 2003-12-02 20:35:13 +0100, Alain Bench wrote:
> From: Alain Bench <veronatif@xxxxxxx>
> To: 1716@xxxxxxxxxxxx
> Cc: Sascha Wilde <wilde@xxxxxxxxxxx>
> Date: Tue, 2 Dec 2003 20:35:13 +0100 (CET)
> Subject: bug#1716: mutt-1.5.5.1i: reply flag is not set when reply-mail was 
> postponed
> Reply-To: Alain Bench <veronatif@xxxxxxx>, 1716@xxxxxxxxxxxx
> Mail-Followup-To: 1716@xxxxxxxxxxxx, Sascha Wilde <wilde@xxxxxxxxxxx>
> X-Spam-Level: 
> 
>  On Friday, November 28, 2003 at 11:18:33 PM +0100, Sascha Wilde wrote:
> 
> > I hope following this step by step will reproduce the bug for you...
> 
>     Yes, thanks. Also 1.4 and even 1.2.5 had the bug. Triggering it can
> be done with two steps only:
> 
>  - 1) To be in the pager.
>  - 2) Recall the reply thru <mail> and "Recall postponed message?" yes.
> 
>     This suffices for the original mail not being /answered/ after
> sending reply. Any PGP status, any message displayed in pager. Step 2
> done in index works OK, <recall-message> from pager (or index) works OK.
> 
>     The attached little patch fixes the bug, but needs more testing
> against side effects (I had one unexplained and unreproducible failure
> while experimenting: Hopefully just a false move...).
> 
> 
>     [flagging in another mailbox]
> > Anyway another (stupid?) idea: when sending an reply and the
> > referenced MID can't be found in the aktive mailbox, write the MID
> > into an special file. Later, when opening an other mailbox, that file
> > could be used (maybe via the folder-hook) to look in the mailbox for
> > the unresolved original messages and flag it, when found.
> 
>     Not stupid, thanks for the idea.
> 
> 
> Bye!  Alain.
> -- 
> set honor_followup_to=yes in muttrc is the default value, and makes your
> list replies go where the original author wanted them to go: Only to the
> list, or with a private copy.

> Experiment to fix r-flagging at sending postponed reply, when recalling
> it from pager thru <mail> and "Recall postponed message? ([yes]/no):"
> prompt. See bug #1716. AB.
> 
> diff -prud mutt-1.4.orig/pager.c mutt-1.4/pager.c
> --- mutt-1.4.orig/pager.c     Sun Jan 13 09:52:15 2002
> +++ mutt-1.4/pager.c  Sun Nov 30 22:24:21 2003
> @@ -2327,7 +2327,7 @@ mutt_pager (const char *banner, const ch
>        case OP_MAIL:
>       CHECK_MODE(IsHeader (extra) && !IsAttach (extra));
>          CHECK_ATTACH;      
> -     ci_send_message (0, NULL, NULL, NULL, NULL);
> +     ci_send_message (0, NULL, NULL, extra->ctx, extra->hdr);
>       redraw = REDRAW_FULL;
>       break;
>  
> --- PATCHES   Tue Nov  6 19:59:33 2001
> +++ PATCHES   Tue Nov  6 19:59:42 2001
> @@ -1,0 +1 @@
> +patch-1.4.ab.mail_recall_from_pager.1


-- 
Thomas Roessler                       <roessler@xxxxxxxxxxxxxxxxxx>