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

Updated Name of Noreply Senders in Custom Folders #399

Open
dotMavriQ opened this issue Jul 12, 2024 · 0 comments
Open

Updated Name of Noreply Senders in Custom Folders #399

dotMavriQ opened this issue Jul 12, 2024 · 0 comments

Comments

@dotMavriQ
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant