Hi!
On 2011-11-11 23:43, Bron Gondwana wrote:
> Do you want to write up a patch for what you think is best? My first
> thought is for the frontend to log a backend to frontend linking
> record... unless you can push the backend SESSIONID back in the
> frontend response somehow.
I attached my pro
On 2011-11-11 23:43, Bron Gondwana wrote:
> Do you want to write up a patch for what you think is best? My first
> thought is for the frontend to log a backend to frontend linking
> record... unless you can push the backend SESSIONID back in the
> frontend response somehow.
Sure, I'll try my best
On Fri, Nov 11, 2011 at 04:55:02PM +0100, Wolfgang Breyha wrote:
> This includes the murders frontend sessionid. But this sessionid is never
> written to syslog by lmtpd on frontends. Only the backends log their sessionid
> when the frontend logs in.
Hmm... yeah, that sucks.
> So, currently these
Hi!
lmtpd returns a session ID with his "250 ok SESSIONID=".
This includes the murders frontend sessionid. But this sessionid is never
written to syslog by lmtpd on frontends. Only the backends log their sessionid
when the frontend logs in.
Even if the frontend logs its own session id, there
