Russ says:
"... a few years ago the university hosting it decided only faculty members there could own lists. …"
Yeah. we sort of had that for class discussion lists. Of course, it ended with the TA's and administrative assistants running the List. Even as "quiet owners". Sometimes there were even "shared passwords" (heaven forefend). The idea most of the faculty wanted to manage their lists was a somewhat quaint holdover of some of the (very) early lists (or a very unclear notion of what was involved). However, if your University has made such a determination, and your site admin won't assist, I do not see a clear path for you. Especially as many (most? all?) of the affected parties have been deleted. At one time, there was some thought Usenet newsgroups could replace the listserver. We see how those have ended up. Now I gather there is a thought of using Microsoft Groups (not sure which) for the job. Advantage would be reasonably good support for Groups. Disadvantage is shifting ideas of groups and the idea they really should be administered with PowerShell (which is a great tool, and I sure liked it) but might scare off new folks.
Well, continue to wish you well with this,
--Joe
________________________________________
From: LISTSERV List Owners' Forum <[log in to unmask]> on behalf of Russell Hunt <[log in to unmask]>
Sent: Friday, September 28, 2018 4:52 PM
To: [log in to unmask]
Subject: Re: records of past subscribers
I'd try setting up another list, as Joe suggests, if I had direct access, but every new list goes through an approval process and I probably couldn't do it, as I'm listowner by courtesy. I've run this list for 20 years, but a few years ago the university hosting it decided only faculty members there could own lists. We found someone to be the authorized owner, and I have access because I'm the only one we could find who was interested in maintaining the list.
> Solving (or even correctly identifying) these is not always straightforward.
> I recall a lot of owners and admins threw in the towel when the mail header problem came up.
> And not without reason. If resolution is not possible (can happen) do what you can to
> notify the subscribers of the problem.
That's the problem, really. Subscribers still on the list don't _have_ the problem; I don't have any way to find out who's been bounced in order to contact them. Most people who've been bounced would never know (until, perhaps, they tried to post; it's a Send=Private list). And it's not particularly active -- currently a couple of dozen posts a month -- and people wouldn't realize they were off.
The list was begun, sometime a bit earlier than 1991, as a mainly discussion list, but in recent years has become pretty much all announcements -- calls for papers, job adverts, publication and conference announcements. I'm beginning to think that LISTSERV may no longer be the appropriate software (and the university hosting it might not object to losing it; I suspect it's the only one running on their server that extends internationally, and I also suspect it's something of a PITA).
-- Russ
############################
To unsubscribe from the LSTOWN-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTOWN-L&A=1
############################
To unsubscribe from the LSTOWN-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTOWN-L&A=1
|
