Nagios Support Forum

I looked through the mail headers, and see the issue in there as well. I haven't been able to reproduce this locally here.

Can you provide a copy of the mail headers from the first server it hits in your environment? I believe it's mail210ntv.

Also, can you update your template to use no HTML (this will cause it send as plaintext) and try again? Here it is stripped:

rkennedy wrote:I looked through the mail headers, and see the issue in there as well. I haven't been able to reproduce this locally here.

Can you provide a copy of the mail headers from the first server it hits in your environment? I believe it's mail210ntv.

Also, can you update your template to use no HTML (this will cause it send as plaintext) and try again? Here it is stripped:

Code: Select all

%alertname% came back with a %state% state at %time%

The alert was processed with the following thresholds:

    Lookback period: %lookback%
    Warning: %warning%
    Critical: %critical%

Here is the full alert output: %output%

See the last %lookback% in the Nagios Log Server dashboard at %url%

%lastalertlog%

Nagios Log Server

I went ahead and forwarded those headers to you Via PM. Removing the formatting seems to have no effect.

Hmm, do you have another SMTP server you could possibly use or can you try using PHP mail to see if it still sends with these = signs?

I've tried to replicate this a lot and I'm unable to at this point.

rkennedy wrote:Hmm, do you have another SMTP server you could possibly use or can you try using PHP mail to see if it still sends with these = signs?

I've tried to replicate this a lot and I'm unable to at this point.

PHP mail does not have the same symptoms as using SMTP. Ill reach out ot our exchange people and see about testing it via another SMTP server.

Thank.s

That sounds reasonable to me, we're pretty sure it's the SMTP server as the same process works on all of our test boxes over here. If a second SMTP server turns up the same result I think a remote session would be in order.