[Reportbug-maint] Bug#560369: reportbug thinks message isn't sent when mutt postpones

Sandro Tosi morph at debian.org
Thu Dec 10 21:12:39 UTC 2009

Hi Gerfried,
thanks for your report.

On Thu, Dec 10, 2009 at 19:57, Gerfried Fuchs <rhonda at debian.at> wrote:
>  First of all, sorry if this is a duplicate. Though, that is the reason
> why I just postponed the bugreport in the first place instead of sending
> it along.

just one came

> reportbug seems to think that it hasn't been sent and gives
> this message:
> #v+
> Mutt users should be aware it is mandatory to edit the draft before sending.
> Report has not been sent yet; what do you want to do now? [E|q|?]? ?
> E - (default) Edit the message.
> q - Quit reportbug; will save the draft for future use.
> ? - Display this help.
> Report has not been sent yet; what do you want to do now? [E|q|?]? q
> #v-

We check the return code: if it's 0, the MUA did it's job correctly,
if != 0 then there was an error, and so we issue the message above.

>  Not sure what exit status mutt gives on postponing a message but I
> guess it should be taken as a positive response too.

for sure it returns a != 0 value.

> I'm also not sure
> if mutt is actually producing different return codes - and if it is
> proper to return 1 on postponed messages; maybe reassigning it to mutt
> is the correct thing to do here.

What you should do is file a bug against mutt asking for
clarifications and then block this bug with the one on mutt.

We can't lead this task, but we'd be welcome to adjust reportbug
behavior once there are some more info.

Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

More information about the Reportbug-maint mailing list