You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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)
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
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:
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
The text was updated successfully, but these errors were encountered: