Tag: cURL

Categories
Knowledge Support Support exacqVision Client

Troubleshooting E-Mail Message Profiles 

Description 

Troubleshooting notification e-mail server configuration settings when e-mail message profile tests fail.   

Product 

ExacqVision Client  

Solution

If the profile test fails, review the exacqVision Verbose System Logs (Configuration > YOURSERVER > Systems Logs tab) for information about the cause.    Pro Tip:  Filter the displayed search results for entries relevant to notifications by typing “notifypi” in the filter box.   

Here are some common causes including coresponding log entries.   

Invalid E-mail Server Password

Invalid E-mail Server Username

Invalid E-mail Server Port 

Invalid E-mail Server Security Type – STARTTLS

Invalid E-mail Server Security Type – Default

Invalid E-mail Server Outgoing Mail Server (SMTP) Address

Blocked by Firewall 

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

NotifyPI fails with cURL error 55

Symptom:

Email notifications fail to be received. 

<br>

Problem:

Server logs resemble:

15/12/2016 2:54:54 PM     NotifyPI     Warning     Profile Description: Playground. Notification attempt return code= 55

15/12/2016 2:54:54 PM     NotifyPI     Verbose     curl: (55) MAIL failed: 530

15/12/2016 2:54:54 PM     NotifyPI     Error       Failed to send notification using profile Playground. This message will be retried

This is caused by missing data from compliance with RFC5321. This will cause failure with some SMTP servers, but not others, depending on how they accommodate the message.

<br>

Solution:

Option 1:  If license subscription allows, update exacqVision Server version to 8.8 or higher. 

Option 2:  If license subscription does not allow update to 8.8 or higher, use an alternative Email/SMTP server. 

<br>

NotifyPI-fails-with-cURL-error-55-1.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

Manually Testing Email Notifications with cURL

Note: while you can test your profile/server via client’s Test Profile button, you won’t get cURL’s most complete debug information, which can sometimes be very informative when diagnosing notification failures.

<br>

ExacqVision Server versions 6.8 and higher use cURL to send notifications. If you are experiencing failures in sending notifications from the servers you may find error codes in the ExacqVision logs indicating the problem. In performing manual testing, you can remove ExacqVision from the equation and test only the cURL mechanism used to send notifications to your SMTP server using the following steps:

  1. Open a CMD prompt in Windows or Terminal on Ubuntu/Linux<br><br>
  2. Navigate to the ExacqVision Server directory with the cd command.

    Windows 32-bit – C:\Program Files (x86)\exacqVision\Server
    Windows 64-bit – “C:\Program Files\exacqVision\Server”
    Ubuntu – “/usr/local/exacq/server” <br><br>
  3. Enter the following command string into the CMD prompt window, replacing with the details of your SMTP server and account:
    curl smtps://url -v --mail-from "from-address@domain" --mail-rcpt "to-address@domain" -u useraccount:password -T "samplefile.txt" -k --anyauth --connect-timeout 60 --stderr
    <br><br>As an example, the above command with the proper credentials would look like the following:
    curl smtps://smtp.gmail.com:465 -v --mail-from "notifyme@gmail.com" --mail-rcpt "user@company.com" -u notifyme@gmail.com:P@ssw0rd -T "C:\Users\anyuser\Desktop\test.txt" -k --anyauth --connect-timeout 60 --stderr
    <br>Here’s an example of the text file:

    {{{
    To: user1@company.com
    To: user2@company.com
    Cc: user3@company.com
    Cc: user4@company.com
    Subject: Test subject
    Body of message.
    }}}

<br>

Notes

  • When testing on Ubuntu/Linux you must use the absolute file path to curl: (/usr/local/exacq/server/curl smtps://url...)<br><br>
  • Because this contains the -v option the output will be verbose. Any errors will be shown as well as any successes. cURL error code meanings can be found online.<br><br>
  • cURL errors can be looked up here.<br><br>
  • SMTP errors can be looked up here.

<br>

Considerations for Gmail

  • Gmail ALWAYS requires SSL. If you attempt to use without SSL, you will likely get:
    curl: (55) MAIL failed: 530<br><br>
  • With SSL, the following error is possible if Gmail is not configured with an App Password.
    curl: (67) Login denied<br><br>
  • Gmail will require an App Password be configured for ExacqVision to send notifications.

<br>