Re: Problem with multiple sites and crossposting
Janne Jalkanen <[email protected]>
| Newsgroups | gmane.network.sn |
|---|---|
| Message-ID | <[email protected]> |
> How are you retrieving the articles? > Does this indeed save bandwidth? We have local newsgroups in which we want the posts to be immediately visible, but since we want the other site to receive them too - we just synchronize every two hours. > Since both sites have the same admin, in your position I would > sync both by having each log in to the other, and issuing sncat -n, > and feeding that output for snstore; instead of relying on nntp. > Since bandwidth is an issue, this can be compressed at the source > and decompressed at the target host. I'll need to try that. We are using SSH to both encrypt and compress the traffic. > sn wasn't designed to host other sites, so it does not do one > critical thing: check for loops. It's not too hard to do this from > a shell script, basically just make sure any message about to be > stored does not have self's hostname in the Path: line. Looking at the path line, it looks something like this: Path: A|B|A|B|A|B|A|B|A|B|A|B|A|B I can't claim much expertise in the sources at the moment, so should I just wrap snstore in a shell script that greps for 'Path' and hostname and rejects the article? Though if I understand correctly, that article will then be transported at each synchronization point anyway, until it expires (which in our case will mean about a year), getting rejected at the other end, using bandwidth each time, correct? -- Janne Jalkanen Regex Pty Ltd [email protected] Level 11 Tel: +61-438 428 041 530 Lt Collins St Fax: +61-3-9909 7510 Melbourne, VIC 3000