| Date: | Tue, 29 Jul 2008 15:50:05 -0700 |
| Reply-To: | jfh@stanfordalumni.org |
| Sender: | "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> |
| From: | Jack Hamilton <jfh@STANFORDALUMNI.ORG> |
| Subject: | Re: Amateurs web camchat |
|
| In-Reply-To: | <a198ba8804c8a6ff3e02e66abd548ee7.squirrel@tasso> |
| Content-Type: | text/plain; charset="ISO-8859-1" |
On Tue, 29 Jul 2008 21:26:18 +0100 (BST), "Eric"
<eric@deptj.demon.co.uk> said:
> > Comp.soft-sys.sas is a news group, but SAS-L is a mailing list. There's
> > also a web interface through Google, and some ISPs provide their own
> > front end.
> >
> > But the parent of all these was a mailing list, not a newsgroup.
> >
> > There are now 3 (I think) peered mail servers, which do have owners.
> >
> > The appropriate place to discuss this is probably the SAS-L BOF at the new
> > incarnation of SUGI. Basically, there aren't any good options currently.
> > --
> > Jack Hamilton
> > jfh@alumni.stanford.org
> >
>
> I replied to a usenet post using newsreader software, there was no sign
> whatever of any connection to a mailing list. It would seem that someone
> is taking usenet posts and feeding them automatically into a mailing
> list.
> I say "automatically" because of the timing of the out-of-office mails I
> received when I posted my message.
Yes, it's automatic.
> I do not understand why this is being done,
It's being done in order to give readers two different ways to see
messages. For some people, email is more convenient, and for others,
the newsgroup or Google Groups interface is more convenient.
> and in any case it is being
> done badly - it would seem that the message-posters email address is
> being
> included in the Reply-To header in the mailing-list message, which should
> not be done.
That's debatable.
> Also it does not make sense that the domain part of such an
> address should be capitalised.
And it converts my userid from jfh@alumni.stanford.org to
jfh@stanfordalumni.org, which not what I want it to do.
> I think the owner of the mailing list should take steps to find out what
> is going on.
It seems to be working as expected, except for the porn problem.
--
Jack Hamilton
Sacramento, California
jfh@alumni.stanford.org <== Use this, not jfh@stanfordalumni.org
|