<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'>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>
<FONT color=#ac193d></FONT> <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>
<FONT color=#ac193d></FONT> <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>
<FONT color=#ac193d></FONT> <BR>
<FONT color=#ac193d>#Allow a specific subnet access to telnet port 23,<BR>tcp access permit all 23</FONT><BR>
<FONT color=#ac193d></FONT> <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> <BR>
<DIV>
<HR id=stopSpelling>
Date: Mon, 24 Mar 2014 00:07:34 -0700<BR>Subject: Re: [nos-bbs] Message log jam<BR>From: n6mef@mefox.org<BR>To: thunderft@hotmail.com; nos-bbs@tapr.org<BR><BR>
<DIV>I'm sure I was not.</DIV>
<DIV><BR></DIV>
<DIV>The only thing I can think of is that it happened right around the time that I switched my link with N6ZX from AXUDP on W2XSC to AX.25/RF on W4XSC. The hang occurred on W2XSC. </DIV>
<DIV><BR></DIV>
<DIV>I can't say for sure when it happened and I can't imagine how that would affect anything. But restarting JNOS solved the problem.</DIV>
<DIV><BR></DIV>
<DIV>Michael</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>
<DIV style="COLOR: #575757; FONT-SIZE: 9px">Sent from my Verizon Wireless 4G LTE smartphone</DIV></DIV><BR><BR>-------- Original message --------<BR>From: Wm Lewis <BR>Date:03/23/2014 11:47 PM (GMT-08:00) <BR>To: TAPR xNOS Mailing List <BR>Subject: Re: [nos-bbs] Message log jam <BR><BR>
<DIV dir=ltr>Michael:<BR> <BR>I need to you to rack your brain on this.....<BR> <BR>When you had your log jam, were you experimenting with 'TCP ACCESS' at the time ???<BR> <BR>I think I just found the source of my jam.....<BR> <BR>.... more to follow.....<BR> <BR>Bill<BR>KG6BAJ<BR> <BR>
<DIV>> From: n6mef@mefox.org<BR>> To: nos-bbs@tapr.org<BR>> Date: Fri, 21 Mar 2014 15:05:43 -0700<BR>> Subject: Re: [nos-bbs] Message log jam<BR>> <BR>> Good to know, but I don't think this was my situation.<BR></DIV></DIV></DIV> </div></body>
</html>