Re: spamassassin - three basic questions
On 21 Feb 2003, Glyn Millington wrote: Levi Waldron [EMAIL PROTECTED] writes: I actually find spamassassin runs pretty slowly on my K6-2/500MHz 384MB machine (I know it's not real fast but not a dinosaur either). It takes about 5-10 seconds per message, so before I started filtering my debian-user messages before processing, it was prohibitive. Have you tried running it as a daemon? That speeds things up and reduces the load on the system. It doesn't speed things up all that much for me. What does speed them, however, is to use the L switch to allow local checking only. This does allow a few more spam messages to get through but I can live with that. It still catches most of them. AC -- [EMAIL PROTECTED]|| http://www.acampbell.org.uk using Linux GNU/Debian || for book reviews, electronic Windows-free zone || books and skeptical articles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
On Sat, Feb 22, 2003 at 11:12:16AM +0530, Sandip P Deshmukh wrote: On Fri, Feb 21, 2003 at 02:34:16PM +, Colin Watson wrote: On Fri, Feb 21, 2003 at 06:59:45PM +0530, Sandip P Deshmukh wrote: 1.how to i tell spamassassin *not to* process some messages? for instance, debain mailing list, i understand, is already processed for spam. no use spamming it again Rearrange your exim filter so that it delivers such messages directly to the appropriate mailbox before the part that calls spamassassin. some confusion here. here is my exim filter (relevant portions): [...] if i understand correctly, my .forward file (exim filter) checks for x-spam-status. this is updated by spamassassin. so is it that all mail that is processed by exim filter is processed by spamassassin anyway? in that case, even if i move my mailing list items out in the beginning of the exim filter, it wont make a difference as the exim filter is processing mails *after* they are processed by spamassassin. Oh. Well, you can't, then. You'll have to use procmail instead to make that work; I gave an example of what should be a working .procmailrc with spamassassin earlier. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
* Sandip P Deshmukh [EMAIL PROTECTED] [2003-02-21 14:47]: 1.how to i tell spamassassin *not to* process some messages? for instance, debain mailing list, i understand, is already processed for spam. no use spamming it again whitelist 2.how do i tell spamassassin *not to* convert all attachments into inline material? retain the structure, just add the tag in subject line? procmail 3.how do i tell spamassassin, here, if the message is from a certain sender, it is not spam - irrespctive of what you think and if a message is from some other sender, it is spam - irrespctive of what you think? blacklist procmail wbr, Lukas -- Lukas Ruf http://www.lpr.ch Wanna know anything about raw ip? Join [EMAIL PROTECTED] on http://www.rawip.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
On Fri, Feb 21, 2003 at 06:59:45PM +0530, Sandip P Deshmukh wrote: 1.how to i tell spamassassin *not to* process some messages? for instance, debain mailing list, i understand, is already processed for spam. no use spamming it again Rearrange your exim filter so that it delivers such messages directly to the appropriate mailbox before the part that calls spamassassin. 2.how do i tell spamassassin *not to* convert all attachments into inline material? retain the structure, just add the tag in subject line? See Mail::SpamAssassin::Conf(3pm). Try unsetting defang_mime. 3.how do i tell spamassassin, here, if the message is from a certain sender, it is not spam - irrespctive of what you think and if a message is from some other sender, it is spam - irrespctive of what you think? See Mail::SpamAssassin::Conf(3pm). Use whitelist_from. Cheers, -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
At 2003-02-21T13:29:45Z, Sandip P Deshmukh [EMAIL PROTECTED] writes: Assuming that SpamAssassin is configured to read per-user settings from ~/.spamassassin/user_prefs, edit that file to add: 1. how to i tell spamassassin *not to* process some messages? for instance, debain mailing list, i understand, is already processed for spam. no use spamming it again whitelist_from *@lists.debian.org 2.how do i tell spamassassin *not to* convert all attachments into inline material? retain the structure, just add the tag in subject line? defang_mime 0 3. how do i tell spamassassin, here, if the message is from a certain sender, it is not spam - irrespctive of what you think and if a message is from some other sender, it is spam - irrespctive of what you think? whitelist_from blacklist_from Read `man Mail::SpamAssassin::Conf' for more information. -- Kirk Strauser In Googlis non est, ergo non est. msg32134/pgp0.pgp Description: PGP signature
Re: spamassassin - three basic questions
On Fri, Feb 21, 2003 at 09:11:00AM -0600, Kirk Strauser wrote: At 2003-02-21T13:29:45Z, Sandip P Deshmukh [EMAIL PROTECTED] writes: 1. how to i tell spamassassin *not to* process some messages? for instance, debain mailing list, i understand, is already processed for spam. no use spamming it again Maybe not necessary, but, unless your mailserver is horribly slow, it'll be done so quick that it's not going to hurt anything anyhow. whitelist_from *@lists.debian.org That was my first thought, but, if you look at the headers of this message, you will see From: Dave Sherohman [EMAIL PROTECTED] Although I haven't tested it, I would not expect spamassassin to start checking other headers to see if they match whitelist_from directives. Also, even if this works, it does not prevent spamassassin from scanning the message, which is what Sandip appears to want. Whitelisting someone just causes sa to subtract 100 from the score of their messages. -- The freedoms that we enjoy presently are the most important victories of the White Hats over the past several millennia, and it is vitally important that we don't give them up now, only because we are frightened. - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
On February 21, 2003 11:24 am, Dave Sherohman wrote: Maybe not necessary, but, unless your mailserver is horribly slow, it'll be done so quick that it's not going to hurt anything anyhow. I actually find spamassassin runs pretty slowly on my K6-2/500MHz 384MB machine (I know it's not real fast but not a dinosaur either). It takes about 5-10 seconds per message, so before I started filtering my debian-user messages before processing, it was prohibitive. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
Levi Waldron [EMAIL PROTECTED] writes: I actually find spamassassin runs pretty slowly on my K6-2/500MHz 384MB machine (I know it's not real fast but not a dinosaur either). It takes about 5-10 seconds per message, so before I started filtering my debian-user messages before processing, it was prohibitive. Have you tried running it as a daemon? That speeds things up and reduces the load on the system. Glyn -- Debian Home http://www.debian.org Debian Planet http://www.debianplanet.org/ For the children http://www.debian.org/devel/debian-jr/ In a hurry??? http://qref.sourceforge.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
On Fri, Feb 21, 2003 at 12:16:37PM -0500, Levi Waldron wrote: On February 21, 2003 11:24 am, Dave Sherohman wrote: Maybe not necessary, but, unless your mailserver is horribly slow, it'll be done so quick that it's not going to hurt anything anyhow. I actually find spamassassin runs pretty slowly on my K6-2/500MHz 384MB machine (I know it's not real fast but not a dinosaur either). It takes about 5-10 seconds per message, so before I started filtering my debian-user messages before processing, it was prohibitive. That sounds unreasonably slow to me, too. I currently run two mailservers, a P3/1GHz 256M at work and a Athlon 900 256M at home. Both are scanning all inbound mail using spamd. Looking over the logs, I see that I'm running at 0 seconds for about 85% of messages and 1 second for almost all the rest. I bet you're not running spamd, which means you're taking the hit for starting up perl on every message scanned. That would hurt pretty bad, now that I think about it... -- The freedoms that we enjoy presently are the most important victories of the White Hats over the past several millennia, and it is vitally important that we don't give them up now, only because we are frightened. - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
Dave Sherohman wrote: On Fri, Feb 21, 2003 at 09:11:00AM -0600, Kirk Strauser wrote: At 2003-02-21T13:29:45Z, Sandip P Deshmukh [EMAIL PROTECTED] writes: 1. how to i tell spamassassin *not to* process some messages? for instance, debain mailing list, i understand, is already processed for spam. no use spamming it again Maybe not necessary, but, unless your mailserver is horribly slow, it'll be done so quick that it's not going to hurt anything anyhow. 'not necessary' is debateable. For whatever reason, half the spam that spamassassin catches for me is directed to debian lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
On February 21, 2003 01:13 pm, Dave Sherohman wrote: I bet you're not running spamd, which means you're taking the hit for starting up perl on every message scanned. That would hurt pretty bad, now that I think about it... You're correct. I'm using kmail to fetch from POP3 mailservers and pipe each message individually through spamassassin -P -a. I didn't realize that using spamd would be so much faster. I could switch to fetchmail for the sake of spamd, although reading through the documentation I see that the spamc daemon could also improve my performance without changing my mail setup at all. I'll give that a try first, and report back... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
On Fri, Feb 21, 2003 at 02:49:25PM +0100, Lukas Ruf wrote: * Sandip P Deshmukh [EMAIL PROTECTED] [2003-02-21 14:47]: 1. how to i tell spamassassin *not to* process some messages? for instance, debain mailing list, i understand, is already processed for spam. no use spamming it again whitelist is this a separate program? will you please elaborate? 2. how do i tell spamassassin *not to* convert all attachments into inline material? retain the structure, just add the tag in subject line? procmail i do not use this. i use .forward exim filter instead. will it do? or will i have to necessarily use procmail? 3. how do i tell spamassassin, here, if the message is from a certain sender, it is not spam - irrespctive of what you think and if a message is from some other sender, it is spam - irrespctive of what you think? blacklist procmail wbr, what is that? a complete newbie here! -- regards, sandip p deshmukh --*** Acquaintance, n: A person whom we know well enough to borrow from but not well enough to lend to. A degree of friendship called slight when the object is poor or obscure, and intimate when he is rich or famous. -- Ambrose Bierce, The Devil's Dictionary -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
On Fri, Feb 21, 2003 at 02:34:16PM +, Colin Watson wrote:
On Fri, Feb 21, 2003 at 06:59:45PM +0530, Sandip P Deshmukh wrote:
1. how to i tell spamassassin *not to* process some messages? for
instance, debain mailing list, i understand, is already processed for
spam. no use spamming it again
Rearrange your exim filter so that it delivers such messages directly to
the appropriate mailbox before the part that calls spamassassin.
some confusion here. here is my exim filter (relevant portions):
# Exim filter
# move all spam
if
$h_X-Spam-Status: contains Yes
or
${if def:h_X-Spam-Flag {def}{undef}} is def
then
save $home/nvnt/spm
finish
endif
# move all mailing list mail to mlst folder
if $h_to: contains lists.debian.org or
$h_cc: contains lists.debian.org or
then
save $home/nvnt/mlst
finish
endif
# move everything else to nvn
save $home/eptr/nvn
finish
if i understand correctly, my .forward file (exim filter) checks for
x-spam-status. this is updated by spamassassin. so is it that all mail
that is processed by exim filter is processed by spamassassin anyway? in
that case, even if i move my mailing list items out in the beginning of
the exim filter, it wont make a difference as the exim filter is
processing mails *after* they are processed by spamassassin.
2. how do i tell spamassassin *not to* convert all attachments into
inline material? retain the structure, just add the tag in subject line?
See Mail::SpamAssassin::Conf(3pm). Try unsetting defang_mime.
3. how do i tell spamassassin, here, if the message is from a
certain sender, it is not spam - irrespctive of what you think and if a
message is from some other sender, it is spam - irrespctive of what you
think?
See Mail::SpamAssassin::Conf(3pm). Use whitelist_from.
one more question. i have read time and again the documentation that
comes with spamassassin. i am unable to decide location of configuration
files. the documentation says that per user settings are a security hole
for users can get root access if spamd is run. i do run spamd and dont
want to have any security holes although i am the only user of the
system. does that mean that i will have to defang mime and whitelist,
etc. in systemwide file? what file do i have to edit? i havent modeified
any spamassassin configuration file as yet.
one more thing, if i understand documentation correctly, inorder to stop
spamassassin from processing some mails (question 1), i may have to do
whitelist_to in the configuration file?
thanx for all the help. i think after i get this clear, my spamassassin
setup will be the way i want it :)
--
regards,
sandip p deshmukh
--***
There are no emotional victims, only volunteers.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
On Fri, Feb 21, 2003 at 09:11:00AM -0600, Kirk Strauser wrote: At 2003-02-21T13:29:45Z, Sandip P Deshmukh [EMAIL PROTECTED] writes: Assuming that SpamAssassin is configured to read per-user settings from ~/.spamassassin/user_prefs, edit that file to add: this is interesting. i have an /etc/default/spamassassin that reads like this (relevant portions): # Change to one to enable spamd ENABLED=1 # Options OPTIONS=-F 0 -m 3 as you can see, i have enabled spamd. the other options are for some from header (this i borrowed directly from dman site) and -m 3 restricts child processes to 3. this prevents too much build up of system load. i also read the documentation. it mentions that per-user settings is a security risk if spamd is run. so, i will prefer not to allow per user settings although i am the only user of the system. what file to i edit if per user settings are not allowed? thanx for your help. i am only one answer away from getting spamassassin to work the way i want to. one last question - this may be off topic. i am sure, there will be several newbies like me who face the same problem on setting up spamassassin. is there a website where i can post my experiences, hoping they are useful for others? -- regards, sandip p deshmukh --*** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: spamassassin - three basic questions
On Fri, Feb 21, 2003 at 02:01:19PM -0500, Travis Crump wrote: 1. how to i tell spamassassin *not to* process some messages? for instance, debain mailing list, i understand, is already processed for spam. no use spamming it again Maybe not necessary, but, unless your mailserver is horribly slow, it'll be done so quick that it's not going to hurt anything anyhow. well, i have read some documents and they are talking about a few seconds of processing per message of an average size. in fact, spamd came up to ease the burden on resources if i understand correctly. one more point, if a small setting is going to save even a small resource, why not? :) -- regards, sandip p deshmukh --*** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
