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

Reverse Alias Replacement feature is not replacing reverse alias in CC Email Reply #1325

Closed
1 task done
LazyGeniusMan opened this issue Sep 30, 2022 · 5 comments
Closed
1 task done

Comments

@LazyGeniusMan
Copy link

LazyGeniusMan commented Sep 30, 2022

Prerequisites

  • I have searched open and closed issues to make sure that the bug has not yet been reported.

Bug report

Describe the bug
Reverse Alias Replacement feature is not replacing reverse alias in CC Email, it's work as expected in To email.

Steps to reproduce

  1. Send email to an alias and add other email as CC.
  2. Open email in alias's mailbox and click "Reply All" so that it will also send reply to CC email account.
  3. Reply the email.
  4. Open the reply in CC email account.
  5. Expand the reply so that is shows original email that's being replied.
  6. It should show On {date}, {name} <{email reverse alias}> wrote: (the reverse alias is being used instead of original email

notes: If the reply is open from To email account, it's using original sender email as expected

Expected behavior
CC Email have reverse alias replaced in reply section

Screenshots
To Email (work as expected)
image

CC Email (not work)
image

Environment (If applicable):

  • OS: Windows
  • Browser: Firefox
  • Version 105

Additional context

@nguyenkims
Copy link
Contributor

@LazyGeniusMan thanks for reporting. Can you give us the steps to reproduce this issue please?

@LazyGeniusMan
Copy link
Author

@LazyGeniusMan thanks for reporting. Can you give us the steps to reproduce this issue please?

Added to post

@nguyenkims
Copy link
Contributor

@LazyGeniusMan thanks. I've managed to reproduce the issue. We've created a PR that should fix this and it should be deployed in the next version.

@nguyenkims
Copy link
Contributor

@LazyGeniusMan the fix has been deployed, please let me know if the issue still happens.

@LazyGeniusMan
Copy link
Author

@LazyGeniusMan the fix has been deployed, please let me know if the issue still happens.

So far looks good. Thank you. I'll close this.

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

2 participants