Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1171265 > unrolled thread
| Started by | Serge Cohen <serge.cohen@cnrs.fr> |
|---|---|
| First post | 2023-10-09 16:40 +0200 |
| Last post | 2023-10-09 16:40 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.debian.bugs.dist
Bug#1053724: offlineimap3: OfflineIMAP crashes on synchronisation of a 'Message-ID: <>' in header Serge Cohen <serge.cohen@cnrs.fr> - 2023-10-09 16:40 +0200
| From | Serge Cohen <serge.cohen@cnrs.fr> |
|---|---|
| Date | 2023-10-09 16:40 +0200 |
| Subject | Bug#1053724: offlineimap3: OfflineIMAP crashes on synchronisation of a 'Message-ID: <>' in header |
| Message-ID | <HmZAl-eEPg-11@gated-at.bofh.it> |
Package: offlineimap3
Version: 0.0~git20230519.c9f44ad+dfsg-1
Severity: important
X-Debbugs-Cc: serge.cohen@cnrs.fr
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Using OfflineIMAP as a solution to synchronise and secure a second copies of messages.
When a message contains a header line as
Message-ID: <>
This causes a crash of the message header parsing of OfflineIMAP :
ERROR: Copying message 66358 [acc: XXXXXX]
list index out of range
Thread 'Copy message from XXXXXX-remote:INBOX' terminated with exception:
Traceback (most recent call last):
File "/usr/lib/python3.9/email/_header_value_parser.py", line 2069, in get_msg_id
token, value = get_dot_atom_text(value)
File "/usr/lib/python3.9/email/_header_value_parser.py", line 1334, in get_dot_atom_text
raise errors.HeaderParseError("expected atom at a start of "
email.errors.HeaderParseError: expected atom at a start of dot-atom-text but found '>'
This crash also inhibit OfflineIMAP from synchronising any message which is later in the IMAP list.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Currently, the only workaround is to suppress such messages from the originating mailbox.
* What was the outcome of this action?
The message is not archived (indeed, even worse : it is completely deleted), but the synchronisation can go on
* What outcome did you expect instead?
Both that the message is synchronised (as any other message) and the process continue to synchronise all the rest of the mailbox.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 11.8
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-26-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages offlineimap3 depends on:
ii ca-certificates 20210119
ii python3 3.9.2-3
ii python3-distro 1.5.0-1
ii python3-imaplib2 2.57-5.2
offlineimap3 recommends no packages.
Versions of packages offlineimap3 suggests:
pn python3-gssapi <none>
-- no debconf information
Back to top | Article view | linux.debian.bugs.dist
csiph-web