Several daemons collaboratively provide mailing list service.
Bounce processing daemon.
Daemon for submitting messages to mail transfer agent (MTA). It may fork several workers as necessity.
Daemon to handle incoming messages. It may fork several workers as necessity.
Daemon to process periodical tasks.
Automatic list creation daemon.
It may be invoked by
sympa_msg.pl as necessity.
Mail transfer agent (MTA) injects incoming messages into incoming spool of Sympa, and takes outgoing messages from Sympa up to distribute them beyond Internet.
HTTP server provides users web interface on behalf of WWSympa
wwsympa.fcgi), the FastCGI server.
WWSympa may either be invoked by HTTP server or launch as an independent daemon.
Database server provides backend database for services above.
Daemons of Sympa services accept following signals:
Daemon finishes process in progress and then terminates safely.
INT signal is also recognized.
Daemon reloads configuration then continues processing.
Anyway, recommended procedure to reload, stop or start the services is described in succeeding sections.
# systemctl status 'sympa*'
# service sympa status
# systemctl restart sympa # systemctl status sympa
# service sympa restart # service sympa status
wwsympa.fcgi script was updated, it detects
change of itself and exits. Then WWSympa will be automatically reloaded.
Exception is the case running separate FastCGI service with initscripts: If script exits, it have to be restared manually by executing such as:
# service wwsympa start
To force reloading, restart HTTP server.
Exception is the case running separate FastCGI service (either with
Systemd or initscripts):
Only that service (
wwsympa) may be reloaded by
service wwsympa restart or
systemctl restart wwsympa.
Ensure that HTTP server is stopping.
If you are running separate FastCGI service, only that service
wwsympa) may be stopped
in many cases: HTTP server itself may not be stopped.
Ensure that mail server is stopping.
Stop Sympa services.
# systemctl stop sympa # systemctl status sympa
# service sympa stop # service sympa status
Database service may be stopped when all services above are stopping.
Ensure that database service is running.
Start Sympa services.
# systemctl start sympa # systemctl status sympa
# service sympa start # service sympa status
Start mail server.
Start HTTP server, if necessary.
If you are running separate FastCGI service, that service
wwsympa) must be started
along with HTTP server itself.
Theme originally designed by orderedlist