[GH-ISSUE #585] Failed delivery recursion #987

New issue

Closed

opened 2026-03-14 11:22:47 +03:00 by kerem · 1 comment

kerem commented

2026-03-14 11:22:47 +03:00

Owner

Originally created by @Iizuki on GitHub (Jan 23, 2024).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/585

I just received a notification mail about a failed delivery (from the official addy.io instance). I went to check it and saw this:

The bottom entry is a real delivery fail, and in so far as I can tell, all the rest are delivery fail notifications about the previous delivery fail notification which failed to deliver, until one finally got through.

The alias in question is not using my default recipient. It has a single other recipient set.

So what likely transpired, was that the particular recipient was out of service for a moment, and Addy just kept spamming it about failed deliveries.

I feel like there should be a bit more logic in where to send the failed delivery notice. It's not very fruitful to send it to the address which just a moment ago failed to receive mail. I would expect the failure notification to be sent to my default recipient, and the settings page gives this impression as well.

This is your account's default recipient email address, it is used for all general email notifications.

Although if it's my default recipient failing to receive mail, then it probably should be sent to some other recipient.

Originally created by @Iizuki on GitHub (Jan 23, 2024). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/585 I just received a notification mail about a failed delivery (from the official addy.io instance). I went to check it and saw this: ![Addy_failed_deliveries](https://github.com/anonaddy/anonaddy/assets/36295229/8a1e17a2-ac9e-4b3e-abfe-ff49e9116bd2) The bottom entry is a real delivery fail, and in so far as I can tell, all the rest are delivery fail notifications about the previous delivery fail notification which failed to deliver, until one finally got through. The alias in question is not using my default recipient. It has a single other recipient set. So what likely transpired, was that the particular recipient was out of service for a moment, and Addy just kept spamming it about failed deliveries. I feel like there should be a bit more logic in where to send the failed delivery notice. It's not very fruitful to send it to the address which just a moment ago failed to receive mail. _I would expect the failure notification to be sent to my default recipient,_ and the settings page gives this impression as well. ```text This is your account's default recipient email address, it is used for all general email notifications. ``` Although if it's my default recipient failing to receive mail, then it probably should be sent to some other recipient.

kerem closed this issue

2026-03-14 11:22:52 +03:00

kerem commented

2026-03-14 11:22:58 +03:00

Author

Owner

@willbrowningme commented on GitHub (Jan 23, 2024):

Thanks, it looks like this was caused because Postfix restarted itself on the mail2.anonaddy.me mail server and then failed to start up again correctly which is why those errors were shown, incoming messages were deferred and should have been automatically retried by the senders.

This was resolved earlier today and messages should be coming through as normal.

The recursion of saving the failed deliveries was indeed a bug that I have now fixed.

@willbrowningme commented on GitHub (Jan 23, 2024): Thanks, it looks like this was caused because Postfix restarted itself on the mail2.anonaddy.me mail server and then failed to start up again correctly which is why those errors were shown, incoming messages were deferred and should have been automatically retried by the senders. This was resolved earlier today and messages should be coming through as normal. The recursion of saving the failed deliveries was indeed a bug that I have now fixed.

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#987

No description provided.

Rows
Columns