[GH-ISSUE #724] [Feature] Disable store failed deliveries status mail #1068

Open
opened 2026-03-14 11:38:21 +03:00 by kerem · 6 comments
Owner

Originally created by @djspacedevil on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/724

Hello,

please add the possibility to disable the information mail for "Store Failed Deliveries".
The function for the storage and resend is good. But i dont need always a notification for every email.

BR

Originally created by @djspacedevil on GitHub (Apr 1, 2025). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/724 Hello, please add the possibility to disable the information mail for "Store Failed Deliveries". The function for the storage and resend is good. But i dont need always a notification for every email. BR
Author
Owner

@djspacedevil commented on GitHub (Jun 26, 2025):

Hello,

When i enable the "Greylisting" Spam Protection on my Plesk Server, it will block the first try, with the delay message.
The sec try, around 5 minutes later, this works.

For the context:
https://www.danami.com/clients/knowledgebase/178/How-can-I-fix-the-error-milter-reject-DATA-451-4.7.1-Service-unavailable---try-again-later.html

So yes, the feature is good, but i dont need always the mail "New Failed Delivery"

BR,
Sven

<!-- gh-comment-id:3009752504 --> @djspacedevil commented on GitHub (Jun 26, 2025): Hello, When i enable the "Greylisting" Spam Protection on my Plesk Server, it will block the first try, with the delay message. The sec try, around 5 minutes later, this works. For the context: https://www.danami.com/clients/knowledgebase/178/How-can-I-fix-the-error-milter-reject-DATA-451-4.7.1-Service-unavailable---try-again-later.html So yes, the feature is good, but i dont need always the mail "New Failed Delivery" BR, Sven
Author
Owner

@RokeJulianLockhart commented on GitHub (Sep 1, 2025):

@djspacedevil, why would you not want it? Do you receive that much spam?

<!-- gh-comment-id:3242983173 --> @RokeJulianLockhart commented on GitHub (Sep 1, 2025): @djspacedevil, why would you not want it? Do you receive *that* much spam?
Author
Owner

@djspacedevil commented on GitHub (Sep 9, 2025):

Yes that’s right. I get first this mail, 1-10 times for one email. And after x times I get the right email.

So I don’t need the notification. Only the option, the resend when addy can’t deliver the mail.

The interesting thing is, I received the notification mail on the same mail account. It’s a bit weird that the original mail came later… after the x delivery failed emails.

<!-- gh-comment-id:3269937143 --> @djspacedevil commented on GitHub (Sep 9, 2025): Yes that’s right. I get first this mail, 1-10 times for one email. And after x times I get the right email. So I don’t need the notification. Only the option, the resend when addy can’t deliver the mail. The interesting thing is, I received the notification mail on the same mail account. It’s a bit weird that the original mail came later… after the x delivery failed emails.
Author
Owner

@qiujun8023 commented on GitHub (Sep 18, 2025):

I’m experiencing a similar issue. I set up some rules in rule to block certain sender email addresses. While the spam emails themselves are successfully blocked, I still keep receiving the “New failed delivery on addy.io” notifications whenever those blocked addresses attempt to send spam.

<!-- gh-comment-id:3305104633 --> @qiujun8023 commented on GitHub (Sep 18, 2025): I’m experiencing a similar issue. I set up some rules in rule to block certain sender email addresses. While the spam emails themselves are successfully blocked, I still keep receiving the “New failed delivery on addy.io” notifications whenever those blocked addresses attempt to send spam.
Author
Owner

@willbrowningme commented on GitHub (Sep 18, 2025):

@qiujun8023 does the failed delivery email say it has been quarantined by addy.io?

<!-- gh-comment-id:3307897013 --> @willbrowningme commented on GitHub (Sep 18, 2025): @qiujun8023 does the failed delivery email say it has been quarantined by addy.io?
Author
Owner

@qiujun8023 commented on GitHub (Sep 19, 2025):

version: v1.3.5

rules.conditions

[
    {
        "type": "sender",
        "match": "is exactly",
        "values": [
            "xxxxx@xxxx.com",
            "xxxxx@xxxx.com",
            "xxxxx@xxxx.com"
        ]
    }
]

rules.actions

[
    {
        "type": "block",
        "value": true
    }
]

Failed Deliveries Code: App\Mail\ForwardEmail has been attempted too many times.

<!-- gh-comment-id:3310182155 --> @qiujun8023 commented on GitHub (Sep 19, 2025): version: v1.3.5 rules.conditions ```json [ { "type": "sender", "match": "is exactly", "values": [ "xxxxx@xxxx.com", "xxxxx@xxxx.com", "xxxxx@xxxx.com" ] } ] ``` rules.actions ```json [ { "type": "block", "value": true } ] ``` Failed Deliveries Code: App\Mail\ForwardEmail has been attempted too many times.
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#1068
No description provided.