Well, if we look at the history of mailetcontainer.xml
https://github.com/apache/james-project/commits/master/server/app/src/main/resources/mailetcontainer.xml
it was added, not properly tested (likely cause the test framework
doesn't support the testing of the config files), fixed and finaly
commented out. Unfortunately the 3.4 branch was commited on 05 Sept 2019
- but the fix was commited into the master branch on 18 Nov 2019 - about
2 months later, wich makes the 3.4 tag kind of broken as no one tried to
start it in it's default config before the final commit (wich is kind of
reasonable as you should check the configs before initial start up).
Sorry, didn't knew that as I just tried compiling but not actual
starting of james 3.4 so I wasn't aware of this screw up. So, according
to the current master branch the prefered way is to just comment it out.
Matt
Am 04.03.2020 um 15:31 schrieb [email protected]:
Hi Matt et al
I may have pinpointed my issue by restarting methodically from scratch.
saw an alternative fix at
https://stackoverflow.com/questions/58493087/apache-james-spring-distribution-not-starting
ie, not commenting out the WithPriority mailet as I did, rather just changing its
<value> tag to <priority>
James starts and that feels like a better fix, but again, no test mail gets
delivered.
Leaving this for another day now :-)
--
David Matthews
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
