On Tue, Mar 17, 2020 at 7:00 AM <m...@dmatthews.org.invalid> wrote:
> hi Duc > > >I know that takes you more effort to find the remote host server. But the > point is, James uses its mailet pipeline system, it's hard to wrap all > information in all pipeline into one line of log. > But each peace of information is provided by a specific mailet. > > I understand that James passes email through a series of mailet code > before the final outcome of deciding what should be done with the message. > However the information I want is the response from a remote server that > James has sent a message to. That surely must be potentially available at a > single point in James' mailet stream. > > The mailets you mention do sound like reasonable places to look though. > > >And I don't think your desire can be easy to implemented - from my little > knowledge about James :D > > Nah > > log.info(remoteSever.getResponse()); > > How hard can it be? Seriously, I think it's a missing feature that should > be implemented even if I have to do it myself :-) > > -- > David Matthews > m...@dmatthews.org > > > I too don't think it's hard to implement logging. From what I know of Java, I don't recall Java having port sharing like MS does. So if you enable the logging right at socket listener, you can see what comes in/out. It's has a very good use case where installing wireshark or equivalent is not feasible.
