In reply to:
The issue isn't "Is it confusing the few tech-savvy people who are using it today?" it is "Will it confuse the non-savvy people who are just general Empeg consumers a few months from now when Empeg's hit the street on a wider basis?"
As a general rule, the non-savvy consumers don't find web interfaces objectionable. It's those of us who are savvy enough to write filters for our email that really prefer having discussions in mail folders instead of web pages. I still think you're tilting at windmills here.
In reply to:
If marc wanted a functional mailing list,
He doesn't. I don't. Mailing lists we can do, and that wheel's been invented rather nicely a few times. No, he, like me, wants to be able to read this discussion in a far more user-friendly way than the web interface presents.
In reply to:
... instead he put a half-cooked
recipe out there which is just a brain-dead non-solution and tries to convince the rest of the world that everyone should help HIM.
Sigh. This has obviously trancended reason with you.
I give you credit though. In the 10+ years I've been on the 'Net, this is the first time anyone has added themselves to my kill file. 
Now then, on to solutions:
In reply to:
1.) user authentication
Any suggestions? This is the only sticky one to me.
In reply to:
2.) threading
Why is this difficult? My last post explained several ways to do it.
In reply to:
3.) post authorization (a different entity altogether from authentication)
Again, you'll have to explain. I don't understand why this isn't already solved if you solve authentication. If you get a message (authenticated somehow) you then look to see if that user can post. If not, then send back a bounce. The logic to authorize posts is already there, we're just accepting input from a different source.
In reply to:
playing games with dynamic e-mail addresses requires access to the configuration files sendmail/qmail/MTA-of-choice uses.
You didn't actually read what I wrote, did you?
This depends on the MTA delivering everything address to *@empeg.comms.net to the gateway.
This is a single configuration entry, and the norm for "joe's random web hosting". All mail to your domain goes to one mbox. Make that mbox the script, and you're done. All I'm doing is reading the To: line for input. And I suggested a way to use the subject line for that instead.
-Zandr
Mk.I #150
Mk.II #39
Previous Topic
Index
