On Aug 6, 18:20, Roger Fajman wrote:
} Subject: Re: Re SCIFAQ-L errors
 
} It sounds to me like a list header option that allowed the list owner
} to specify where duplicates are to be sent would help solve this
} problem.  Then the option could be used to cause the duplicates to be
} sent to the owner of SCIFAQ-L instead of the poster.  It seems like it
} makes sense for a list like SCIFAQ-L, whose only purpose is to
} redistribute USENET articles.
 
Precisely, except that I'd add one more possibility: "drop".  Giving:
 
        - poster (default - current action)
        - owner
        - drop (drop the posting, no bounceback to anyone)
 
"drop" is ideal for SCIFAQ-L, because the list owner knows that it's
only carrying USENET (bounces shouldn't be done anyways) FAQs (where
duplicates are frequent).
 
Una could set "drop" and set his checksum retention high:
        a) He'd not have worry about mailer barfs
        b) He could impose a minimum repeat time - a weekly USENET
           FAQ probably doesn't have to be sent weekly on a LISTSERV.
           Perhaps a retention equivalent to about 2 weeks or even
           a month could be used to great benefit - reducing traffic
           on the LISTSERV, yet not missing anything new.
        c) Not worry about spurious bounces getting FAQ writers annoyed.
 
This doesn't take anything away from LISTSERV, doesn't impose the
dreaded USENET conventions on LISTSERV.  It only makes its operation
more flexible for slightly out of the usual use.
 
--
Chris Lewis; [log in to unmask]; Phone: Canada 613 832-0541
Psroff 3.0 info: [log in to unmask]
Ferret list: [log in to unmask]