+Reloading configuration without restarting
+When running in watch mode, parsedmarc supports reloading its
+configuration file without restarting the service or interrupting
+report processing that is already in progress. Send a SIGHUP signal
+to the process, or use systemctl reload if the unit file includes
+the ExecReload line shown above:
+sudo systemctl reload parsedmarc
+
+
+The reload takes effect after the current batch of reports finishes
+processing and all output operations (Elasticsearch, Kafka, S3, etc.)
+for that batch have completed. The following settings are reloaded:
+
+All output destinations (Elasticsearch, OpenSearch, Kafka, S3,
+Splunk, syslog, GELF, webhooks, Log Analytics)
+Multi-tenant index prefix domain map (index_prefix_domain_map —
+the referenced YAML file is re-read on reload)
+DNS and GeoIP settings (nameservers, dns_timeout, ip_db_path,
+offline, etc.)
+Processing flags (strip_attachment_payloads, batch_size,
+check_timeout, etc.)
+Log level (debug, verbose, warnings, silent)
+
+Mailbox connection settings (IMAP host/credentials, Microsoft Graph,
+Gmail API, Maildir path) are not reloaded — changing those still
+requires a full restart.
+On a successful reload, existing output client connections are
+closed and new ones are created from the updated configuration. The
+service then resumes watching with the new settings.
+If the new configuration file contains errors (missing required
+settings, unreachable output destinations, etc.), the entire reload
+is aborted — no output clients are replaced and the previous
+configuration remains fully active. This means a typo in one section
+will not take down an otherwise working setup. Check the logs for
+details:
+journalctl -u parsedmarc.service -r
+
+
To check the status of the service, run:
service parsedmarc status
@@ -756,6 +799,7 @@ as well as the current process (newest to oldest), run:
+