[GH-ISSUE #166] Forwarding email received on AnonAddy address to someone behind another AnonAddy address fails #729

Closed
opened 2026-03-14 10:22:44 +03:00 by kerem · 1 comment
Owner

Originally created by @xanoni on GitHub (Jun 4, 2021).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/166

Originally created by @xanoni on GitHub (Jun 4, 2021). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/166
kerem closed this issue 2026-03-14 10:22:49 +03:00
Author
Owner

@willbrowningme commented on GitHub (Jun 7, 2021):

That's because the forwarded message has an "In-Reply-To:" header which AnonAddy checks for.

I've just tested this myself and both work, forwarding a recieved email and also just sending a fresh one from scratch.

In both scenarios I received the email as expected.

Could you email me with more details and the actual aliases used if you are still having this issue?

<!-- gh-comment-id:855919449 --> @willbrowningme commented on GitHub (Jun 7, 2021): That's because the forwarded message has an "In-Reply-To:" header which AnonAddy checks for. I've just tested this myself and both work, forwarding a recieved email and also just sending a fresh one from scratch. In both scenarios I received the email as expected. Could you email me with more details and the actual aliases used if you are still having this issue?
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#729
No description provided.