4 Apr
2010
4 Apr
'10
6:40 p.m.
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?
Thanks!
micah
--
"It is no measure of health to be well adjusted to a profoundly sick society." -
J Krishnamurti
5 Apr
5 Apr
11:59 p.m.
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!).
6 Apr
6 Apr
2:48 p.m.
On 2010-04-05, micah anderson wrote:
On Sun, Apr 04, 2010 at 02:40:16PM -0400, Micah
Anderson wrote:
Great! I'm happy to help test and provide feedback. once it hits
unstable I can pull it and try it out.
m
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!).
9 Jul
9 Jul
6:13 a.m.
On Tue, Apr 06, 2010 at 09:59:01AM +1000, Simon Horman wrote:
On Sun, Apr 04, 2010 at 02:40:16PM -0400, Micah
Anderson wrote:
Hi Micah,
these changes have been merged and are included in 1.19~rc1,
which is now in sid.
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!).
5187
days inactive
5283
days old
3 comments
3 participants
participants (3)
-
Micah Anderson -
micah anderson
-
Simon Horman