[GH-ISSUE #441] [Feature request] Fallback forwarding address #890

Open
opened 2026-03-14 11:02:20 +03:00 by kerem · 8 comments
Owner

Originally created by @pierreis on GitHub (Apr 10, 2023).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/441

Problem
Currently, if a message delivery fails, it is not possible to recover it. This tends to be problematic when transferring messages to iCloud addresses, that seems to reject emails quite easily due to the sensitive spam filter, presumably.

Solution
The ability to set a fallback address. If delivery fails to the primary address, delivery is attempted to the fallback address before being marked as failed.

Originally created by @pierreis on GitHub (Apr 10, 2023). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/441 **Problem** Currently, if a message delivery fails, it is not possible to recover it. This tends to be problematic when transferring messages to iCloud addresses, that seems to reject emails quite easily due to the sensitive spam filter, presumably. **Solution** The ability to set a fallback address. If delivery fails to the primary address, delivery is attempted to the fallback address before being marked as failed.
Author
Owner

@willbrowningme commented on GitHub (May 26, 2023):

Thanks, that's a good idea and definitely something I would like to add in the future.

For now though I recently added the ability to choose to temporarily store any failed deliveries so that they can be downloaded and viewed. You can enable this in your account settings.

<!-- gh-comment-id:1564048699 --> @willbrowningme commented on GitHub (May 26, 2023): Thanks, that's a good idea and definitely something I would like to add in the future. For now though I recently added the ability to choose to temporarily store any failed deliveries so that they can be downloaded and viewed. You can enable this in your account settings.
Author
Owner

@ririko5834 commented on GitHub (May 27, 2023):

good idea. I think that there could be an option to set catch-all email address for custom domains and usernames that you can set custom receipt where emails sent to unexisting, deleted or forgotten aliases will be resend if it is enabled.

<!-- gh-comment-id:1565351801 --> @ririko5834 commented on GitHub (May 27, 2023): good idea. I think that there could be an option to set catch-all email address for custom domains and usernames that you can set custom receipt where emails sent to unexisting, deleted or forgotten aliases will be resend if it is enabled.
Author
Owner

@anondev-sudo commented on GitHub (Jul 19, 2023):

Agree

<!-- gh-comment-id:1641860165 --> @anondev-sudo commented on GitHub (Jul 19, 2023): Agree
Author
Owner

@willbrowningme commented on GitHub (Jul 6, 2025):

I have just added the ability to resend failed deliveries and you can choose a different recipient(s) to resend to.

Go to the failed deliveries page and you will see "Resend" next to "Download" and "Delete".

Currently only available on "Forward" email types.

<!-- gh-comment-id:3042324988 --> @willbrowningme commented on GitHub (Jul 6, 2025): I have just added the ability to resend failed deliveries and you can choose a different recipient(s) to resend to. Go to the [failed deliveries](https://app.addy.io/failed-deliveries) page and you will see "Resend" next to "Download" and "Delete". Currently only available on "Forward" email types.
Author
Owner

@anondev-sudo commented on GitHub (Jul 7, 2025):

Where can I download this update to my selfhosted version? I don't see new release

<!-- gh-comment-id:3043878294 --> @anondev-sudo commented on GitHub (Jul 7, 2025): Where can I download this update to my selfhosted version? I don't see new release
Author
Owner

@willbrowningme commented on GitHub (Jul 7, 2025):

It's not available on self-hosted instances yet. It will be in the next release.

<!-- gh-comment-id:3043987535 --> @willbrowningme commented on GitHub (Jul 7, 2025): It's not available on self-hosted instances yet. It will be in the next release.
Author
Owner

@anondev-sudo commented on GitHub (Jul 29, 2025):

It still wasn't added in the latest release :/

<!-- gh-comment-id:3131162152 --> @anondev-sudo commented on GitHub (Jul 29, 2025): It still wasn't added in the latest release :/
Author
Owner

@willbrowningme commented on GitHub (Jul 29, 2025):

This is available in the latest https://github.com/anonaddy/anonaddy/releases/tag/v1.3.4.

<!-- gh-comment-id:3132729275 --> @willbrowningme commented on GitHub (Jul 29, 2025): This is available in the latest https://github.com/anonaddy/anonaddy/releases/tag/v1.3.4.
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#890
No description provided.