From owner-freebsd-current Thu Jan 7 15:37:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25101 for freebsd-current-outgoing; Thu, 7 Jan 1999 15:37:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25090 for ; Thu, 7 Jan 1999 15:37:48 -0800 (PST) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id AAA02409 for freebsd-current@freebsd.org; Fri, 8 Jan 1999 00:37:27 +0100 (CET) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m0zyM6w-000WyaC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Thu, 7 Jan 1999 21:32:54 +0100 (CET) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: News Server Date: 7 Jan 1999 21:32:51 +0100 Message-ID: <7735lj$cuq$1@mips.rhein-neckar.de> References: <199901052151.OAA06423@gongshow.masterplan.org> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199901052151.OAA06423@gongshow.masterplan.org>, Jason George wrote: > Because forwarding the FreeBSD lists via UUCP home would be evil (Why? You are aware of batched SMTP, aren't you? I get quite a chunk of the freebsd-lists by E-mail to my UUCP home site, and it doesn't hurt me.) > 3) The scripts do not like cross-posts at all. Only one group will get > the post. Anyone wanting to hack the code to correct this should > contact me. I don't have the time or resources to do this. This is a basic problem of mail->news gateways. Those "crossposts" arrive as separate mail messages that share the same message ID. This works for mail, but not for news, where a message ID is *unique*. The first message is gatewayed, further ones will be refused as duplicates by the news system. (You could "solve" this by giving out new message IDs. However, this would be a case of the cure being worse than the disease. Replys sent in response to the articles would reference the munged IDs, breaking threading. Bad. Also, if you munge message IDs and your mail->news gateway interacts with a rogue news->mail gateway, the result will be a catastrophic feedback loop. Don't say it won't happen. I've seen too many people munging message IDs between Usenet and BBS networks and claiming nothing would happen. Catastrophic duplicate spews did happen regularly. Don't munge message IDs in newsgroups. Never ever.) Setting up a local mail->news gateway is a trivial exercise. I have one running here for my personal consumption (on a, dare I say, Linux box). While not perfect, Rich $alz' mail2news program from his newsgate package does quite a nice job. Generally I suggest setting up *local* mail->news gateways, not propagating the groups, and if you're a feeder site, keeping the gateway on a separate news server. You can make the groups moderated, set the moderator address to the submission address of the source mailing list, and inews will automatically forward attempts to post a followup article to the mailing list. Very nice. Alas, this doesn't work for freebsd-*, because such messages will have Path and Newsgroups header fields, and our dear FreeBSD postmaster filters all submissions that appear to bear the dreadful mark of Usenet. Of course this, uh, questionable policy can be circumvented again. PS: What is this thread doing in freebsd-current? -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de See another pointless homepage at . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message