-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In a recent thread I saw mention of using a "lock" file with spamassasin. I don't use fetchmail, procmail etc (at least nothing that I've configured) , just lowly kmail to download and read my mail. (don't have time or the need to learn about fetchmail, procmail etc, right now). I set up a filter in kmail to use spamc to sort out spam mails and its working well - except for the horrible slowdown while spamc does its job. I've read the spamassasin docs but I don't see any info about how to setup a "lock" file, especially in conjunction w/ kmail. Can this be done with kmail? If so how. Part of the thread discussing lock files is quoted below... On Wednesday 27 August 2003 01:52 pm, H du Plooy wrote:
On Wed, 2003-08-27 at 20:51, Dylan wrote:
# The lock file ensures that only 1 spamassassin invocation happens # at 1 time, to keep the load down. #
:0fw: spamassassin.lock
# # Limit size to 250 KB * < 256000 # # Use spamc
| spamc -d 127.0.0.1 -f -u <your_user_name>
Where do I find that? I've looked through the files in /usr/share/spamassassin and /etc/mail but can't find those lines anywhere?
This is all supposed to be in your ~/.procmailrc
As I'm only using kmail I have no ~/.procmailrc file. Thanks - -- dh Don't shop at GoogleGear.com! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/UkdIBwgxlylUsJARAp73AJ9LlckPvDF+e1RoeVO20suQtpjViwCdHkNG 2Jqi1d5bVZDUpMuLBtmp8RM= =Vhx7 -----END PGP SIGNATURE-----
--Z:wse1o,YLnKw'=. Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sun, 31 Aug 2003 12:06:48 -0700 David Herman <mesamoo115@attbi.com> wrote:
I've read the spamassasin docs but I don't see any info about how to setup a "lock" file, especially in conjunction w/ kmail.
This is not the job of spamassassin (on a dedicated mail server you certain want more than 1 mail processed at a time). It is the job of the Kmail (in your case) to limit the copies of spamc being run concurrently.
Can this be done with kmail? If so how.
Don't know, haven't used Kmail in a long time. Maybe you will have better luck on suse-kde. If it can't be done, you should consider file a bug report/feature request at bugs.kde.org. Charles -- "MSDOS didn't get as bad as it is overnight -- it took over ten years of careful development." (By dmeggins@aix1.uottawa.ca) --Z:wse1o,YLnKw'=. Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/Ula+3epPyyKbwPYRAmC9AKCWtRJbrrSPQdFKY86f9OwgsprRYgCffsrb jdOotRVgd9i1/XEEjufdMIQ= =to6X -----END PGP SIGNATURE----- --Z:wse1o,YLnKw'=.--
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 31 August 2003 01:12 pm, Charles Philip Chan wrote:
On Sun, 31 Aug 2003 12:06:48 -0700
David Herman <mesamoo115@attbi.com> wrote:
I've read the spamassasin docs but I don't see any info about how to setup a "lock" file, especially in conjunction w/ kmail.
This is not the job of spamassassin (on a dedicated mail server you certain want more than 1 mail processed at a time). It is the job of the Kmail (in your case) to limit the copies of spamc being run concurrently.
I'm sure that is why the documentation leans towards procmail et al. I assume that kmail really doesn't expect to wait for another program to work and this is causing the windo to not refresh.
Can this be done with kmail? If so how.
Don't know, haven't used Kmail in a long time. Maybe you will have better luck on suse-kde.
Thanks for the help - -- dh Don't shop at GoogleGear.com! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/U1CfBwgxlylUsJARAkT2AJ98TM+JhypNP4K0onuHwQeq79vTDwCfVwXe UODIUXGe+NmqdPjGy0GIveQ= =WFYS -----END PGP SIGNATURE-----
On 2003-08-31, David Herman wrote:
I set up a filter in kmail to use spamc to sort out spam mails and its working well - except for the horrible slowdown while spamc does its job.
Hi David! I don't use KMail but I did have this very same problem in my configuration, what changed all that for me was putting my trusted recipients as whitelisted in ./spamassassin/user_prefs like that: whitelist_to *@suse.com whitelist_to *@mutt.org for example. All mailing lists and the trusted addresses you receive the most mail from don't need to be filtered by SpamAssassin, it takes a lot of time to chew. Cheers, Helgi Örn -- /// Helgi Örn Helgason, Registered Linux User: #189958 \\\ \\\ ~~~~ SuSE 8.2 * Kernel 2.4.20-4GB * KDE 3.1.3 ~~~~ ///
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 31 August 2003 09:44 pm, Helgi Örn Helgason wrote:
On 2003-08-31, David Herman wrote:
I set up a filter in kmail to use spamc to sort out spam mails and its working well - except for the horrible slowdown while spamc does its job.
Hi David! I don't use KMail but I did have this very same problem in my configuration, what changed all that for me was putting my trusted recipients as whitelisted in ./spamassassin/user_prefs like that: whitelist_to *@suse.com whitelist_to *@mutt.org for example. All mailing lists and the trusted addresses you receive the most mail from don't need to be filtered by SpamAssassin, it takes a lot of time to chew.
Thanks for the tip, I'll try it. I was under the impression that by having spamassasin as my last filter (second to last) all of my other filters would have done their jobs so there would only be a few messages left for spamassasin to check. The main problem is that when spamassasin (spamc) goes to work then kmail refuses to refresh its window (and allow me to continue reading mail) until the filter process finishes, perhaps there is a way I can run spamc at a lower priority/higher nice value? thanks again for your idea - -- dh Don't shop at GoogleGear.com! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/U09KBwgxlylUsJARAkHQAJ9yuaWTKnGvuovqHleWKsf+xUEpbgCePRiw IvsYoVF5V4tuM60OuTabV3U= =1r4P -----END PGP SIGNATURE-----
participants (4)
-
Charles Philip Chan -
David Herman -
David Herman -
Helgi Örn Helgason