Oh! :-( Thank Garry for responding... Well this issue is not a
showstopper, just a false flag then, I guess, that I have been chasing.
Probably should be flagged for debugging/fixing of the code or flagged
for updating the documentation so others won't chase this. BTW I was
able to hack the
Yeah, the extra logs seem like a good idea, but details are either logged in
the james-server.log for out-of-the-box components, or wrapper.log for custom
code.
Sent from my iPhone
> On Jan 28, 2019, at 9:27 PM, Marc Chamberlin wrote:
>
> Thanks Simon for your thoughts, I tried making the
Hi Apache James community,
We, at Linagora had been working hard on the past few months on making
James a fully distributed email server.
This work had been achieved on top of the Guice product
'Cassandra-ElasticSearch-RabbitMQ'.
Our team did rewrite most of the mailbox event system,
Thanks Simon for your thoughts, I tried making the change as you
suggested but still no joy! You gave me a path to explore so I am
digging into log4j and trying to understand it better... And I am
seeing some warnings in the wrapper log file that look ominous so I am
digging in to those as
Hi Marc,
I had the same issue and found out they are using
"DailyRollingFileAppender". My fix was to use "DailyRollingFileAppender".
You can see the full file I am using here:
