[opensuse] Starting daemons for email
Hi, I would like to know if the Postfix 'wrapper' program will start the spamd or clamd if the daemons when new email arrives, if they do not start on system boot. TIA Hylton -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hylton Conacher (ZR1HPC) wrote:
Hi,
I would like to know if the Postfix 'wrapper' program will start the spamd or clamd if the daemons when new email arrives, if they do not start on system boot.
I'm not sure what the "postfix wrapper program" is, but postfix certainly won't auto-start any spamd/clamd in the default configuration. /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Hylton Conacher (ZR1HPC) wrote:
Hi,
I would like to know if the Postfix 'wrapper' program will start the spamd or clamd if the daemons when new email arrives, if they do not start on system boot.
I'm not sure what the "postfix wrapper program" is, but postfix certainly won't auto-start any spamd/clamd in the default configuration.
OK further explanation below: I have a local IMAP mail server that I use to store my email. Mail is retrieved from my ISP POP mail a/c by Fetchmail, passed to Postfix, who in turn commands/requests spamd and clamd to inspect the incoming mail. Once they have finished with the email it is handed back to Postfix to forward onto the IMAP server software, Courier-Imap I think. The above is my understanding of how the mail server works. with local power restrictions here, I shutdown the IMAP mail server daily. On restart the following day, and watching the boot messages fly past while the system boots up, I occasionally see that Spamd or Clamd have 'Failed' i.e. are not 'Done'. What would the command be to manually start these daemons/apps/services or will Postfix start them when new email is passed to it from Fetchmail OR should I rather reboot the system and see that none of the processes/services/apps/daemons fail? Regards Hylton -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hylton Conacher (ZR1HPC) wrote:
Per Jessen wrote:
Hylton Conacher (ZR1HPC) wrote:
Hi,
I would like to know if the Postfix 'wrapper' program will start the spamd or clamd if the daemons when new email arrives, if they do not start on system boot.
I'm not sure what the "postfix wrapper program" is, but postfix certainly won't auto-start any spamd/clamd in the default configuration.
OK further explanation below: I have a local IMAP mail server that I use to store my email. Mail is retrieved from my ISP POP mail a/c by Fetchmail, passed to Postfix, who in turn commands/requests spamd and clamd to inspect the incoming mail. Once they have finished with the email it is handed back to Postfix to forward onto the IMAP server software, Courier-Imap I think.
The above is my understanding of how the mail server works.
It's a bit different: - fetchmail polls the mails from the ISP and submits them to Postfix - Postfix has a content_filter setting that feeds the mails to amavisd-new - amavisd-new is the framework that calls virus and spam scanning - after checking the mails are returned to Postfix - Postfix finally delivers the mails to the imap server (or directly to maildir) It is possible that clamd is used. That would depend on your configuration. In my case, clamd is used but will fall back to clam-scan (command line) if the daemon version is down: Apr 24 13:30:13 spamkill amavis[20655]: Using primary internal av scanner code for ClamAV-clamd Apr 24 13:30:13 spamkill amavis[20655]: Found primary av scanner H+BEDV AntiVir or CentralCommand Vexira Antivirus at /usr/bin/antivir Apr 24 13:30:13 spamkill amavis[20655]: Found secondary av scanner ClamAV-clamscan at /usr/bin/clamscan So I've got a command line version primary scanner (Avira), a daemonized version (clamd) as primary, and a command line secondary (clam-scan) if all else fails.
with local power restrictions here, I shutdown the IMAP mail server daily. On restart the following day, and watching the boot messages fly past while the system boots up, I occasionally see that Spamd or Clamd have 'Failed' i.e. are not 'Done'.
This must not happen. The system start must work reliable and be able to start all required daemons.
What would the command be to manually start these daemons/apps/services or will Postfix start them when new email is passed to it from Fetchmail OR should I rather reboot the system and see that none of the processes/services/apps/daemons fail?
Check if all required daemons are configured to start automatically: chkconfig postfix chkconfig amavis chkconfig clamd chkconfig cyrus/courier-imap/dovecot whatever... -- Sandy List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Sandy, Sandy Drobic wrote:
Hylton Conacher (ZR1HPC) wrote:
Per Jessen wrote:
Hylton Conacher (ZR1HPC) wrote:
Hi,
I would like to know if the Postfix 'wrapper' program will start the spamd or clamd if the daemons when new email arrives,
<snip>
It's a bit different:
- fetchmail polls the mails from the ISP and submits them to Postfix - Postfix has a content_filter setting that feeds the mails to amavisd-new - amavisd-new is the framework that calls virus and spam scanning - after checking the mails are returned to Postfix - Postfix finally delivers the mails to the imap server (or directly to maildir)
<snip>
...I occasionally see that Spamd or Clamd have 'Failed' i.e. are not 'Done'.
This must not happen. The system start must work reliable and be able to start all required daemons.
What would the command be to manually start these daemons/apps/services or will Postfix start them when new email is passed to it from Fetchmail OR should I rather reboot the system and see that none of the processes/services/apps/daemons fail?
Check if all required daemons are configured to start automatically:
chkconfig postfix chkconfig amavis chkconfig clamd chkconfig cyrus/courier-imap/dovecot whatever...
Thanks for that. All checked and all on. Of course further man reading told me more about the chkconfig command, and I know how how to start the relevant services that fail to start at boot. i.e. #>chkconfig <daemonname> on Would there be any notification, and where could I view it i.e. F10 or /var/log/messages, of other parent services that also need to be started, after starting a child service? Tnx Hylton -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hylton Conacher (ZR1HPC) wrote:
Thanks for that. All checked and all on. Of course further man reading told me more about the chkconfig command, and I know how how to start the relevant services that fail to start at boot.
i.e. #>chkconfig <daemonname> on
chkconfig <service name> checks whether it will start on boot. chkconfig <service name> {on/off} will set it to start/not start
Would there be any notification, and where could I view it i.e. F10 or /var/log/messages, of other parent services that also need to be started, after starting a child service?
/var/log/messages and /var/log/mail are your friends. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 04/24/2008 07:04 PM, Hylton Conacher (ZR1HPC) wrote:
OK further explanation below: I have a local IMAP mail server that I use to store my email. Mail is retrieved from my ISP POP mail a/c by Fetchmail, passed to Postfix, who in turn commands/requests spamd and clamd to inspect the incoming mail.
If procmail is used for this, it may use spamd and perhaps clamd (but I do not think so). More than likely you are describing AMaViS. This runs as a daemon, mail comes to Postfix, is sent to AMaViS, spam and virus checked (but not with the daemonized versions of spamassassin), if it passes it is sent back to Postfix for delivery, which may deliver to the mailbox or to Procmail, which may do more things or simply deliver to the mailbox.
Once they have finished with the email it is handed back to Postfix to forward onto the IMAP server software, Courier-Imap I think.
That sounds like AMaViS.
The above is my understanding of how the mail server works.
with local power restrictions here, I shutdown the IMAP mail server daily. On restart the following day, and watching the boot messages fly past while the system boots up, I occasionally see that Spamd or Clamd have 'Failed' i.e. are not 'Done'.
Spamd is redundant and you could stop it from starting. Clamd is communicated with by freshclam and AMaViS, so it is needed.
What would the command be to manually start these daemons/apps/services or will Postfix start them when new email is passed to it from Fetchmail OR should I rather reboot the system and see that none of the processes/services/apps/daemons fail?
Regards Hylton
rcspamd restart or rcclamd restart, but AMaViS doesn't use spamd. Definitely no need to reboot to start those daemons. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 04/24/2008 06:02 PM, Hylton Conacher (ZR1HPC) wrote:
Hi,
I would like to know if the Postfix 'wrapper' program will start the spamd or clamd if the daemons when new email arrives, if they do not start on system boot.
Postfix won't, but amavis will use spamassassin and clamav, but they do not need to run as daemons, only amavis needs to run as a daemon. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris wrote:
On 04/24/2008 06:02 PM, Hylton Conacher (ZR1HPC) wrote:
Hi,
I would like to know if the Postfix 'wrapper' program will start the spamd or clamd if the daemons when new email arrives, if they do not start on system boot.
Postfix won't, but amavis will use spamassassin and clamav, but they do not need to run as daemons, only amavis needs to run as a daemon.
True, if clamd is not running, amavis will use clamscan, but it's slower that way - and spamd doesn't need to run at all since amavis loads the spamassassin code directly into memory itself. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hylton Conacher (ZR1HPC) wrote:
Hi,
I would like to know if the Postfix 'wrapper' program will start the spamd or clamd if the daemons when new email arrives, if they do not start on system boot.
No, I've never heard of it being done like that - and FWIW a spamassassin/clamav startup for every incoming mail would bring a machine to it's knees in the event of any appreciable email traffic. The standard suse setup is to launch clamd and amavisd at boot. Amavisd turn loads the spamassassin libraries into memory and waits for incoming messages. Postfix passes messages to amavisd after whatever sanity checks are configured. amavisd passes the messages through clamd and spamassassin, and if clean, they are sent back to postfix for delivery to the user. It's a fairly efficient setup, our amavis servers routinely churn through several hundred messages a minute. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 24 April 2008 12:59:08 pm Sloan wrote:
Hylton Conacher (ZR1HPC) wrote:
Hi,
I would like to know if the Postfix 'wrapper' program will start the spamd or clamd if the daemons when new email arrives, if they do not start on system boot.
No, I've never heard of it being done like that - and FWIW a spamassassin/clamav startup for every incoming mail would bring a machine to it's knees in the event of any appreciable email traffic.
The standard suse setup is to launch clamd and amavisd at boot. Amavisd turn loads the spamassassin libraries into memory and waits for incoming messages.
Postfix passes messages to amavisd after whatever sanity checks are configured. amavisd passes the messages through clamd and spamassassin, and if clean, they are sent back to postfix for delivery to the user.
It's a fairly efficient setup, our amavis servers routinely churn through several hundred messages a minute.
While we are on the subject. Would someone please explain what Kmail does? Seems to be pretty efficient, Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Apr 24, 2008 at 7:06 PM, Bob S <911@sanctum.com> wrote:
On Thursday 24 April 2008 12:59:08 pm Sloan wrote:
Hylton Conacher (ZR1HPC) wrote:
Hi,
I would like to know if the Postfix 'wrapper' program will start the spamd or clamd if the daemons when new email arrives, if they do not start on system boot.
No, I've never heard of it being done like that - and FWIW a spamassassin/clamav startup for every incoming mail would bring a machine to it's knees in the event of any appreciable email traffic.
For a large server, that might be true. For a personal machine, or a mail server for a small company, its just not a problem.
The standard suse setup is to launch clamd and amavisd at boot. Amavisd turn loads the spamassassin libraries into memory and waits for incoming messages.
Spamassassin is launched by amavisd once for each email. Amavis does not use spamd/spamc. Amavisd also forces you to use site-wide bayes databases. Its a real mixed blessing. I wish the amavis developers were not so arrogant as to assume they know best.
Postfix passes messages to amavisd after whatever sanity checks are configured. amavisd passes the messages through clamd and spamassassin, and if clean, they are sent back to postfix for delivery to the user.
It's a fairly efficient setup, our amavis servers routinely churn through several hundred messages a minute.
While we are on the subject. Would someone please explain what Kmail does? Seems to be pretty efficient,
Bob: Kmail merely calls spamassassin with each message. Spamassassin simply inserts headers to indicate the spam score, and kmail accepts the revised message. Don't let Kmail do this if you are running spamassassin in the more conventional installation (in conjunction with postfix or sendmail). The kmail method works great with pop accounts. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Bob S -
Hylton Conacher (ZR1HPC) -
Joe Morris -
Joe Sloan -
John Andersen -
Per Jessen -
Sandy Drobic -
Sloan