Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message parsing error prevents importing of emails #450

Open
yu-tendo opened this issue Dec 21, 2023 · 1 comment
Open

Message parsing error prevents importing of emails #450

yu-tendo opened this issue Dec 21, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@yu-tendo
Copy link

yu-tendo commented Dec 21, 2023

Description of the problem

The email cannot be imported with the Proton Mail Bridge due to a parsing error of the message (body). When moving the message (with Thunderbird), one of the following error messages is printed:

  1. failed to import message: failed to import message: Imported message is empty (Code=36026, Status=0): known recovery message, possible duplication. (see attached example, issue-1.txt)
  2. failed to import message: failed to import message: Error while parsing message (Code=36026, Status=0) (see attached example, issue-2.txt and issue-2-1.txt)

Comment

I am not sure if it is possible to fix these issues, as it might be the case that the e-mails are simply faulty (i.e., the respective issue cannot be corrected automatically). However, identifying manually the faulty e-Mails while actually moving thousands of e-Mails is very time-consuming. Thus, I would expect that at least the email-moving process is not interrupted and the faulty emails are skipped. Assuming the bridge cannot handle the parsing issue, I suggest that a respective FAQ entry (or similar) is created covering an explanation of the issue and how to potentially manually fix this issue (otherwise users will keep opening new issues).

Version Information

Proton Mail Bridge v3.8.1 (br-187)
Thunderbird 115.6.0 (64-bit)
Microsoft Windows 10

File Attachments

issue-1.txt
issue-2.txt
issue-2-1.txt

@LBeernaertProton
Copy link
Collaborator

Thanks for the report. This seems to be an issue with the Proton API. We need to investigate.

Internally tracked as GODT-3180.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants