<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<link href="chrome://translator/skin/floatingPanel.css"
type="text/css" rel="stylesheet">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">May be something wrong in the order of
the tcp access lines you missed?<br>
<br>
<br>
# NOTES: The preceding TCP ACCESS code is read in order. TOP
down!<br>
# Order is important. In reading from top down the first rule
that<br>
# satisfies the origination address and port requirements is the
one<br>
# used. So you should place excludes before includes for
specific<br>
# originating addresses then followed by global [all] includes or<br>
# excludes.<br>
#<br>
# Example:<br>
# tcp access permit all 1 32768<br>
# tcp access deny 167.23.43.1 3600 3601 <= should be first
line<br>
#<br>
# This would not deny 167.23.43.1 access to convers server as the
first<br>
# rule would satisfy the test to allow, but reversing the order
would!<br>
<br>
73,<br>
<br>
Bob VE3TOK<br>
<br>
<br>
On 14-03-24 12:24 PM, Wm Lewis wrote:<br>
</div>
<blockquote cite="mid:BLU170-W393E00DE41FC7980B2EB68A97A0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">I have solved the mystery of all my incoming mail
being jammed.<br>
<br>
This all started right after I started using 'TCP ACCESS...'<br>
<br>
That's when the message log jam started. After turning off TCP
ACCESS, all my backed up messages came flooding in. <br>
<br>
My rules were simple, as outlined below:<br>
<font color="#ac193d">===========================================</font><br>
<font color="#ac193d">#Allow a specific AMPRnet host SMTP access<br>
tcp access permit 44.0.0.0/8 all</font><br>
<br>
<font color="#ac193d">#Allow LUNIX Commercial mailserver SMTP
access<br>
tcp access permit 50.79.156.221/32 all <br>
tcp access permit 127.0.0.1 all</font><br>
<br>
<font color="#ac193d">#but deny all other services to abusers<br>
tcp access deny 1.50.228.0/24 all<br>
tcp access deny 1.81.175.0/24 all<br>
tcp access deny 1.81.248.0/24 all</font><br>
<font color="#ac193d">--- (long list of abusers here) ---</font><br>
<br>
<font color="#ac193d">#Allow a specific subnet access to telnet
port 23,<br>
tcp access permit all 23</font><br>
<br>
<font color="#ac193d">#Note that all other hosts not matched
above, are denied access</font><br>
<font color="#ac193d">============================================================</font><br>
<br>
So, I'm not sure if there is a bug in the TCP ACCESS that causes
JNOS mail to hang in the incoming MQUEUE folder or what?<br>
<br>
For good measure I added/allow from 127.0.0.1 so JNOS would not
block itself, but that had no effect.<br>
<br>
I turned off TCP ACCESS yesterday and as of this morning, all
the mail is still flowing as it should.<br>
<br>
So for now, I have to leave TCP ACCESS turned off.<br>
<br>
Anyone else seeing this behavior ??<br>
<br>
Wm Lewis<br>
KG6BAJ <br>
</div>
</blockquote>
<br>
<div style="bottom: auto; left: 279px; right: auto; top: 667px;"
class="translator-theme-default" id="translator-floating-panel">
<div title="Click to translate"
id="translator-floating-panel-button"></div>
</div>
</body>
</html>