[
https://issues.apache.org/jira/browse/JAMES-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-4059.
---------------------------------
Resolution: Fixed
PR solved the issue
> MailetContainerModule should not do a strict check on RemoveMimeHeader with
> bcc name param
> ------------------------------------------------------------------------------------------
>
> Key: JAMES-4059
> URL: https://issues.apache.org/jira/browse/JAMES-4059
> Project: James Server
> Issue Type: Improvement
> Affects Versions: 3.8.3
> Reporter: René Cordier
> Priority: Minor
> Fix For: 3.9.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> By trying to add an other mime header to remove alongside the bcc name
> parameter in RemoveMimeHeader mailet in mailetcontainer.xml, then James fails
> to start correctly.
> It appears that MailetContainerModule is checking that there is a
> RemoveMimeHeader mailet present in the pipeline with a name param strictly
> equal to bcc, or it fails to start. However, name param allows multiple
> hearders to be removed, so technically the syntax to add other headers is not
> wrong, you still remove bcc logically. It's not normal.
> A quick win on this would be to relax the check and just verify that the name
> param contains bcc, instead of strictly equal.
> On an other work it could be good as well to add a jvm system property to
> allow to disable mailet container checks, it could be useful for people that
> do not wish to be constrained by such strict rules.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
