On Wed, 4 Sep 2002, Ashley M. Kirchner wrote:
> Keith Morse wrote:
>
> > I don't know the answer without some research but, I use the following
> > tools to help understand this type of output.
>
> No, I know what the messages are. And I know what's it trying to do. What I
>wanted to kn
Keith Morse wrote:
> I don't know the answer without some research but, I use the following
> tools to help understand this type of output.
No, I know what the messages are. And I know what's it trying to do. What I
wanted to know was, WHAT on the remote end, could be trying to access my
On Wed, 4 Sep 2002, Ashley M. Kirchner wrote:
>
> Nevermind, I figured out what my error was. I was trying to block that IP,
> and allow other smtp traffic through, but I did it in the wrong order.
>
> Now I'm seeing where these things are coming from, and this is what I'm
> seeing:
>
Nevermind, I figured out what my error was. I was trying to block that IP,
and allow other smtp traffic through, but I did it in the wrong order.
Now I'm seeing where these things are coming from, and this is what I'm
seeing:
Packet log: input DENY eth0 PROTO=6 211.108.38.83:3868 my.ma
