Neews to accomodate multiple news servers from uu.net

[The Doctor]

On Sun, Nov 11, 2007 at 09:06:21AM -0500, Jeffrey M. Vinocur wrote:
> On Sat, 10 Nov 2007, The Doctor wrote:
> 
> > 1)
> > 
> > At Verizon, news is received via NNTP on the host <custID>.inbound.news.uu.net.
> > 
> > Is INN STABLE capable of this?
> 
> Yes.  Configure your innfeed.conf to feed news to that host.
> 
> And configure your newsfeeds with the H3 flag as they describe.
> 
> 
> > We have a number of systems providing NNTP feeds to customers. Your
> > server(s)/firewall(s) must be configured to allow ICMP and NNTP access to
> > port 119 on your server from all of our servers including: nntp-out1.uu.net
> > thru nntp-out15.uu.net, each of which expands to approximately 17 servers.
> 
> You should be listing those 15 hostnames in incoming.conf, which will take 
> care of your issue regarding 256 IP addresses -- INN will resolve each of 
> the 15 hostnames to 17 IP addresses and keep track of them all for you.
> 
>  
> > 2)
> > 
> > Nov  5 14:30:21 sosrv10.sac1.maint.ops.us.uu.net newslink[28774]: [ID 702911
> > +news.notice] ns2.nk.ca:/prod/news/dqueue/Huca516916!.S00539 connect: 502 You
> > +have no permission to talk.  Goodbye.
> >
> > Supposed this is fixed.
>  
> This means you don't have their hosts listed in incoming.conf as above.
> 
> 
> > 3)
> > 
> > You should be using "news.uu.net".
> > 
> > Name:    news.uu.net
> 
> > Addresses:  198.6.0.5, 198.6.0.6, 198.6.0.12, 198.6.0.13
> >                                                             
> > 
> > end of 3)
> > 
> > Now you know why I say supposedly.
> 
> I don't know what part of the config you're talking about here.
> 
>  
> > 4)
> > 
> > For outbound (posting) you should use <customerID>.inbound.news.uu.net as in
> > "!@#$%^&*(.inbound.news.uu.net". Thjis is better than using thje generic term
> > +"news.uu.net".
> > 
> > For receiving feeds please allow Port 119 connections from any server in the IP
> > +Netblock
> > 198.6.0.0/24. All Verizon Business news servers are in this IP netlbock.    
> 
> As I mentioned above, if you include the hostnames they mention, you will 
> get those IP addresses without needing to list them all manually.
> 
> 
> > Point:  This is the first time I have seen this model.
> > Has anyone else had to deal with this?
> > 
> > Can INN be up to the job to do this??
> 
> This is a pretty common model (although usually on a slightly smaller 
> scale) and INN can deal with it easily.  I'm not sure why you're having so 
> much confusion -- can you point out exactly what parts you're having 
> trouble with?
> 
>

Easy the news.uu.net servers that are sending to me
are news*.news.uu.net .

The outbound is no issue, that is solved.

The inbound is the only issue outstanding.

Let me see if I can implement the above mentioned. 

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.