There are three modules designed within the last 18 months that all purport to provide the same basic functionality: creating new nodes in an organic group via email.
http://drupal.org/project/mail2og (June 10 2009) alpha version
http://drupal.org/project/og_mailhandler (Sept 22, 2009) a dev version
http://drupal.org/project/og_mailinglist (March 17, 2010) alpha version

it is unclear why the second two even exist (full disclosure, I helped to spec out Mail2og with arthurf). But I am not speaking selfishly. I don't care one way or another which module or approach delivers the functionality. I just want to see the functionality available with drupal. But instead of having a solid module that allows users to create nodes within a specific organic group we have 3 modules none of which have stable releases.

I am sure that the developers of these modules, at one point or another, were motivated either by interest or a client contract to provide this functionality. I am also sure that between the three a fare amount of work and thinking has gone in to solving the problem. Perhaps one, two or all three of the developers would be interested in collaborating on developing a module if not for drupal6 than looking toward drupal7 that offers this functionality? Or hand off maintenance of their module to someone else, or officially retire/abandon their module to make room for one of the others to become a solution that others can rally around.

Thinks about it.

Comments

GregoryHeller’s picture

xurizaemon’s picture

Thanks for raising, Gregory. I agree - these three modules should be consolidated.

I created this module after suggestion by Moshe that it be created to allow some code to mature - it would be just as good for same to exist in one of the other modules.

It hasn't had much action from me as it did the job needed ...

Has anyone reviewed the code from all three to see how well they'd merge?

xurizaemon’s picture

The aim of this module WAS simply to test some code for inclusion in OG. Unfortunately that was never pursued. So merging this code with OG is another option.

OG Mailinglist -

  • Not just an OG / Mailhandler drop-in, this module also includes changes to Exim in order to speed response times on mail processing and really aim for a more complete mailinglist / groups result than the cron-driven solutions do. Requires root access etc.
  • Raison d'etre. I have to say that this comment in particular sounds very familiar and rings some loud bells about the OG / Mailhandler setup.
  • Usage: 4 sites, low I'm sure due to the complexity of configuration.

Mail to OG

  • Replaces the complex listhandler mailbox setup & listhandler command configuration with one which uses email addresses to identify the appropriate group.
  • Probably circumvents one of the two issues, #136606: Mailhandler cannot assign emailed content to group, which this module aims to resolve. It deals with the listhandler command issue by simply not using listhandler commands :)
  • Probably not a suitable candidate for replacement. Sites which do wish to use mailhandler + og can't (by my reading of the mail2og project page) do so; they must swap to mail2og.
  • Therefore also not a suitable path for this code. (But you're welcome to take whatever you want!)
  • Usage: 33 sites (this module currently has 32! neck and neck!)

Conclusion - on looking at those two modules briefly, I don't see how I can fold this module into either and have it provide the same solution for the sites currently using it.

I'm definitely open to discussion and suggestions here. Currently this module is not a major priority, and unless I get some work which focusses me on it, I will be maintaining but not developing it. I'm open to co-maintainers or contributors if anyone wants to help with that.

Greggles reports that he's using this stack, most of it for g.d.o, but also on another site for more complete groups solution.