🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

3 total messages Started by Ronald Harichandran Mon, 25 Jan 1993 19:02
Filter and From header line
#3534
Author: Ronald Harichandran
Date: Mon, 25 Jan 1993 19:02
9 lines
885 bytes
Use of "from" in filter-rules currently matches text on the From: line.
With some of the automatic LISTSERVers, the original poster's address is
retained in the From: line, and the only way to know that the message is
from a particular LISTSERVer is to look at the very first From header
line.  Is there any way to instruct the filter program to scan the very
first From header line in mail?

Ron Harichandran
Michigan State University
Re: Filter and From header line
#3553
Author: Scott Ophof
Date: Thu, 28 Jan 1993 03:27
32 lines
2000 bytes
Ronald Harichandran said:
]Use of "from" in filter-rules currently matches text on the From: line.
]With some of the automatic LISTSERVers, the original poster's address is
]retained in the From: line, and the only way to know that the message is
]from a particular LISTSERVer is to look at the very first From header
]line.  Is there any way to instruct the filter program to scan the very
]first From header line in mail?

The original poster's addr is *always* retained in the "From:" line
when such an item is distributed by LISTSERV.  "LISTSERV" of course 
refers to Eric Thomas' implementation of the list server concept, ie. 
the one and only program which is allowed to use the name "LISTSERV", 
if one respects trademarks (even when not formally registered, ie. 
based only on ones morals).

That was just to make clear that "LISTSERV" is imho a protected name,
and should not be applied to other list servers.

LISTSERV uses the "Sender:" field as per RFC-822, if I'm not very wrong.
Ie. "Sender:" states where the item came from last, and overrides the
address in "From:" (which with LISTSERV states the original author of
the item).
So to answer your question, you should look in the "Sender:" field for
the name of a discussion list if sent by LISTSERV software.
This may not necessarily be the address of the LISTSERV itself!

If it's not LISTSERV but some other list server (or mailing list manager),
then all bets are off as far as *I* can tell.  Too many different solutions
have been implemented, imho.  :-(

Regards.
$$\
Re: Filter and From header line
#3562
Author: R. David Murray
Date: Thu, 28 Jan 1993 15:02
26 lines
2031 bytes
In article <9301280325.AA16613@SERVER.uwindsor.ca>, ophof@SERVER.uwindsor.ca (Scott Ophof) writes:
> Ronald Harichandran said:
> ]Use of "from" in filter-rules currently matches text on the From: line.
> ]With some of the automatic LISTSERVers, the original poster's address is
> ]retained in the From: line, and the only way to know that the message is
> ]from a particular LISTSERVer is to look at the very first From header
> ]line.  Is there any way to instruct the filter program to scan the very
> ]first From header line in mail?
> 
> The original poster's addr is *always* retained in the "From:" line
> when such an item is distributed by LISTSERV.  "LISTSERV" of course 

A possible answer to the question, though, is that, at least in the case
of the few LISTSERV lists I am on, the To: header contains the name of
the list.  I have, for example, 'if to contains IBM-KERM then save ...'
in my filter rules file, and that seems to work well.  It does not work
quite so well for some Internet mailing lists; there, the To: field is
not as consistent; sometimes the mailing list name only shows up in the
'Apparently To:' header.  

Which brings me to a question/suggestion.  It seems to me that a filter
rule refering to the To field also 'sees' text in the cc: field.  Why not
be consistent and also look at 'Apparently To:'?  Or has all this changed
in the new versions (I'm running ELM 2.3 PL11)?
-- 
david			david@staff.udc.upenn.edu
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