Re: Port logging
micah anderson <[email protected]>
| Newsgroups | gmane.mail.perdition.user |
|---|---|
| Message-ID | <[email protected]> |
On 2010-04-05, micah anderson wrote: > On Sun, Apr 04, 2010 at 02:40:16PM -0400, Micah Anderson wrote: > > > > Since I'm on the subject of logging... > > > > I notice that even if I am coming in on port 993, the port field that is > > logged is the port of the outgoing connection: > > > > Apr 4 11:19:24 auk perdition[19421]: Auth: 0.0.0.0->0.0.0.0 ---- server="0.0.0.0" port="143" status="ok" > > > > In this case, my incoming imap connection was an imaps (993) connection > > to perdition, it then looked up my user and found the server to connect > > to, and then made the connection to that server over port 143. I > > expected it to connect to the remote server over 143, but I was > > expecting to get a log entry from perdition that the port it received > > the connection on is port 993. > > > > Is there a way to get a log entry that indicates the incoming port > > number, as well as the outgoing one? > > Fixes for that are also in the changes that I need to merge (ASAP!). Great! I'm happy to help test and provide feedback. once it hits unstable I can pull it and try it out. m ______________________________________________ Perdition-users mailing list [email protected] http://lists.vergenet.net/listinfo/perdition-users
signature.asc
(application/pgp-signature, 835 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCgAGBQJLu0m1AAoJEIy/mjIoYaeQgKsP/2kmYDdl3zlh1eneF2p7Ynfz ZD/WpVfe8uK2JmFdP4DCZfO/7o+xxG7LfA1u9RObFILxP8YkgCE8pTj2W/H0jaPZ Rj1C10u7Zvzq8JSOs3VE1WPtUgWjMNmQfi0cDod3hgvcX1e+IXKzoTAGgr5VZZ1B ZgDMaQIhbDirxcWcifoANfIjf3B1Otx9CBu3yqwxKG6I+ZlKeUabz0fNo1Bsq9bP Awqo6RiC++MfhRoww9kJfudeDQtuxzQqF1twf8pzFqrJkxrDzVuunvMmrh0eN+k+ EN5zVtz/G0w92wi9N/tH0ww58GWr7RKBE1mNZyXGKkiJqXsXRTFKSfT/XTthkPAv /o8I9HWXri0ezIhhRN3JKJDOj0OFJGh9x0WT6yBv12MgfjrUSCVQ06SJ5X4Keswy GO5wSvxribCpv4SS+hrjTSicjy7pLGq1PWeT5/K49M0GUYLNS2GvS/bFDMZiM8Hm IA2ZXTp4z+PPN+bptLYGJz8zRUGipks0rU60Ds2SXi6zWI7Iwa/22Ct0D+3IQV31 HYNyazCnC/J2jL8MqBhusEUsd+mtniKWBQDMGLl/Ygp49dJbovEXygj49y2nBcdt KJXDTER922RPjM12BRBwl8SRmd7fzNA7J2P0+eMjN0nKqm5RwY05kurNUbr90Jtx WCSxHY9lTv11MzdXb8qg =qpBw -----END PGP SIGNATURE-----