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

[Bob Tenty]

May be something wrong in the order of the tcp access lines you missed?


#  NOTES:  The preceding TCP ACCESS code is read in order.  TOP down!
#  Order is important.  In reading from top down the first rule that
#  satisfies the origination address and port requirements is the one
#  used.  So you should place excludes before includes for specific
#  originating addresses then followed by global [all] includes or
#  excludes.
#
#  Example:
#  tcp access permit all 1 32768
#  tcp access deny 167.23.43.1 3600 3601    <= should be first line
#
#  This would not deny 167.23.43.1 access to convers server as the first
#  rule would satisfy the test to allow, but reversing the order would!

73,

Bob VE3TOK


On 14-03-24 12:24 PM, Wm Lewis wrote:
> 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

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