Test a Sensor

After the first Sensor has been installed and can connect to Fortra Cloud Email Protection, you can send a test email directly to the Sensor.

Because the Sensor is listening for SMTP conversations on the port you specified in the installation script, it is possible to inject a test message directly to the Sensor. If you can telnet to the SMTP port you configured in the installation script and you are comfortable issue SMTP commands directly, you can create a test message:

$ telnetsensor_name:sensor_port

Trying IP_address...

Connected to sensor_name

 

Escape character is '^]'.

220 collector-milter ESMTP Postfix

HELO example.com

250 collector-milter

MAIL FROM: <test@example.com>

250 2.1.0 Ok

RCPT TO: user@yourcompany.com

DATA

354 End data with <CR><LF>.<CR><LF>

 

Received: from 1.2.3.4 by test.example.com

Received: from 192.168.3.3. by internal

From: "John Smith" <jsmith@example.com>

To: "Jane Doe" <jdoe@example.net>

Subject: test message sent from manual telnet session

Date: Wed, 11 May 2011 16:19:57 -0400

Message-Id: <testing-testing>

 

Hello World,

This is a test message sent from a manual telnet session.

 

Yours truly,

SMTP administrator

.

250 2.0.0 Ok: queued as message_ID

quit

Be sure that the message DATA contains a Received: header. Entering a “.” character on its own line will end the data command. The “250 2.0.0. Ok: queued as…” command means that your test message was accepted successfully, and the Sensor is ready to accept messages routed from your dual delivery configuration.

Troubleshooting Test Email

If you get an error message similar to this after entering the MAIL FROM: line:

>451 4.7.1 Service unavailable - try again later

…it is likely the Sensor is not up and running yet. Try:

  • Look at the /var/log/agari/container.log on the host to see if you can find a line similar to:
  • Feb 01 2017 05:07:59 INFO collector-milter is ready.

    If not, the milter process has not started up yet. Wait a few more minutes and try again.

  • Has it been more than five minutes since you've started the Sensor?
  • If not, wait the full five minutes and then restart the container if the milter has still not started:

    $ /opt/agari/bin/agari-ep restart

  • If after restarting the container there is still an issue, consider restarting the entire Sensor:
  • $ sudo service agari-collector restart