I found the root cause of the logging for me... James 3.3 & 3.4 is still using log4j (version 1) that's EOL in 2015 [1] which is really broken with Java 9+ [2]. I'm using JDK 11 :( I'll have to replace the log4j (v1) jar(s) with log4j2 add see if it works.
[1] http://logging.apache.org/log4j/1.2/ [2] https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 On Wed, Mar 18, 2020 at 4:36 AM <m...@dmatthews.org.invalid> wrote: > Hi Jerry > > Thanks for that. I'm actually using 3.3.0, but I put your log4j.properties > in conf pretty much as is. And now I see log files other than > james.server.log actually starting to accumulate content. > > Better still this is at least very close to solving my gripe about not > seeing the response of a remote MX when sending a message. In the formerly > empty mailetcontainer.log I see > > DEBUG 11:04:47,426 | > org.apache.james.transport.mailets.remote.delivery.MailDelivrerToHost | > Mail (Mail1584529471843-0f9c6aa4-2919-47e1-bd7d-c446516ebb49- > to-dmatthews.org) sent successfully to a.mx.dmatthews.org. at > 213.138.100.30 from xx...@caudwell.org.uk for [x...@dmatthews.org] > > That looks like james' assessment of the remote MX response rather than > the actual raw response, but it's a good deal better than nothing. Also I > now know exactly where to look if I really want to see the remote response > as is. > > I'll add your log4j.properties to my james 3.3.0 write up and credit you > for it :-) > > > >Tommy, I hit this problem as well. Turns out that all the logs were > >restructured in 3.4, and the log4j file was not updated accordingly. > >I've updated mine and also added several more log points. This one > >works for me. Replace your /conf/log4j.properties file with this one, > >and play around with it: > > -- > David Matthews > m...@dmatthews.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > >
