Service Logs

This service handles GreenArrow’s TLS Certificate Configuration, allowing it to automatically obtain TLS certificates from Let’s Encrypt.

This service’s log contains information about TLS certificate registration and renewals.

The bounce processor is responsible for processing bounce messages received at Bounce Mailboxes and spam complaint notifications received at Spam Complaint Mailboxes.

See the Bounce Processor Concepts page for more information.

This service’s log contains information about each bounce message that is processed.

The Lite Bounce Processor is responsible for handling bounces and FBL complaints matched by the lite_bounce_processor_address and lite_fbl_processor_address directives.

See the Lite Bounce Processor documentation for more information.

This service periodically writes internal configuration files for use by other GreenArrow services.

This service’s log is quiet except for error messages.

This service handles execution of GreenArrow Dynamic Delivery.

This service’s log is quiet except for error messages.

This service handles parsing GreenArrow delivery logs for GreenArrow Dynamic Delivery.

This service’s log is quiet except for error messages.

This service handles execution of the Legacy Event Processor.

This service logs:

• Information about each event delivery attempt.
• Performance statistics of event delivery.

This service handles execution of the Event Processor.

This service logs:

• Diagnostics every 3 seconds.
• Performance statistics of event delivery.

This service runs the Apache HTTP Server and is responsible for all incoming HTTP and HTTPS connections.

The multilog directory for this service is quiet except for error messages.

Apache’s log files are stored in /var/hvmail/apache/logs and provide information on each incoming HTTP and HTTPS request.

This service polls (and logs) the HTTPD service’s status page every 10 seconds. This is useful for troubleshooting Apache problems.

This service polls the delivery attempt logs in order to populate the “send summary queue” files located in /var/hvmail/log/send-summary-queue.

This service’s log is quiet except for error messages.

This service processes the data generated by the Logfile Agent and populates the “send summary” files located in /var/hvmail/log/send-summary.

This service’s log is quiet except for error messages.

This service polls the delivery attempt logs in order to write to the Delivery Attempt Log and delivery_attempt events.

This service’s log is quiet except for error messages.

This service is an internal app server used for GreenArrow’s UI and API. The HTTPD service acts as a proxy between the public internet and Passenger.

This service logs:

• Information about each incoming request (under normal situations).
• Error messages/conditions (under abnormal situations).

This service runs the PostgreSQL database system.

The Postgres log can be fairly chatty with diagnostics and connection details.

This service runs the authentication agent for the FTP server. This service is normally disabled for Engine-only installations.

This service’s log is quiet except for error messages.

This service runs an FTP server. This FTP server is provided for GreenArrow Marketing Studio users to be able to upload files to be used by import features. This service is normally disabled for Engine-only installations.

This service’s log is quiet except for error messages.

This service runs GreenArrow’s POP3 server. This allows mail clients to download messages from local mailboxes.

This service logs details about incoming connections.

This service runs GreenArrow’s port 25 SMTP server.

This service logs details about incoming connections.

This service runs GreenArrow’s port 587 SMTP server.

This service logs details about incoming connections.

This service runs GreenArrow’s port 901 SMTP server (this service is disabled by default).

This service logs details about incoming connections.

This service runs GreenArrow’s RAM queue. This is the queue of first delivery attempts and is only persisted to RAM.

This service logs details about each delivery attempt.

This service runs GreenArrow’s bounce queue. This is the queue from which bounce messages are delivered.

This service logs details about each delivery attempt.

This service runs GreenArrow’s disk queue. This is the queue from which all non-first delivery attempts are tried and is persisted to disk at /var/hvmail/qmail-disk/queue.

This service logs details about each delivery attempt.

This service runs the Redis in-memory data store.

This service logs details about its persistence to disk.

This service runs the Redis in-memory data store. This service is configured to not persist to disk (it is used for performant ephemeral data that we don’t want to stream to disk).

This service’s log is quiet except for a startup message and error messages.

This service handles internal GreenArrow RPC requests.

This service’s log is quiet except for a startup message and error messages.

This service is responsible for outgoing SMTP delivery and managing delivery throttles.

This service logs:

• Details about each outgoing SMTP connection (depending on configuration such as log_smtp_connections).
• Every 5 seconds a summary of diagnostics from the delivery engine.
• Error messages.

This service is responsible for processing all email injected into Engine, except for the following:

• Messages injected from GreenArrow Marketing Studio.
• Messages injected from the HTTP Submission API.

This service’s log is quiet except for a startup message and error messages (unless the /var/hvmail/control/opt.simplemh.debug option is enabled).

This service is responsible for processing email injected into Engine via the HTTP Submission API.

This service’s log is quiet except for a startup message and error messages (unless the /var/hvmail/control/opt.simplemh.debug option is enabled).

This service is an SMTP server running on port 226. This SMTP server discards all messages injected to it.

This service logs details about each incoming connection.

This service runs all of GreenArrow Marketing Studio’s background processing. This service is normally disabled for Engine-only installations.

The Studio Worker log can be fairly chatty with diagnostics and background job details.