Re: Subject: Loop control mechanisms in mailing lists

Thread View: net.mail.headers

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Jacob_Palme_QZ%QZCOM.MAILNET Tue, 18 Feb 1986 02:34

#611

Author: Jacob_Palme_QZ%QZCOM.MAILNET
Date: Tue, 18 Feb 1986 02:34

18 lines
1340 bytes

Your solution of appending a postmark on the message is a variant
of my method (2). This method should have been formulated in
more general terms, to append some kind of trace information
on the message. I prefer to put the postmark in the TO field
for the following reasons:

(a) What you want to stop is not the same message looping back
to the same host. This, in fact, can be perfectly legal in some
cases. What you want to stop is the message looping back to the
same mailing list.

(b) The TO: field is one of the safest field from being munged
by header-munging systems.

Best of course would be to have an additional, special field
in the headers intended for this kind of trace information -
provided that all systems accept and are willing to handle this
trace field in the proper manner.

Re: Subject: Loop control mechanisms in mailing lists

#629

Author: Michael C. Berch
Date: Thu, 20 Feb 1986 18:20

56 lines
3012 bytes

Speaking of loop control, we have received FOUR copies of this message
and several others gatewayed to net.mail.headers:

Second of four copies:

> From lognet2!seismo!brl-smoke!smoke!Jacob_Palme_QZ%QZCOM.MAILNET@MIT-MULTICS.ARPA Thu Feb 20 10:12:38 PST 1986
> Relay-Version: version B 2.10.2 8/21/84; site styx.UUCP
> Path: styx!lognet2!seismo!brl-smoke!smoke!Jacob_Palme_QZ%QZCOM.MAILNET@MIT-MULTICS.ARPA
> >From: Jacob_Palme_QZ%QZCOM.MAILNET@MIT-MULTICS.ARPA
> Newsgroups: net.mail.headers
> Subject: Re: Subject: Loop control mechanisms in mailing lists
> Message-ID: <1024@brl-smoke.ARPA>
> Date: 18 Feb 86 01:52:46 GMT
> Date-Received: 19 Feb 86 19:52:10 GMT
> Sender: news@brl-smoke.ARPA
> Lines: 18
> 
> Your solution of appending a postmark on the message is a variant
> of my method (2). This method should have been formulated in
> more general terms, to append some kind of trace information
> on the message. I prefer to put the postmark in the TO field
> for the following reasons:
>
> [remainder deleted...]


Fourth of four copies:

> From lognet2!seismo!brl-smoke!smoke!Jacob_Palme_QZ%QZCOM.MAILNET@MIT-MULTICS.ARPA Thu Feb 20 10:05:45 PST 1986
> Relay-Version: version B 2.10.2 8/21/84; site styx.UUCP
> Path: styx!lognet2!seismo!brl-smoke!smoke!Jacob_Palme_QZ%QZCOM.MAILNET@MIT-MULTICS.ARPA
> >From: Jacob_Palme_QZ%QZCOM.MAILNET@MIT-MULTICS.ARPA
> Newsgroups: net.mail.headers
> Subject: Re: Subject: Loop control mechanisms in mailing lists
> Message-ID: <1026@brl-smoke.ARPA>
> Date: 18 Feb 86 02:34:08 GMT
> Date-Received: 19 Feb 86 19:52:13 GMT
> Sender: news@brl-smoke.ARPA
> Lines: 18
> 
> Your solution of appending a postmark on the message is a variant
> of my method (2). This method should have been formulated in
> more general terms, to append some kind of trace information
> on the message. I prefer to put the postmark in the TO field
> for the following reasons:
> 
> [remainder deleted...]

Note that these have different message-IDs from brl-smoke. 
Since this has occurred before, I assume we can rule out the
possibility of duplicate messages being sent over from the Internet.
Would whomever is doing the gatewaying please look into this?

Michael C. Berch
ARPA: mcb@lll-tis-b.ARPA
UUCP: {akgua,allegra,cbosgd,decwrl,dual,ihnp4,sun}!idi!styx!mcb

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads