Slash Boxes

Slash Open Source Project

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • by peloy (2936) on Monday November 19 2001, @10:24AM (#3699) Journal

    I guess I don't completely understand the problem. Do we want to submit e-mails we receive from a mailing list as stories, or as discussions?

    Submitting the mails from mailing lists as stories should be trivial, but I think the problem is that when there is a discussion on a mailing list you don't want to see all messages in the thread as separate stories; you want to see all messages going as comments to the story (or discussion, if the first message in the thread was posted as a discussion.)

    So, the problem seems to be: how de we map incoming messages to an existing discussion or story? Perhaps we would need to use the "In-Reply-To:" field of incoming messages and map that to the parent id in the comments table? In this case the message ID should probably be stored somewhere in the DB, probably in the comments table.

    This particular feature would make Slash a very powerful system because it would allow to use a Slash site as archive for mailing lists.
    • by Anonymous Coward
      yes, i think this would make slashcode the "killer app". its awesome as it is right now, but if it could integrate email lists! omg!

      check out for an existing perl email -> www solution. maybe it could be integrated into the slashcode?

    • by Anonymous Coward
      well, this is what yahoo groups (formerly egroups) does. thier interface definately sucks, but they keep track of messages and attach replies to the appropriate post.

      as long as you got people to leave the subject line alone (only add re:) then it probably wouldn't be too tricky, just add a key (ie FHJ6F7JI900F) and use it to match to a story/comment)