Failing to get 'reply above line' in all emails

Just adding some more info as I suspect this is related to the 'reply' code not getting through.

Message sending method is 'mail'
Message body filter is 'messaging plain text'

I think we had the same problem as you did -- see #521446: og_notifications doesn't play nice with other modules implementing message_alter for our fix.

peted - can you post back whether this was what you were running into? Regardless, I'll keep this case open until #521446 is resolved.

Hi Ian - we are about to try the above suggestion, but thought I would post the a modified summary of my investigation in case it helps shed light - or at least confirms the problem. It may also point to why others users have experienced 'inconsistent' results that are refered to in other posts.

HISTORY and CONTEXT
Up to this point we had identified that Notifications re Group content going to a member of a Group were NOT including REPLY ABOVE LINE but were spotting some inconsistencies as well.

So I reset Subscriptions so my Test User could subscribe to Blog Content (which can be posted to Groups) and therefore enable me to test sending both Group and non-Group content.

Seems the issue relates to whether NOTIFICATIONS are going out due to being SUBSCRIBED or being a MEMBER OF A GROUP.

And that if AUTHOR is set to receive Notifications of own content then their Notifications differ in some cases with those received by a SUBSCRIBER

OG Config is set to : YES - Autosubscribe users to any groups that they join.

OG notifications for new content is set to SUBJECT = [site-name] [ogname]: [title]

Notifications for node creation is set to SUBJECT = New [type-name]: [title]

which all ties in with the observed behaviour below.

'REPLY ABOVE" settings come from here /admin/messaging/mail2web and is set to
- Blog Entry
- Group Meeting
- Group Post
- Group Wiki

SUMMARY OF TESTING

I created a Blog Entry via 3 approaches
1. via /node/add/blog with no Group audience
2. via /node/add/blog and adding Group audience
3. via /node/add/blog?gids[]=122 (ie the Create Blog from within the Group context)

Basically
- a SUBSCRIBER gets the correct outcome for options 1 + 2
- an AUTHOR gets correct outcome only on option 1

(In below 'table' YES = has 'reply above line')

Created via > /node/add/blog NO GROUP AUDIENCE
Subscriber = YES
Author = YES

Created via /node/add/blog = GROUP AUDIENCE
Subscriber = YES
Created = NO

Created via /node/add/blog?gids[]=122 = GROUP CONTENT
Subscriber = NO
Author = NO

SO yes I think this pretty much confirms problem is where og_notification sits in the order of things.

Hope the above helps. Do you concur that disabling og_notification's message_alter function is a 'safe' route to go for now?

Okay - so the testing above and the suggestion about "disabling og_notification's message_alter function" has lead to this patch http://drupal.org/node/521446#comment-1926934 which seems to have resolved our issues though we will do more testing - hopefully some others can test and we can move on to the next part of this 'snakes and ladder' game - which is resolving why some messages via mailhandler are 'looping' or for whatever other reason, causing multiple notifications to get fired out.

modified title from 'any' to 'all' as it better reflects what we actually ended up dealing with.

Switch to mailcomment project. Mail2web is now known as "mailcomment" due to a trademark issue with the name mail2web.