Morbus Iff wrote:
> What would
> be more helpful, code-wise, would be something that DID NOT
> HAVE to live on the SERVER. If a script could be dummied
> up in a procmail recipe (or whatever, you know), then
> ANY subscriber would be able to provide an RSS feed,
> and not necessarily have to wait for an already overworked
> (or unappreciative) admin to implement a plugin.
I had occasion to be thinking about this last fall a I contemplated the
fact that out Mail server of choice has mailing list options but no list
archives options. I was looking for an agent that could be subscribed
to the Mailing List and would put it's copies of the postings in a data
store for indexing and searching.
One of the issues that I bumped into was that was passes for HTML in
some email programs is [insert expletive of choice here]. Putting it in
an XML data store was going to cause a tons of validation errors.
But RSS has a significantly greater win and that's in the fight against
spam. Having finally broken down an put Spam Assassin on the front end
of Mail Server of choice, I'm just observing for the first time in a
scientific fashion just how much of email passing into the system might
meet programmatic definitions of spam (to this point I was living a
sheltered life where Mozilla's heuristics were doing a reasonably good
job of skimming off the scum at the desktop level).
Mail to RSS means we bypass the filter "logic" and can get back to
distributing information via reasonably trusted mechanisms.