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

Problem list #27

Closed
exander77 opened this issue Apr 27, 2020 · 6 comments
Closed

Problem list #27

exander77 opened this issue Apr 27, 2020 · 6 comments
Labels
duplicate This issue or pull request already exists

Comments

@exander77
Copy link

exander77 commented Apr 27, 2020

These are the problems I have encountered so far after 14 days of using ProtonMail. I am losing track of what I have reported and how, so I would like to keep it in one place and mark it solved when it is solved. Support advised me that there is no public bug tracking and as most of these relates to Bridge or are somehow connected to Bridge, I would like to keep it here.

Receiving emails:

  1. Damages some emails by correctly not detecting headers and body, causing the part of headers to be encrypted as part of the body.
    Reported to [email protected]
  2. Damages signatures on emails, for example, S/MIME.
    Reported: Signed emails has broken signatures after ProtonMail mangles them #26
  3. Damages attachments encoded as quoted-printable replacing \r\n by \n in binary files.
    Reported: Replace MIME parser completely with some lite version for critical parts #18
  4. Ads Content-Disposition: inline to multipart data.
    Reported: Replace MIME parser completely with some lite version for critical parts #18
  5. Changes encoding to all parts to base64.
    Reported: Replace MIME parser completely with some lite version for critical parts #18
  6. Does not comply with RFC7505 and hijacks emails sent to a domain hosted on ProtonMail even if the MX records do not lead to ProtonMail and by that opens you to a few kinds of a man-in-the-middle attack.
    Reported to [email protected], [email protected]
  7. Corrupts emails which contains another email (like an undeliverable response), but incorrectly detecting headers and body and making part of the headers part of the body.
    Reported to [email protected]

Sending and importing emails from ProtonBridge:

  1. Damages signatures on emails, for example, S/MIME.
    Reported: Signed emails has broken signatures after ProtonMail mangles them #26
  2. Silently shreds any email moved into Sent folder where the From corresponds to the account email (complete loss of that email when moving from a different IMAP account, even the ProtonMail one).
    Reported: APPEND result when targetSeq.Len() == 0 #2
  3. Unable to import a large number of messages because of various parsing problems, namely:
  1. Ads Content-Disposition: attachment to multipart data.
    Reported: Replace MIME parser completely with some lite version for critical parts #18
  2. Fails to import mails over 26214400 bytes.
    Reported to [email protected]
  3. Randomly fails to return APPENDUID.
    Reported to [email protected]
  4. Operating with a large number of emails causes unrecoverable 120% CPU usage until the cache was cleared.
    Reported: High CPU usage when doing nothing #25
  5. Changes encoding to all parts to base64.
    Reported: Replace MIME parser completely with some lite version for critical parts #18

General:

  1. All Mail folder contains Trash and Spam which is non-standard and causes glitches in mail clients (like a complete profile failure).
    Reported to [email protected], [email protected]

Web UI:

  1. Cannot find emails by subject if it contains /, \ or ? symbols.
    Reported to [email protected]
  2. Cannot find emails by message-id.
    Reported to [email protected]
  3. When an email is moved into Sent folder, it shows message of success, but actually fails and messages stay in the original location.
    Maybe connected to this somehow as well: APPEND result when targetSeq.Len() == 0 #2
    Reported to [email protected]
  4. Reports any action as success even if it fails.
@horejsek
Copy link
Member

Thank you for all your reports. We will look into them. But please let's keep only one issue per issue so we can track all of them more easily (e.g. comments in one place). Thank you.

@horejsek horejsek added the duplicate This issue or pull request already exists label Apr 28, 2020
@horejsek
Copy link
Member

BTW also note this is repository for bridge only, so this is not place where to report web UI or general issues.

@exander77
Copy link
Author

exander77 commented Apr 28, 2020

@horejsek This not so much for you, as it is for me, to keep track, as I am losing track in bug reports I have sent.

Also, some bugs are connected, for example, Sent mail folder behaves strangely in the Bridge and Web UI as well. Same goes for All Mail folder.

@omicron-b
Copy link
Contributor

@exander77 you have a fork of Bridge, you can keep track there for yourself
such list in the official repo would confuse other reporters

@exander77
Copy link
Author

exander77 commented Apr 28, 2020

@omicron-b I hope that before that could possibly happen, all of those bugs will be solved for a long time.

@exander77
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants