Re: Problem with multiple sites and crossposting

> : 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?
> 
> Yes.

Okay, the script was easy to write, but I encountered a different
problem: All programs rely on finding a program called 'snstore' to
store their articles.  No problem, me thinks, we just call our script
'snstore' and the original program 'snstore-orig'... Except that
snstore is really a symlink to snsend, and won't work unless the file
is called exactly 'snstore'.  So I can't name my script 'snstore'...

So, now I have to do some creative PATH juggling (a kludge if I ever
heard one) or patch the source code of snsend.c to expect a different
name.  Both are somewhat unsatisfactory, as they make upgrading that
much more difficult.

It would seem that a check in snsend.c for loops would be useful.
Otherwise, the proposed ability to filter messages could also be used
for a similar purpose.

> No, if an article originally posted to A, then transferred to B,
> were to arrive back at A, then it would be rejected and not stored
> (your script would have discarded it).  Since it was not stored,
> B would not see that article from A again, and so neither would A.
> There would be 1 rejection, so you waste the transfer of 1 article
> only.

Good.  Thanks!

-- 
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