[Users] [Bug 4352] New: Local mail fetching fail if mailbox file has an empty message

[noreply at thewildbeast.co.uk]

https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4352

            Bug ID: 4352
           Summary: Local mail fetching fail if mailbox file has an empty
                    message
           Product: Claws Mail
           Version: 3.17.3
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: blocker
          Priority: P3
         Component: Other
          Assignee: users at lists.claws-mail.org
          Reporter: gpaclog at free.fr

When local mailbox (located in /var/mail/) contains an empty message,
claws-mail fails in retrieving messages in that local mailbox file.

Only indication of failure is an error message in console (or
.xsession-errors), but no indication on GUI.

Error message :
(claws-mail:1297): Claws-Mail-WARNING **: 12:48:54.224: malformed mbox:
/home/xxx/.claws-mail/tmp/tmpmbox.0x1fa6c80: message 1 is empty

Issue seems to come from the test conducted in lines 222-230 from mbox.c (if no
lines in the message, then it stops).

Nota : RFC 822 is allowing such message without body : "A message consists of
header fields and, optionally, a body"

To be RFC compliant claws should load that empty message. 
Alternatively better behaviours could be to drop that empty message, or add a
blank line in its body to simulate a non-empty message, or add in its body some
kind of information string mentioning the message is empty.

This is a blocker in the sense that current behaviour is just preventing claws
to fetch mails while not informing the user of the issue.

Nota : when the issue appears, the only way to fix the problem is to open the
mailbox file in a text editor, find the empty message (= a line starting with
From, followed by only an empty line before another line starting by From), and
remove it. Then claws can fetch messages without complaining (this can be
painful depending of number of mails is that mailbox file !).

-- 
You are receiving this mail because:
You are the assignee for the bug.