ProtonMail / ProtonMail/WebClients
Updated Name of Noreply Senders in Custom Folders
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 715
- PR merge metrics
- No merged PRs in 30d
Description
When using ProtonMail, I have observed that the names of noreply senders get updated when emails are received in a custom folder created through filtering. This behavior has caused confusion in my use case, particularly during recruitment processes where I receive emails from HR personnel through third-party services. The altered sender names make it difficult to identify and organize important communications.
Is this behavior intended to be the default?
Steps to Reproduce
- Create a custom folder in ProtonMail.
- Set up a filter to direct emails from noreply addresses to this custom folder.
- Observe the sender names in the custom folder over time.
Expected Behavior
The sender names of noreply emails should remain consistent and not be updated upon being received in a custom folder.
Actual Behavior:
The sender names of noreply emails get updated when they are received in the custom folder, leading to potential confusion and mismanagement of emails, especially in professional contexts.
Environment
ProtonMail Version: 5.0.41.9 β
Browser: Microsoft Edge (Webview), Chrome
Operating System: Windows 11
Mobile: Android (using the ProtonMail app)
Additional Information:
This behavior has been particularly detrimental during recruitment processes where I rely on consistent sender information to track communications from HR personnel using third-party services.
Thank you for your assistance in resolving this issue
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named in the issue. Start by reproducing the behavior in the web client with a filtered custom folder, then compare the sender name in the original mailbox and custom folder over time. Done means noreply sender names remain consistent after delivery to the custom folder, with coverage for the reported reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100