Re: Preventing junk mail + proposed sf-announce linkage


From Peter Wainwright <pan@xxxxxxxxxxxxxxxxxxxx>
Date Thu, 27 May 1999 19:47:16 +0100

John Bray wrote:

> Peter, is it possible to set the Space Future mailserver to only
> accept messages from members of the list. That should
> stop this kind of thing, though might make it more awkward for
> people who read and post from different locations.

Agreed. It is in fact extremely difficult to police this kind of thing -
for example this email came from a free email account service akin to
Hotmail, so simply banning the domain prevents potential valid
subscribers.

However, I have decided to alter the policy regarding subscriptions -
previously any message sent to the list from a non-subscriber was
accepted
and the sender subscribed to the list. Now only subscribers may post and
an explict subscribe message must be sent to sf-discuss-request first.

As John points out, this will inconvenience people who post from more
than
one email address, but unfortunately there is no avoiding it.

As a general point, all subscribers to this list are welcome to invite
their friends along too :-) At the moment we're quite lucky in that
the signal-to-noise ratio is actually very high, at least at the moment.

----------------

While I'm on the subject of maintaining the mailing lists, I have been
considering either subscribing sf-discuss itself to the sf-announce
mailing list, and removing duplicates for those who subscribe to both,
on the grounds that sf-announce is low traffic and most people on
sf-discuss probably wouldn't object to update information about Space
Future in any case.

Alternatively I could arrange for subscriptions to sf-discuss to also
subscribe to sf-admin, which would allow people to unsubscribe from
sf-admin at a later date. Does anyone have any strong preferences or
objections to either of these proposals?

Lastly, I have occasionally wondered if there is any other mailing list
that Space Future could implement that would be of use - once you have
the general system up, adding a new list is trivial. I already have
the intention to establish sf-journal as a digest of the Space Future
Journal, just as soon as I have time for it, but I'm open to suggestions
for others.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Peter Wainwright      Cybrid Technology Ltd.     
Peter.Wainwright@xxxxxxxxxx
=-=-[ http://www.spacefuture.com ]-=-[ Peter.Wainwright@xxxxxxxxxxxxxxx
]-=-=
http://spacefuture.com/lists/sf-discuss/May-1999/msg00012.html
spacefuture.com
crawl=CC-MAIN-2016-50
5530
application/http; msgtype=response
sha1:GD6EE4234FCEDZAGS5XMP74QH2BHDYBN
<urn:uuid:67013b40-e26b-4e76-bd5d-d9430d8862ae>
2016-12-05T18:44:20Z
66.111.5.164
sha1:VG6VXMCPSS7TCYPHHNCGEOJKAH7KSFZC
<urn:uuid:23150e66-7ade-4392-9934-66ce1e1d1c47>
http://spacefuture.com/lists/sf-discuss/May-1999/msg00012.html
response
<urn:uuid:72d09ede-3ece-40a5-b3f2-8691a2192acf>
robots: classic
hostname: ip-10-31-129-80.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2016-50
operator: CommonCrawl Admin
description: Wide crawl of the web for November 2016
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf