Hi, Situation: Our company uses a IBM helpdesk system to generate alerts and work orders. We are currently in the transition from MOM 2005 towards SCOM 2007 R2 and have reached a milestone which needs to be passed to continue. The IBM system is generating items according to a mail scrubber which scrubs the incoming mails and puts it in the correct fields in his form. There's unfortunately no way to implement a connector at the time being. The mails which are coming from MOM2005 are coming in UTF8 format and are completely processed and are working fine. However all the mails which come from SCOM 2007R2 are also sent in UTF8 but are completely random text when they arrive in the IBM system. When I tick the option to not use the formatting in the subject the subject itself is processed correctly. To conclude: This is the complete opposite of what a lot of people out there are facing (header messed up but body ok) Maybe I'm missing something here but these are the troubleshooting steps I've already taken: Sent the mail to my mailbox and then did a forward to the mailbox => mail came in ok and was processed. Used a script to scrub the alerts out of the webconsole and send them in html to the scrubber ==> no go. Checked out the result with various formatting in the mail settings in scom (UTF, UTF7, UTF8, ECBIC,...) ==> no go. Things that crossed my mind: Is there a reg key to also put the body in "use no formatting" as there's an option for the header to accomplish this but not for the body of the text. The 2 servers of MOM and SCOM are both Win2003 machines running. I've came accross a post in another forum that perhaps the mime version could be the issue. But unfortunately this was an issue with the console view and not with the mails so don't want to end up with 2 systems which can't mail. As long as this connection is not working I can't continue to shift the focus from MOM 2005 to SCOM 2007 so thanks in advance for reading this and if you need more info please do not hesitate to ask. See you at MMS2011!It's doing common things uncommonly well that brings succes.

Can anyone give me some pointers? It's doing common things uncommonly well that brings succes.

Hi Dieter, Have you found a solution to your e-mail problem? If you cant get the notification channel and subscription format correct a alternativ could be to use command based notification or pwoer shell. For more info around how to configure command based notification in 2007 R2 please take a look at http://contoso.se/blog/?p=860 . If you have Opalis in your organization, maybe you could do this with a integration pack.Anders Bengtsson | Microsoft PFE | blog at http://www.contoso.se

Hi Thanks for your answer. I've currently set up a command notification channel with a powershell script which is scrubbing the webconsole and sending the info in html. To give you an update on the situation. At this point we might have pinpointed the actual bottleneck. The mail is sent to a Lotus Notes mailbox and is displayed correctly. However in the dbase behind lotus notes the mail body field is encoded base 64 code. Which is not a problem for the Lotus Notes viewer because it decodes on the fly but unfortunately the agent which pulls in the mails in the mainframe system just reads out the "body" field in the dbase and is not decoding the message. So now we are looking for a way to decode on the fly but came accross some issues with line return carrier symbols which are mal converted. Hanging in there but get's kinda frustrating. Thanks again for your interes in my issue.It's doing common things uncommonly well that brings succes.

Just for reference when somebody does a search. I managed to solve this issue by creating a mailing via Powershell and update it from there. More info here: http://scug.be/blogs/dieter/archive/2011/05/11/scom-dump-alerts-to-text-file-and-mail.aspxIt's doing common things uncommonly well that brings succes.