Mailcomment is not working when mail2og is enabled. HELP.

I can confirm this is indeed a problem. I've spent days trying to debug this. Once I set "not pass through mailhandler" I received this message. This told me that the MessageID was probably incorrect. So I checked an email that the "subscribe" functions sent out, and it indeed does NOT have the correct messageID. It contains no Nid,Uid, etc type of lines. Instead it looks like this:

<20100804060753.9529FEF1BA@mydomain.com>

Instead of looking like the function docs say it should look like which is:
* Parse message id into parameters
*
* The message id should have this form:
* uid.nid.cid.time.signature@server string

But I do not know how or where the rest of the message ID is built. This is a critical error and completely stops this module from working at all. Since the msg id is not created properly by the subscribe notification emails, any replies to them will never work and will result in the original poster's error msg being displayed in the watchdog logs. If I were to take a guess, I would say that the mailcomment_message_alter (hook_message_alter) is not even being run because this is the only place I could find that builds a message ID header. I added a return at the top of the function which should have essentially broke everything, but it didnt do a single thing. Nothing broke and I did not see the drupal_set_message() notification that I set either. this tells me that the hook was never even run. How is this even possible? Is this hook obsoleted somehow? Is it unfinished? What is it? I've never even heard of it before and its not documented anywhere. What exactly is this hook for and when does it run and by which module is it defined.

So while I know why replies do not work, I am not able to fix this because I simply do not know exactly how this piece of the puzzle works. The code for it is very unreadable and does not have any comments that really help make things clear as to exactly what they are for, do, etc.

@crystaldawn, are you talking about the outgoing messageid?

That can be overwritten by mail servers downstream, particularly smtp servers seem to like to do that if you are using an smtp module to send mail.

I am not using the SMTP module to do the sending. I am using the php mail function which in in turn does use an smtp server but it does not as far as I know re-write any of the headers as that simply wouldnt make any sense. If these messageid's can be overwritten by things like this, then why would this module use the messageid for such a critical role rather than something else? like say the return address (the one used for bounce msgs) or something similar that would not be overwritten? Dont get me wrong, I am not knockin ya, but doesnt it make sense that if you know something like that would happen thats out of the hands of a potential user that you would come up with a different method? The server that this runs on is a CPanel server, I absolutely hate it, and it runs Exim. Do you know of any problems with this type of setup? Can u also explain why the hook_message_alter function simply does not run? I am stumped as to why I cant even get it to use drupal_set_message let alone do what it's suppose to do.

@SocialNicheGuru you could try http://github.com/ianshward/Mail-Group instead of mail2og. It's actually a spaces feature so requires the use of spaces and has a few other requirements. I'm seeing now that spaces and og are not dependencies in the .info file for mailgroup but they should be. It's ideally used with Open Atrium but should work w/o it. I'll release it soon on drupal.org. The module will let you choose a target address (based off of a catchall) for each group and users all get their own email address to send email to for security purposes. The name to use in the subject line for notifications coming from that group.

I realize this is not how to get mail2og working, but mailgroup may accomplish the same task w/ a different feature set.

This post is really helpful, I had at one question for every suggestion that y'all have addressed and now I don't have any questions because you've been so helpful.
Thanks!

@SocialNicheGuru OTOH I think the group settings will override whatever you put in the email body as commands for type: content-type. So right now it's limited to making all incoming content just that one type that the group admin chooses. You should first create a mailhandler mailbox which is a catchall email address so that x@example.com, y@example.com, whatever@example.com all go to that address. W/ 1and1 at least the catchall email address is like *@example.com. Then, configure mailcomment, selecting the catchall address. Then, config the global mailgroup settings /admin/settings/mailgroup, then config each group's mailgroup settings.

@SocialNicheGuru: that's right. You just need to select that base address.

When you're on /mailgroup there should be a block in the sidebar which shows the logged-in user what email address they should send to - it's different for each user which is possible because of the catchall. It sounds like for some reason the block is not showing up for you?

I just re-read the code for the block. It will not show up unless you've filled out all the settings for mailgroup w/in the group - Mailgroup Prefix, subject name, content type. It's set to show up in the right sidebar region.

Great suggestions. Makes a lot of sense. I'll make a d.o project for mailgroup likely this weekend then push this issue into that issue tracker and break it into two separate issues. I'll try debugging the block issue as well if I've got time over the weekend.

The right sidebar

I don't have mail2og installed, but I still get this error message:

Received an email with no parameters from [my private email address] Re: [site name] [node title] on [site]

Any idea how I can figure out the message id with gmail?

I posted a mailcomment patch here http://drupal.org/node/587688#comment-4368576 that needs review. It's not all that flexible, but it works for me.

Sorry, Mail Comment 6.x-1.x is no longer supported. Please upgrade to 6.x-2.x and re-open if still an issue. Thanks!