<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>You're seeing it as is in JNOS. Main allowed first, denied second and port 23 allowed third.<BR>
<BR>
(At one point I even deleted *ALL* the 'deny' lines and still had the same issue.)<BR>
<BR>I'm running a 64 bit system, so I don't know where JNOS's coding my hiccup from that, or if there is just a coding error related to TCP ACCESS?<BR>
<BR>
All I know is now that once I started using TCP ACCESS I had theproblem, and once I stopped using it, the problem went away .<BR>
<BR>
Bill <BR>
KG6BAJ<BR>
<BR>
<DIV>
<HR id=stopSpelling>
Date: Mon, 24 Mar 2014 18:42:49 -0400<BR>From: bobtenty@gmail.com<BR>To: nos-bbs@tapr.org<BR>Subject: Re: [nos-bbs] Message log jam - SOLVED - BUG ??<BR><BR>
<DIV class=ecxmoz-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>
<STYLE><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
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; TOP: 667px; RIGHT: auto; LEFT: 279px" id=ecxtranslator-floating-panel class=ecxtranslator-theme-default>
<DIV id=ecxtranslator-floating-panel-button title="Click to translate"></DIV></DIV><BR>_______________________________________________ nos-bbs mailing list nos-bbs@tapr.org http://www.tapr.org/mailman/listinfo/nos-bbs</DIV> </div></body>
</html>