wex@milano.UUCP (05/14/86)
In article <3789@utah-cs.UUCP>, donn@utah-cs.UUCP (Donn Seeley) writes: > Does anyone have a suggestion for handling these awkward situations? (referring to people shipping rogue sources across mail links and busting them.) The first thing to do is to update the new-users' guide to reflect this problem (much the way it reflects problems of flammage today). When we want to chastise incorrect behavior we need to have a source of correct information to point at. Second, we need to expand the routing tables so that in addition to frequency information, load information is also given. The information could contain an estimate of the amount of traffic a site is willing to accept, and an estimate of how much they're currently accepting. When a mail message (or group of messages) would exceed the willing threshold, the message(s) are delayed and the respective sysops are notified automatically. They can then negotiate an appropriate action (and possibly examine the contents of the mail). They could decide to reroute it, to reject it, to break it up into smaller chunks, to track down and lynch a repeat offender, etc. The costs of this idea are in sysop time and in getting and maintaining extra database information. Also, large messages will be slower to mail. The benefits are: reduced (and maybe eliminated) huge messages. Additionally, we might be able to catch bugs like that HP site that sent out their entire news directory. And, ultimately, we might be able to preserve some of the more fragile links (thus improving things for everyone). -- Alan Wexelblat ARPA: WEX@MCC.ARPA UUCP: {ihnp4, seismo, harvard, gatech, pyramid}!ut-sally!im4u!milano!wex "We do not act as a result of consideration, but as a way of being."
broman@noscvax.UUCP (05/14/86)
In article <3789@utah-cs.UUCP>, donn@utah-cs.UUCP (Donn Seeley) writes: ...<description of an academic's poverty>... > Last year in October and > November, some obnoxious person shipped tens of megabytes of data from > a uucp site on the east coast to one on the west coast, using > utah-cs!hplabs as one of their links ... > Does anyone have a suggestion for handling these > awkward situations? Many sites restrict the size of messages they will pass on. Huge mailings get tossed and a message of regret is returned. The limit is usually 64K, sometimes 20K or less. If someone tries sending rogue sources in itty bitty pieces, they should be flamed by someone who watches the mail queue, or by mailer software which logs a record on who sends how often. It would be useful if mod.map data included info on such size limits placed on forwarded mail. Vincent Broman, code 632, Naval Ocean Systems Center, San Diego, CA 92152, USA Phone: +1 619 225 2365 Starship: 32d 42m 22s N/ 117d 14m 13s W Arpa: broman@bugs.nosc.mil Uucp: {floyd,moss,bang,gould9,sdcsvax}!noscvax!broman
joel@gould9.UUCP (Joel West) (05/16/86)
it would be nice if there were a way to limit the length of transfers
to certain expensive sites, or perhaps only through transfers to
those sites.
sure you can declare a separate mailer class in sendmail, but that's
a lot of explicit programming. Not that bad, though, if you only
have two classes: *CHEAP* and *EXPENSIVE*.
--
Joel West (619) 457-9681
CACI, Inc. Federal, 3344 N. Torrey Pines Ct., La Jolla, CA 92037
{cbosgd, ihnp4, pyramid, sdcsvax, ucla-cs} !gould9!joel
joel%gould9.uucp@NOSC.ARPArbj@icst-cmr (Root Boy Jim) (05/21/86)
The first thing to do is to update the new-users' guide to reflect this problem (much the way it reflects problems of flammage today). When we want to chastise incorrect behavior we need to have a source of correct information to point at. How about posting this guide to net.sources (or one of its subgroups, which seem to be gatewayed along with it)? People only on the ARPAnet (such as myself) have never read anything about etiquette (obviously :-). Or to spare the entire net, someone just mail that stuff to me. Oh yeah, if it's long, tell me you are willing, and I will pick someone to *actually* send it to me. No response means don't bother. (Root Boy) Jim Cottrell <rbj@cmr> "One man gathers what another man spills"