You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2023/12/18 07:03:00 UTC
[jira] [Closed] (JAMES-3967) Improve loop handling
[ https://issues.apache.org/jira/browse/JAMES-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-3967.
---------------------------------
Fix Version/s: 3.9.0
Resolution: Fixed
> Improve loop handling
> ---------------------
>
> Key: JAMES-3967
> URL: https://issues.apache.org/jira/browse/JAMES-3967
> Project: James Server
> Issue Type: Improvement
> Components: configuration, Mailet Contributions
> Affects Versions: 3.8.0
> Reporter: Benoit Tellier
> Priority: Major
> Fix For: 3.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> For a reason too long to explain here (but one can check attachment), and due to some legacy in our mail infra, we ended up with some emails reaching relay limit.
> With default configuration those emails are dropped. And Lost. Which is not acceptable.
> I attend to:
> - 1. Add clear ERROR logs when relay limit is exceeded. That's an important information.
> - 2. And modify default configuration in order to systematically store emails in a dedicated repository (No LOSS)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org