Essentially what we'll need to do is when we detect that a new email is part of an existing discussion according to the in-reply-to or reference headers to then compare the subject of the incoming email to the original node title. If it's significantly different, this means the person changed the subject line intentionally meaning to start a new discussion.

We'll use http://php.net/manual/en/function.levenshtein.php to compare the strings.

Another note, this means upon creating new nodes that we should strip out the in-reply-to headers and the reference header so that email clients won't thread the new discussion with the previous one it was forked from.

Comments

tobias’s picture

tobias commented

Another approach to this would be to have a manual link for group managers to fork a comment into a new node. This is functionality I seem to recall seeing in some forum or other.

Cheers,

Tobias

kyle_mathews’s picture

kyle_mathews commented

That's an interesting idea but probably not one that ogm will handle. That would belong as a forum submodule or something.

kyle_mathews’s picture

kyle_mathews commented
Status: Active » Fixed

Fixed with http://github.com/KyleAMathews/og_mailinglist/commit/292c29a8201031826a8...

tobias’s picture

tobias commented
Status: Fixed » Active

Maybe the comment mover module: http://drupal.org/project/comment_mover

kyle_mathews’s picture

kyle_mathews commented
Status: Active » Fixed

We cross posted. :) Moving status back to fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

tobias’s picture

tobias commented

Is it possible to make this an optional feature? I think it's causing problems on my site, where replies are very often being interpreted as being new threads and are starting new nodes instead of adding comments. Or maybe my problem is a different bug?

In any case I'd rather the threads be kept together rather than making assumptions about when someone is forking a thread.

Cheers,

Tobias