dovecot - May 2012 - dovecot-2.1.6: why are loglines longer and longer

do we really need "session=<ugAua+i/ewBUcit1>" additional
to proxy log-lines? until this change it was possible on
a 24" screen with "tail -f /var/log/maillog" to watch
without linebreaks, now each proxy line breaks

PLEASE reconsider such changes!

May 13 12:27:38 mail dovecot: imap-login: proxy(*******@thelounge.net): started
proxying to 127.0.0.1:143:
user=<********@thelounge.net>, method=PLAIN, rip=********, lip=******,
TLS, session=<ugAua+i/ewBUcit1>



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20120513/db910bde/attachment-0004.bin>

On 13.5.2012, at 13.31, Reindl Harald wrote:
> do we really need "session=<ugAua+i/ewBUcit1>" additional
> to proxy log-lines? until this change it was possible on
> a 24" screen with "tail -f /var/log/maillog" to watch
> without linebreaks, now each proxy line breaks
> 
> PLEASE reconsider such changes!
> 
> May 13 12:27:38 mail dovecot: imap-login: proxy(*******@thelounge.net):
started proxying to 127.0.0.1:143:
> user=<********@thelounge.net>, method=PLAIN, rip=********,
lip=******, TLS, session=<ugAua+i/ewBUcit1>
For login process lines you can configure this from login_log_format_elements
setting.

Anyway the session IDs are especially useful with proxying, since you can match
proxy connections to backend connections easily by grepping for the session ID
from both logs.