CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] Proposed EOL for 3830 at contesting.com

To: <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] Proposed EOL for 3830 at contesting.com
From: <john@kk9a.com>
Date: Mon, 11 Dec 2023 17:25:11 -0500
List-post: <mailto:cq-contest@contesting.com>
There is really no reason to get emails from any lists.contesting dot com list, 
it is very easy to read the archives.  Besides raw scores, there are many 
interesting stories on 3830 and  I like the score listings that were added 
years ago.

What is the plan for posting contest scores once 3830 is decommissioned?  Have 
a post contest 3.830MHz net😊

John KK9A



Dave Pascoe km3t wrote:

Good morning.

The 3830 Mailing List has been around since at least 1996. My 
recollection is that we had it going prior to that but the current 
archives have been around since January 1996. Over the years it has been 
a useful resource for the contesting community.

It is becoming increasingly difficult to deliver email to certain 
(major) email providers, despite using every required email sending best 
practice. We have subscribers marking email as spam (damaging server IP 
reputation), subscribers who have changed email address and never 
unsubscribed from the list, and many other administrative hassles.

Despite the admin hassles, Bruce Horn WA7BNM's 3830score.com site has 
been wildly successful, and is really the focal point for gathering 
contest scores after contests. It is difficult to imagine that anyone 
would prefer getting an email for every single score that's reported. 
It's not a very efficient use of email.

So unless I hear (really) loud screams before December 31, 2023, I 
intend to decommission this list on that date. You can contact me at 
km3t at km3t.org if you have any comments. The historical web archives 
of the 3830 list will continue to be available.

73,
Dave KM3T


_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
<Prev in Thread] Current Thread [Next in Thread>