mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 14:15:53 +03:00
[GH-ISSUE #8] Show original "from" name #56
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#56
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @erik-h on GitHub (Nov 29, 2019).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/8
First of all I'd like to say that I'm loving AnonAddy so far, so thank you!
Would you support the idea of adding an option in the settings to set the "From" name of forwarded emails to the name of the original sender? After sending a couple of test emails I'm noticing it's hard to differentiate between senders forwarded through AnonAddy, since they're all from the same address.
@erik-h commented on GitHub (Nov 29, 2019):
Ahh sorry, I realized that the reason I'm seeing "AnonAddy" as the "from" for every email is because I added mailer@anonaddy.com to my contacts. When I forwarded to another email account that doesn't have AnonAddy in its contacts I realized that the "from" name is already set to the real sender.
@erik-h commented on GitHub (Nov 29, 2019):
FYI for anyone using ProtonMail: to get the result I wanted (adding AnonAddy to my contacts while still showing the original sender's name in the "from" field) I had to manually remove the "Name" field from my contacts entry. When I originally hit the "add to contacts" button it had set the Name to AnonAddy.
@anonaddy commented on GitHub (Nov 29, 2019):
Thanks, yes you're right AnonAddy does currently set the sender's from name and from address in the From: header but obviously it still has to be sent from an AnonAddy domain e.g. anonaddy.me otherwise it would end up in spam for forging the From: header.