SMS change might break security

Home Forums Conduit: AEP Model SMS change might break security

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #11846
    Gavin Perry
    Participant

    In AEP 1.1.2 one of the changes was this:
    Update Node-RED SMS node to use only HTTP instead of HTTPS to conserve memory.
    When using Node-RED, I noticed that I can’t send e-mail using smtp.google.com (Gmail) as Google rejects the sender as insecure. Did you change to SMS affect SMTP too? Is there a way to get the Node-RED email sender to work (Got an insecure SMTP server we can use 🙂 ?)

    #11847
    Jeff Hatch
    Keymaster

    Gavin,

    The change to the SMS node was for localhost-only traffic between the node and the SMS API interface on the Conduit. HTTPS consumes a lot of memory in nodejs.

    As for the SMTP node, I’m not sure that it does TLS. That may be the issue. Either that or the auth is broken. Either way, it is the stock Node-RED SMTP node, and we haven’t touched it. I haven’t gotten it to work effectively with any “real” email server.

    Jeff

    #11848
    Jeff Hatch
    Keymaster

    Gavin,

    You could try the what Nick O’Leary recommended in the following thread:

    https://developer.ibm.com/answers/questions/176998/error-on-sending-e-mail-by-using-e-mail-node-on-no.html

    Jeff

    #11849
    Brandon Bayer
    Blocked

    Gavin,

    It sounds like you may need to allow insecure apps to access your account: https://support.google.com/accounts/answer/6010255?hl=en

    -Brandon

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