stange symbols in notifications

[Hari Sekhon]

Hari Sekhon wrote:
> Here is an example
>
> CRITICAL: Only 19.11G (4%) free on 
92.168.1.138ig2
>
>
> Why does it seem to be mangled? Is this a character set issue or a local issue or something?
>
> Hari
>
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
>
>   
also, the web interface shows this normally:

CRITICAL: Only 18.85G (4%) free on \\192.168.1.138\big2

but the email alerts always come out as

CRITICAL: Only 18.88G (4%) free on 
92.168.1.138ig2


I have got quite a lot of these notifications (which is good) but they 
are always mangled in the same way (which is bad).

It's not that terrible cos I still know what's going on but this 
shouldn't happen, and I'd like to resolve it.

Hari

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null