PRTG sends email notifications to a portal that forwards the messages as SMS. Since the upgrade to V13 these SMS have an unreadable subject. What can I do?
Why do SMS notifications have a subject like "SUBJ:=?utf-8?B?Z29iYmxlZGlnb29r?=" ?
For reasons regarding compatibility with various e-mail clients we had to adapt the headers of email notifications so that they're encoded in UTF-8 now. Apparently some SMS providers or scripts are not able to decode these headers correctly and forward them unprocessed.
Please contact your provider or script guru and ask if they have a solution for processing UTF-8 encoded e-mails.
One of our customers found the solution for AT&T:
If you use txt.att.net please use mms.att.net instead.
For our workaround we configured PRTG to send a text based email to to an email account on our exchange server. We then configured a server side rule to redirect those incoming emails from PRTG to our alphanumeric pagers email addresses and this fixed our problem. We now get readable text. We haven't tested this on SMS.
I have received complaints from users about this too. The @mms.att.net workaround threads the incoming messages into a single TXT message on iPhones, and does not time stamp all the alerts, so it is difficult to tell when a message was received. Is there any other way to disable the UTF-8 encoding of the subject line? Thanks!
We're working on a fix regarding this issue.
At the moment there is no way to get PRTG to send non-UTF8 subjects, sorry!
However, you might try to adapt Steve's workaround to your sitiuation, for the time being.
This issue still affects SMS on our iPhones (AT&T network). The MMS workaround is not acceptable. Also, tried forwarding through outside mail server (including Gmail) but this does not fix the issue either (and I really don't want to route these messages through a mail server - these are my PRTG emergency alerts!).
Please advise on the status of this fix!
which version of PRTG and which type of SMS notification do you use?
This topic is about SMS already being sent through an email server. We didn't mean to suggest you should route your SMS through email servers. So if the subjects of your SMS are not correct, this is presumably a different topic.
May I ask you to open a support ticket at [email protected]?