We have a running DotNetNuke installation (4.8.2) on various servers. Each server mails event notifications to our IT mailing list. However, this e-mail arrives without any formatting whatsoever, even newlines are stripped. This makes the notification mails highly unreadable, so I would like to change this.

Unfortunately neither Google nor the DotNetNuke site and forums allowed me to find the answer. Of course I tried to go through all configuration options but I could not find it.

For example, a part of an error message we receive might look like this:

AssemblyVersion04.08.02PortalID-1PortalNameUserID-1UserNameActiveTabID-1ActiveTabNameRawURL/xxxx/Hos
t/Portals/tabid/xx/portalid/xxx/Default.aspxAbsoluteURL/xxxx/Host/Portals/tabid/xx/portalid/xxx/Defa
ult.aspxAbsoluteURLReferrerUserAgentMozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4
322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)DefaultDataProviderDotNetNuke.Data
.SqlDataProvider, DotNetNuke.SqlDataProviderExceptionGUIDzzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzzInnerExce
ptionCould not load file or assembly 'DotNetNuke.Modules.Media' or one of its dependencies. The system 
cannot find the file specified.FileNameFileLineNumber0FileColumnNumber0MethodSystem.RuntimeTypeHandle._
GetTypeByNameStackTraceMessageSystem.IO.FileNotFoundException: Could not load file or assembly 'DotNet
Nuke.Modules.Media' or one of its dependencies. The system cannot find the file specified. File name: '
DotNetNuke.Modules.Media' at System.RuntimeTypeHandle._GetTypeByName(String name, Boolean throwOnError, 
Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName) 
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolea
n reflectionOnly

Hopefully any of you guru's out there have a suggestion on how to investigate and/or fix this problem

Sebastian, thanks for your time and your response.

Unfortunately this can't really be the problem; this smtp server accepts and sends all kinds of messages just fine. A good example in this context would be another type of message that is also sent by DotNetNuke, being portal-signup-mails. A typical message we receive is formatted nicely/normally, for example as follows:

Dear xxxx xxxx,

Your Portal Website Has Been Created. Please read the following
information carefully and be sure to save this message in a safe 
location for future reference.

Portal Website Address: xxxx.xxxx.xx/xxxxxxxx
Username: xxxxxxxxx
Verification Code: xx-xx

Please take the opportunity to visit the website to review its 
content and take advantage of its many features.

Thank you, we appreciate your support...

DotNetNuke

In case anyone googling for this very problem ends up in this thread, here's the solution (annex workaround) we now use.

As far as we could research our problem is the result of a bug or omission in DotNetNuke (4.8.2). We chose a completely different approach to reach the same goal.

We wrote a custom SSIS script that is called from a batch file, which in turn is scheduled by Windows to run every 5 minutes.

The SSIS package retrieves the last 5 minutes worth of entries from the EventLog table in the DotNetNuke database. The LogProperties column is simple xml which is parsed through XSLT to an html. The SSIS package sends html-formatted e-mail then to our error-mailing-list.