Forum Home › Forums › Runtime Bugs › Server Bugs › Email sender bug
Tagged: Automatic Control Module, Email
- This topic has 14 replies, 2 voices, and was last updated 6 years, 2 months ago by Mikhail.
-
AuthorPosts
-
January 31, 2018 at 12:06 pm #3091tripodeParticipant
Hello, I am currently testing the Automatic Control Module and I can receive mails with values, time, etc, when an event is triggered. Great !
But with some channels, the subject or the message get corrupted data. Just only when adding {EvText} field.
I have tryied many configurations, but when I receive an event from that channel the data comes corrupted, and not with others. Both are ‘real’ type values.
January 31, 2018 at 1:34 pm #3092tripodeParticipantMore info I can add here:
The corrupt email has
Content-Type:text/plain;charset=utf-8
Content-Transfer-Encoding:base64The correct mail has:
Content-Type:text/plain;charset=us-ascii
Content-Transfer-Encoding:quoted-printableThe first one comes from a OMROM PLC, and the second one comes from a SIEMENS PLC, but both come from an OPC server through OPC Demo device.
February 1, 2018 at 2:09 pm #3096MikhailModeratorHi,
What text contains the events that cause the error? How to reproduce the error?February 1, 2018 at 2:15 pm #3099tripodeParticipantHi,
{EvText} contains the event description; should be: ‘Alarm High: 111.1ºC’.
If I include {EvText} in subject of the messages, all the text in the subject is corrupted too.
I can reproduce it, as it only fails with the alarms/events coming from OMROM PLC
February 2, 2018 at 1:32 pm #3109MikhailModeratorHi,
You can generate events manually using Server. Can you reproduce the error by creating an event such way?February 5, 2018 at 8:50 am #3115tripodeParticipantMikhail, If I use the event generation from server I get the emails corrupted when I set ‘Alarm High: 111.1ºC’ in the ‘Description’ field, but I get it OK if I set that field to ‘Alarm High: 111’ (removing .1ºC)
February 5, 2018 at 8:52 am #3116tripodeParticipantOK, the problem is the ‘º’ character. If I remove it the message is good.
February 5, 2018 at 4:07 pm #3121MikhailModeratorCould you determine where the bug makes effect? Can you send email with that sign from Communicator?
February 6, 2018 at 7:05 am #3127tripodeParticipantYes, If I use the ‘command’ feature in Communicator and try to send a simple ‘ º ‘ character both in subject and content fields, the mail is corrupted.
February 6, 2018 at 11:00 am #3134MikhailModeratorThank you. I added this bug to the tracker.
February 19, 2018 at 1:35 pm #3186MikhailModeratorHi,
Strange, but I can’t reproduce. I send command from Communicator using my gmail. Can you send me the text of the command that caused the error?
Example:
myemail@gmail.com;Test;100°CFebruary 19, 2018 at 1:48 pm #3187tripodeParticipantHi,
With this I have the bug: myemail@gmail.com;test;Alarm High: 111.1ºC
With this I don’t: myemail@gmail.com;test;Alarm High: 111.1C
February 20, 2018 at 4:54 pm #3191MikhailModeratorHi,
Both examples work on my workstation. What mail server do you use for sending (in the “device” properties)? I use gmail.February 21, 2018 at 7:10 am #3195tripodeParticipantHi, Here using hmailserver. I couldn’t make gmail work.
February 21, 2018 at 3:50 pm #3205MikhailModeratorFor gmail you should “Enable IMAP” on “Forwarding and POP/IMAP” settings.
-
AuthorPosts
- You must be logged in to reply to this topic.