search for: brightok

...d=%m rip=%r lip=%l pip=%{real_rip} mpid=%e %c This is primarily useful for backend servers to log both the rip, lip, and in case of xsession, the real rip. I haven't done extensive testing yet, but as long as nothing does anything weird elsewhere in the code, it should be good. http://www.brightok.net/jbates/dovecot-2.1.10-real-ip.patch dovecot: pop3-login: Login: user=<test>, method=PLAIN, rip=192.168.1.5, lip=::1, pip=::1, mpid=8665, secured Jack Bates

Version: 2.1.9 Connecting directly to the proxy server on the LMTP port, issue lhlo, mail from, rcpt to, data. After the . closing of data, it just hangs there. The logs on the proxy server show: Sep 27 19:55:12 proxy1 dovecot: lmtp(9398): Connect from 69.8.2.71 Sep 27 19:55:24 proxy1 dovecot: lmtp(9398): Error: lmtp client: connect(lmtp, 7025) failed: Connection refused root 9398 1102

The logging on lmtp and lmtp proxy is pretty limited from what I can see. It seems to handle errors, Connect, Disconnect, and in the case of lmtp delivery, it logs where an email is saved to. The lmtp may be enough, "connect, saved user, saved user..., disconnect", but I was curious if it is worth while to add more info logging for the proxy, primarily which recipients are sent to

Dec 14 14:33:03 test2 dovecot: auth: Debug: auth client connected (pid=24143) Dec 14 14:33:14 test2 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=pop3#011secured#011session=D6dl6dDQdAAAAAAAAAAAAAAAAAAAAAAB#011lip=::1#011rip=::1#011lport=110#011rport=38004#011resp=<hidden> Dec 14 14:33:14 test2 dovecot: auth: Debug: