Sorry if this has been asked/suggested before but I can find no trace of it in the archives.
My point is this - if it were possible for subscribers to use a web form to post to archives (as well as the usual email method) it would be nice. Users could then choose to use a service as a conference or via email.
For myself, there are times when I like to receive everything by email so I don't miss anything and times things are busy enough that I would prefer the conference idea. Often I want to switch from one to the other depending on how busy things are.
The point about doing this with the archives is that this functionality is almost there already - it just needs a way of "on-server" posting to be developed. Since this could be limited to subscribers and can only go to the list then it is safe.
There are other products that do this sort of thing - I think bscw does, but non so "clean" and simple to use as mailman. Also, the same thing *could* be done with gating to newsgroups but doing so involves much unneccessary complexity.
Why has no-one combined the list-server and conference functions before (rhetorical).
Please COPY replies to a.k.heath@shu.ac.uk as I'm not a subscriber
Andy
Andy Heath a.k.heath@shu.ac.uk
My point is this - if it were possible for subscribers to use a web form to post to archives (as well as the usual email method) it would be nice. Users could then choose to use a service as a conference or via email.
This is pretty easy to do, and I think outside of the scope of Mailman.
Just set the list subscription so that it only archives, then restrict posting to a single known (non-obvious) address.
The Web form would then call a CGI script which would provide the correct headers to a local sendmail invocation, or connect to a remote system on port 25 and jump through the proper ESMTP hoops.
The mail should be sent to look as if it's coming from the allowed address, so it will go through the system checks and be archived.
What I would really like to see in addition to sender-based authentication is some sort of "if this header matches send it through" type scenario. Majordomo uses an 'Approved: password' header -- implementing something similar could allow Web-based forms to post, etc. NOTE: password wouldn't have to be the list password -- it could be anything. Mailman should also have the option of stripping it out before sending the message through.
Imagine any of these possibilties!
Approved: mypassword # we'll add a special header Message-Id: .*example.com # we generate a Message-Id, so trust it Date:.*\sAug\s1999 # allow anyone to post before the contest ends
Chris
I renamed a list by creating a new one with the new name, then copying the old one over the top of the new one. This worked, except that the archives still get put into the old location. Does anyone know where the info might be that tells the archiver where to put the archives -- it appears to be separate from the visible configuraton options.
Thanks!
JohnR
participants (3)
-
Andy Heath
-
Christopher Lindsey
-
John Reekie