[nos-bbs] Message log jam - SOLVED - BUG ??

[Michael E Fox - N6MEF]

I haven't used "tcp access" but I do use "ip access" without this problem.
You could use that as a workaround.  After all, if you're blocking TCP from
some hosts due to abuse, don't you want to block UDP and other stuff from
those hosts, too?

 

Michael

N6MEF

 

 

From: nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org] On Behalf
Of Wm Lewis
Sent: Monday, March 24, 2014 9:24 AM
To: nos-bbs at tapr.org
Subject: Re: [nos-bbs] Message log jam - SOLVED - BUG ??

 

I have solved the mystery of all my incoming mail being jammed.
 
This all started right after I started using 'TCP ACCESS...'
 
That's when the message log jam started. After turning off TCP ACCESS, all
my backed up messages came flooding in. 
 
My rules were simple, as outlined below:
===========================================
#Allow a specific AMPRnet host SMTP access
tcp access permit 44.0.0.0/8 all
 
#Allow LUNIX Commercial mailserver SMTP access
tcp access permit 50.79.156.221/32 all  
tcp access permit 127.0.0.1 all
 
#but deny all other services to abusers
tcp access deny 1.50.228.0/24 all
tcp access deny 1.81.175.0/24 all
tcp access deny 1.81.248.0/24 all
--- (long list of abusers here) ---
 
#Allow a specific subnet access to telnet port 23,
tcp access permit all 23
 
#Note that all other hosts not matched above, are denied access
============================================================
 
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?
 
For good measure I added/allow from 127.0.0.1 so JNOS would not block
itself, but that had no effect.
 
I turned off TCP ACCESS yesterday and as of this morning, all the mail is
still flowing as it should.
 
So for now, I have to leave TCP ACCESS turned off.
 
Anyone else seeing this behavior ??
 
Wm Lewis
KG6BAJ
 

  _____  

Date: Mon, 24 Mar 2014 00:07:34 -0700
Subject: Re: [nos-bbs] Message log jam
From: n6mef at mefox.org <mailto:n6mef at mefox.org> 
To: thunderft at hotmail.com <mailto:thunderft at hotmail.com> ; nos-bbs at tapr.org
<mailto:nos-bbs at tapr.org> 

I'm sure I was not.

 

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. 

 

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.

 

Michael

 

 

 

 

Sent from my Verizon Wireless 4G LTE smartphone



-------- Original message --------
From: Wm Lewis 
Date:03/23/2014 11:47 PM (GMT-08:00) 
To: TAPR xNOS Mailing List 
Subject: Re: [nos-bbs] Message log jam 

Michael:
 
I need to you to rack your brain on this.....
 
When you had your log jam, were you experimenting with 'TCP ACCESS' at the
time ???
 
I think I just found the source of my jam.....
 
.... more to follow.....
 
Bill
KG6BAJ
 

> From: n6mef at mefox.org <mailto:n6mef at mefox.org> 
> To: nos-bbs at tapr.org <mailto:nos-bbs at tapr.org> 
> Date: Fri, 21 Mar 2014 15:05:43 -0700
> Subject: Re: [nos-bbs] Message log jam
> 
> Good to know, but I don't think this was my situation.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20140324/be62adf8/attachment.html>