[GH-ISSUE #479] Add option to 'From' be the true sender #916

Closed
opened 2026-03-14 11:08:06 +03:00 by kerem · 3 comments
Owner

Originally created by @joaonunovalente on GitHub (Jul 11, 2023).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/479

Right now, we have the option to the 'From' header to be:

Would be nice that we could also have the option:

That would be easier to know who is the email from and would add the possibility to answer directly to it, using our email.

I know the last reason ignores the main purpose of anonaddy, but still.

Originally created by @joaonunovalente on GitHub (Jul 11, 2023). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/479 Right now, we have the option to the 'From' header to be: - alias@username.anonaddy.com - alias+sender=example.com@username.anonaddy.com Would be nice that we could also have the option: - sender@example.com That would be easier to know who is the email from and would add the possibility to answer directly to it, using our email. I know the last reason ignores the main purpose of anonaddy, but still.
kerem closed this issue 2026-03-14 11:08:11 +03:00
Author
Owner

@willbrowningme commented on GitHub (Jul 12, 2023):

It is not possible to have the original sender as the From: header because AnonAddy forwards the messages on as entirely new emails and this would cause all authentication checks to fail and messages to be rejected.

<!-- gh-comment-id:1632171051 --> @willbrowningme commented on GitHub (Jul 12, 2023): It is not possible to have the original sender as the `From:` header because AnonAddy forwards the messages on as entirely new emails and this would cause all authentication checks to fail and messages to be rejected.
Author
Owner

@joaonunovalente commented on GitHub (Jul 12, 2023):

Yeah... That actually makes sense!

Another sugestion then.

Would it be possible to have the To: be another email instead of the alias?

For instance:

From: sender@username.anonaddy.com
Reply-to: sender+example=sender.com@username.anonaddy.com
To: sender@username.anonaddy.com

Could the To: email be our own email?

<!-- gh-comment-id:1632726116 --> @joaonunovalente commented on GitHub (Jul 12, 2023): Yeah... That actually makes sense! Another sugestion then. Would it be possible to have the `To:` be another email instead of the alias? For instance: **From:** sender@username.anonaddy.com **Reply-to:** sender+example=sender.com@username.anonaddy.com **To:** sender@username.anonaddy.com Could the `To:` email be our own email?
Author
Owner

@willbrowningme commented on GitHub (Jul 12, 2023):

The To: could be your recipient's email e.g. you@gmail.com yes.

<!-- gh-comment-id:1632797020 --> @willbrowningme commented on GitHub (Jul 12, 2023): The `To:` could be your recipient's email e.g. `you@gmail.com` yes.
Sign in to join this conversation.
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/anonaddy#916
No description provided.