Unable to send emails

Forum Home Forums Understanding the Software Unable to send emails

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #934
    inpelsa
    Participant

    Hi,

    Please write proper documentation for the whole system and/or make it more intuitive. Some configuration screenshots or video (in any language) will help a lot. Some easy tasks take too long to guess how to make it work.

    Using 4.5.0.5…

    I have configured timed events, commands… they seem to be correctly raised. No luck using the kpemail device’s commands tab for testing.

    After ‘fighting’ with the config I get to this point, but no clue about what is happening:

    ——————————————————————————–

    Device 44 “EMailSender”
    ———————–
    DLL : KpEmail
    State : error
    Comm. session : time is undefined
    Command : 11/04/2016 18:35:18

    Comm. sessions (total / errors) : 0 / 0
    Commands (total / errors) : 4 / 4
    Requests (total / errors) : 0 / 0

    Current device tags data
    +——–+————-+——-+———+
    | Signal | Name | Value | Channel |
    +——–+————-+——-+———+
    | 1 | Sent emails | 0 | |
    +——–+————-+——-+———+

    No archive data

    No events

    Commands (recent 10 commands)
    +——+———————+———————————————————–+
    | Num. | Date and Time | Description |
    +——+———————+———————————————————–+
    | 1 | 11/04/2016 18:34:59 | Command: type = Binary, device num. = 44, data = 74657374 |
    +——+———————+———————————————————–+
    | 2 | 11/04/2016 18:35:04 | Command: type = Standard, device num. = 44, value = 1.000 |
    +——+———————+———————————————————–+
    | 3 | 11/04/2016 18:35:12 | Command: type = Binary, device num. = 44, data = 74657374 |
    +——+———————+———————————————————–+
    | 4 | 11/04/2016 18:35:15 | Command: type = Standard, device num. = 44, value = 1.000 |
    +——+———————+———————————————————–+

    ——————————————————————————–
    2016-04-11 18:34:47 Initialize communication line 4 “COM-ETH-RS485”
    2016-04-11 18:34:47 Start communication line 4 “COM-ETH-RS485”
    2016-04-11 18:34:47 Serial port ‘COM4’ is open
    Loading address book

    Waiting for commads…

    2016-04-11 18:35:18 Command to the Device 44 “EMailSender”, type: KpEmail, address: 44
    Incorrect command data

    2016-04-11 18:35:18 Command to the Device 44 “EMailSender”, type: KpEmail, address: 44
    Illegal command

    2016-04-11 18:35:18 Command to the Device 44 “EMailSender”, type: KpEmail, address: 44
    Illegal command

    2016-04-11 18:35:18 Command to the Device 44 “EMailSender”, type: KpEmail, address: 44
    Illegal command

    Waiting for commads…

    ——————————————————————————–

    Thanks for any help in advance,

    #935
    inpelsa
    Participant

    Reading the .DLL source code I guessed the command syntax:

    https://github.com/RapidScada/scada/blob/master/ScadaComm/OpenKPs/KpEmail/KpEmailView.cs

    “Sending email notifications.\n\n” +
    “Commands:\n” +
    “1 (binary) – send the notification.\n\n” +
    “Command text examples:\n” +
    “group_name;subject;message\n” +
    “contact_name;subject;message\n” +
    “email;subject;message”;

    I don’t know where this tip can can be seen but… better doc… lesser time spent.

    I understand you have to sell the Extended Support, but a community software without a minimal documentation is useless.

    #936
    Mikhail
    Moderator

    Hello,
    You right, the documentation should be improved.

    The description that you found in the source is shown on Device Libraries tab of Communicator application.

    To send emails automatically you need to install and configure Automatic Control Module

    Are emails sent successfully for now?

    #939
    Mikhail
    Moderator

    Functionality of sending emails will be added to the default configuration.

    #940
    inpelsa
    Participant

    well… it works sometimes.

    Is it mandatory to use a mail server IP Address?
    Seems using a DNS address doesn’t work anymore

    #941
    Mikhail
    Moderator

    Of course you can use DNS.
    E.g.,
    smtp.gmail.com, port 587

    #942
    inpelsa
    Participant

    It works well.
    DNS problem was just the firewall blocking it.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.