mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 14:15:53 +03:00
[GH-ISSUE #780] [BUG] Cannot use anonaddy alias to sign up to mailing list as cannot respond to confirmation request. #536
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#536
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 @DavidPesticcio on GitHub (Oct 20, 2025).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/780
When responding to a specific return address to confirm the request to join the mailing list, all I get is a message sent to myself?
When subscribing via: https://oss-security.openwall.org/subscribe
A response is sent to the subscribing email address requesting a confirmation response email to a specific email address.
e.g.
When clicking the send link for the approrpiate alias at https://app.addy.io/aliases the above format is converted to an anonaddy reply address which results in;
Which results in an email being sent to the anonaddy alias instead of the intended recipient. Therefore preventing the ability to confirm the request to join the mailing list.
Presumably the issue is with the return email address using a similar format to anonaddy but the wrapping and unwrapping of the address is not working as expected. 🙁
@willbrowningme commented on GitHub (Oct 20, 2025):
That sounds like you are sending from an email that isn't listed as a verified recipient on your addy.io account.
https://addy.io/faq/#im-trying-to-reply-send-from-an-alias-but-the-email-keeps-coming-back-to-me-whats-wrong
If you believe it is a verified recipient then please send me an email with specific details of the alias so that I can check the logs.
@DavidPesticcio commented on GitHub (Oct 21, 2025):
This issue was resolved by @willbrowningme to update the validation method in relation to the code snippet below;
Many thanks Will, much appreciated. 👍