Re: procmail recipe not working
On Thursday 06 December 2001 17:32 pm, shock wrote: > So far, it's been *fantastic*. Mail::SpamAssassin is unbelievably > accurate, and the filter script behaves exactly as I expect it to. I've been trying to install this module from CPAN with dh-make-perl. The build fails claiming it can't find libgdbm. It also complains that I don't have the MD5 module. I think I have both. I wonder what painfully obvious thing I'm overlooking... twocups:~# dpkg -l libgdbm\* ii libgdbmg1 1.7.3-27 GNU dbm database routines (runtime version). twocups:~# dpkg -l libdigest-md5-perl ii libdigest-md5- 2.14-1 Perl interface to the MD5 Algorithm twocups:~# dh-make-perl --build --cpan Mail::SpamAssassin CPAN: Storable loaded ok Going to read /root/.cpan/Metadata Database was generated on Wed, 12 Dec 2001 08:13:03 GMT CPAN: MD5 security checks disabled because MD5 not installed. Please consider installing the MD5 module. [snip lots of pretty normai looking build stuff...] -- cc -DDEBIAN -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 spamd/spamc.c \ -o spamd/spamc -L/usr/local/lib -lgdbm -ldbm -ldb -ldl -lm -lc -lcrypt /usr/bin/ld: cannot find -lgdbm collect2: ld returned 1 exit status make[1]: *** [spamd/spamc] Error 1 make[1]: Leaving directory `/root/.cpan/build/Mail-SpamAssassin-1.5' make: *** [build-stamp] Error 2 Cannot create deb package Bud Rogers <[EMAIL PROTECTED]> All things in moderation. And not too much moderation either.
Re: procmail recipe not working
Klaus, > > SPAM=SPAM > > SPAMMERS=$HOME/procmail/spammers > > > > # Anti-spam > > :0: > > * ? (formail -x From: -x Sender: -x Reply-To: -x Received: -x > > Subject: | fgrep - iqf $SPAMMERS) . > > $SPAM /|\ > >| > > (the * ? (formail ... ) thing is all on one line) + > > > > Then you can put things like this into $HOME/procmail/spammers: > > > > End your IRS tax problems! > > [EMAIL PROTECTED] > > Be aware of the typo in the rule above, it shouldn't be a space between > the '-' and the options 'iqf', should be 'fgrep -iqf'. Thanks for the correction. One of those 80 character cut and paste errors. So it should look like: * ? (formail -x From: -x Sender: -x Reply-To: -x Received: -x Subject: | fgrep -iqf $SPAMMERS) Except all on one line. Chris -- Christopher S. Swingley phone: 907-474-2689 Computer / Network Manager email: [EMAIL PROTECTED] IARC -- Frontier ProgramGPG and PGP keys at my web page: University of Alaska Fairbanks www.frontier.iarc.uaf.edu/~cswingle "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Ben Franklin
Re: procmail recipe not working
On Fri, Dec 07, 2001 at 11:21:57AM -0900, Christopher S. Swingley wrote: | > I've been thinking of making a similar thing, just so I can list each | > spammer on one line instead of 4. | | FYI, if you do something like this in your procmail recipe file: | | SPAM=SPAM | SPAMMERS=$HOME/procmail/spammers | | # Anti-spam | :0: | * ? (formail -x From: -x Sender: -x Reply-To: -x Received: -x | Subject: | fgrep - iqf $SPAMMERS) . | $SPAM /|\ || | (the * ? (formail ... ) thing is all on one line) + | | Then you can put things like this into $HOME/procmail/spammers: | | End your IRS tax problems! | [EMAIL PROTECTED] | | I got this from someone on this list sometime in the past, so they | deserve the credit for this. Works great from here! If I keep using procmail, I need to learn formail one of these days. -D -- How great is the love the Father has lavished on us, that we should be called children of God! 1 John 3:1
Re: procmail recipe not working
On Fri, 7 Dec 2001, Christopher S. Swingley wrote: > > I've been thinking of making a similar thing, just so I can list each > > spammer on one line instead of 4. > > FYI, if you do something like this in your procmail recipe file: > > SPAM=SPAM > SPAMMERS=$HOME/procmail/spammers > > # Anti-spam > :0: > * ? (formail -x From: -x Sender: -x Reply-To: -x Received: -x > Subject: | fgrep - iqf $SPAMMERS) . > $SPAM /|\ >| > (the * ? (formail ... ) thing is all on one line) + > > Then you can put things like this into $HOME/procmail/spammers: > > End your IRS tax problems! > [EMAIL PROTECTED] > > I got this from someone on this list sometime in the past, so they > deserve the credit for this. Works great from here! > > Chris > Be aware of the typo in the rule above, it shouldn't be a space between the '-' and the options 'iqf', should be 'fgrep -iqf'. Correct me if I'm wrong BTW works great for me as well! -- GnuPG v1.0.6 Fingerprint = 67E6 1D18 B2C4 4F8A 3DA3 5C6D 849F 9F5F 26FA 477D Institute of Theoretical Astrophysics www.astro.uio.no
Re: procmail recipe not working
On Fri, 7 Dec 2001 13:40:18 -0500 dman <[EMAIL PROTECTED]> wrote: > | I did this yesterday, but had to abandon it. I got quite a few errors and > | messages sent back to the originator of the emails. This is part of my > | /var/log/exim/mainlog: > > I think this might be relevant - > http://www.exim.org/FAQ.html#SEC176 Thanks, dman. There were two problems. I had missed off the pipe symbol for formail in my procmail receipe - consequently the mail I thought was lost was actually in ~/formail - unsurprisingly. The messages sent to the sender have now been stopped by commenting out 'return_output' in my exim.conf. I appreciate your help. -- Phillip Deackes Using Debian Linux /"\ \ / ASCII RIBBON CAMPAIGN XAGAINST HTML MAIL AND NEWS / \
Re: procmail recipe not working
> I've been thinking of making a similar thing, just so I can list each > spammer on one line instead of 4. FYI, if you do something like this in your procmail recipe file: SPAM=SPAM SPAMMERS=$HOME/procmail/spammers # Anti-spam :0: * ? (formail -x From: -x Sender: -x Reply-To: -x Received: -x Subject: | fgrep - iqf $SPAMMERS) . $SPAM /|\ | (the * ? (formail ... ) thing is all on one line) + Then you can put things like this into $HOME/procmail/spammers: End your IRS tax problems! [EMAIL PROTECTED] I got this from someone on this list sometime in the past, so they deserve the credit for this. Works great from here! Chris -- Christopher S. Swingley phone: 907-474-2689 Computer / Network Manager email: [EMAIL PROTECTED] IARC -- Frontier ProgramGPG and PGP keys at my web page: University of Alaska Fairbanks www.frontier.iarc.uaf.edu/~cswingle "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Ben Franklin
Re: procmail recipe not working
On Fri, Dec 07, 2001 at 05:26:33PM +, Phillip Deackes wrote: | On Fri, 7 Dec 2001 10:43:32 +0530 | Raghavendra Bhat <[EMAIL PROTECTED]> wrote: | | > Get yourselves the razor, dman. It is very good at catching and | > reporting spam. | > | > apt-get install razor | | I did this yesterday, but had to abandon it. I got quite a few errors and | messages sent back to the originator of the emails. This is part of my | /var/log/exim/mainlog: I think this might be relevant - http://www.exim.org/FAQ.html#SEC176 -D -- Failure is not an option. It is bundled with the software.
Re: procmail recipe not working
On Thu, Dec 06, 2001 at 07:16:48PM -0500, dman wrote: > I saw a mention of a distributed spam-identification system in the > weekly news, so I'll check that out too sometime. It's razor. I just installed it, and it correctly recognised the two spam messages I had lying around in my mailbox :) Thanks Robert for the packaging, if you're reading. Chris -- Chris Halls | Frankfurt, Germany
Re: procmail recipe not working
On Fri, 7 Dec 2001 10:43:32 +0530 Raghavendra Bhat <[EMAIL PROTECTED]> wrote: > Get yourselves the razor, dman. It is very good at catching and > reporting spam. > > apt-get install razor I did this yesterday, but had to abandon it. I got quite a few errors and messages sent back to the originator of the emails. This is part of my /var/log/exim/mainlog: 2001-12-06 19:20:57 16C44j-MI-00 <= [EMAIL PROTECTED] H=localhost [127.0.0.1] P=esmtp S=421565 [EMAIL PROTECTED] 2001-12-06 19:20:59 16C44j-MI-00 ** |/usr/bin/procmail -f- <[EMAIL PROTECTED]> D=userforward T=address_pipe: return message generated 2001-12-06 19:21:00 16C44q-MP-00 <= <> R=16C44j-MI-00 U=mail P=local S=107584 2001-12-06 19:21:00 16C44j-MI-00 Error message sent to [EMAIL PROTECTED] 2001-12-06 19:21:00 16C44j-MI-00 Completed 2001-12-06 19:21:00 16C44q-MP-00 == [EMAIL PROTECTED] routing defer (-45): domain is in queue_remote_domains 2001-12-06 19:23:01 Start queue run: pid=1395 2001-12-06 19:23:13 16C44q-MP-00 => [EMAIL PROTECTED] R=smarthost T=remote_smtp H=smtp.ntlworld.com [62.253.162.40] 2001-12-06 19:23:13 16C44q-MP-00 Completed 2001-12-06 19:23:13 End queue run: pid=1395 2001-12-06 19:31:10 16C4Eg-Mf-00 <= [EMAIL PROTECTED] H=localhost [127.0.0.1] P=esmtp S=2545 [EMAIL PROTECTED] 2001-12-06 19:31:10 16C4Eg-Mf-00 ** |/usr/bin/procmail -f- <[EMAIL PROTECTED]> D=userforward T=address_pipe: return message generated 2001-12-06 19:31:11 16C4Eh-Mm-00 <= <> R=16C4Eg-Mf-00 U=mail P=local S=3625 2001-12-06 19:31:11 16C4Eg-Mf-00 Error message sent to [EMAIL PROTECTED] 2001-12-06 19:31:11 16C4Eg-Mf-00 Completed 2001-12-06 19:31:11 16C4Eh-Mm-00 == [EMAIL PROTECTED] routing defer (-45): domain is in queue_remote_domains 2001-12-06 19:38:02 Start queue run: pid=1418 2001-12-06 19:38:04 16C4Eh-Mm-00 => [EMAIL PROTECTED] R=smarthost T=remote_smtp H=smtp.ntlworld.com [62.253.162.40] 2001-12-06 19:38:04 16C4Eh-Mm-00 Completed 2001-12-06 19:38:04 End queue run: pid=1418 2001-12-06 19:53:01 Start queue run: pid=1425 2001-12-06 19:53:01 End queue run: pid=1425 2001-12-06 20:01:42 16C4iE-Nu-00 <= [EMAIL PROTECTED] H=localhost [127.0.0.1] P=esmtp S=4386 [EMAIL PROTECTED] 2001-12-06 20:01:42 16C4iE-Nu-00 ** |/usr/bin/procmail -f- <[EMAIL PROTECTED]> D=userforward T=address_pipe: return message generated 2001-12-06 20:01:42 16C4iE-O1-00 <= <> R=16C4iE-Nu-00 U=mail P=local S=5466 2001-12-06 20:01:42 16C4iE-Nu-00 Error message sent to [EMAIL PROTECTED] 2001-12-06 20:01:42 16C4iE-Nu-00 Completed I have a .forward file like this: # Exim filter <<== do not edit or remove this line! if error_message then finish endif logfile $home/eximfilter.log if $h_To: contains "[EMAIL PROTECTED]" then deliver scott elif $h_To: contains "sah1" then deliver scott else pipe "/usr/bin/procmail -f-" endif And a .procmailrc like this: # Augment $PATH as necessary. PATH=/usr/local/bin:$PATH ORGMAIL=/var/spool/mail/$LOGNAME DEFAULT=$ORGMAIL :0 Wc razor-check :0 Waf formail -i "Subject: Razor Warning: SPAM/UBE/UCE" I have posted about this to the razor-user list, but maybe a fellow debian user might be more helpful. Thanks for any help you can give. -- Phillip Deackes Using Debian Linux /"\ \ / ASCII RIBBON CAMPAIGN XAGAINST HTML MAIL AND NEWS / \
Re: procmail recipe not working
On Fri, Dec 07, 2001 at 12:20:29AM +, Pollywog wrote: | On 2001.12.06 22:18 dman wrote: | > On Thu, Dec 06, 2001 at 09:01:36PM +, Pollywog wrote: | | > | Maybe Procmail is in a different place than you set in your | > | procmailrc. | > | > What do you mean by this? I also have a long list of other spammer | > addresses in that same file, and those others get filed properly. | | Nevermind then :) Actually, Those other recipes are also spam blockers. I figured they were working since I hadn't seen that bit of spam since I added the recipes. Now that I've gotten some of that pesky spam that wouldn't filter again, I checked the logs and did a little bit of testing. I previously had INCLUDERC=$HOME/util/procmailrc/spam I checked the manpage again, and tried INCLUDERC=util/procmailrc/spam and INCLUDERC util/procmailrc/spam I also just included the whole file (via vim's :read command). Including the recipes in ~/.procmailrc worked. Apparently it is a problem with my INCLUDERC usage. Any pointers? (I do have ~/util/procmailrc/spam) -D -- Microsoft: "Windows NT 4.0 now has the same user-interface as Windows 95" Windows 95: "Press CTRL-ALT-DEL to reboot" Windows NT 4.0: "Press CTRL-ALT-DEL to login"
Re: procmail recipe not working
[Thu, Dec 06, 2001 at 07:16:48PM -0500] dman :
> I saw a mention of a distributed spam-identification system in the
> weekly news, so I'll check that out too sometime.
Get yourselves the razor, dman. It is very good at catching and
reporting spam.
apt-get install razor
--
ragOO, VU2RGU<->http://gnuhead.dyndns.org/<->GPG: 1024D/F1624A6E
Helping to keep the Air-Waves FREE Amateur Radio
Helping to keep your Software FREE the GNU Project
Helping to keep the W W W FREE Debian GNU/${kernel}
Re: procmail recipe not working
On Thu, Dec 06, 2001 at 01:17:30PM -0800, Craig Dickson wrote: | dman wrote: ... | > :0 | > * [EMAIL PROTECTED] | > /dev/null | > | > However the messages keep getting past these recipes and to my | > list-matching recipe. | | Those look like they ought to work. One thing, though I doubt it's | causing your problem, is that you ought to be escaping literal dots with | a backslash. So the first recipe should look like this: Right, but I figured it was close enough (what's the chance a legitimate address will match that re because of the dots?) and easier to copy-n-paste from the mails. | Verbose logging may help to figure out what's going on. I hope. For the frequency with which the messages arrive, I haven't seen one in my log yet (since I started it logging). -D -- He who finds a wife finds what is good and receives favor from the Lord. Proverbs 18:22
Re: procmail recipe not working
On Thu, Dec 06, 2001 at 05:28:02PM -0700, Gary Hennigan wrote: | dman <[EMAIL PROTECTED]> writes: ... | > I've been thinking of making a similar thing, just so I can list each | > spammer on one line instead of 4. | | You do know that you can use a logical "OR" in your rules right? The | "|" symbol. Actually, it is an "alternation" in regex terminology, not "logical or". Same principle though (and I tend to say "or" in my head when I write it). | For example, | | :0 | * ^From:.*junker.home|^To:[EMAIL PROTECTED]|^Cc:[EMAIL PROTECTED] | /dev/null | | Would cover three addresses that would go to /dev/null. | | Perhaps you're doing something automated that makes this difficult? No, I just didn't want to have one several-thousand-character-long-line in my file (well, my list isn't that long yet, but it will likely grow). As a side effect, alternation tends to sap quite a bit more CPU resources for an NFA engine and more memory for a DFA enging (see the O'Reilly book for a somewhat-detailed-yet-still-simplfied explanation). -D -- (E)very (M)inor (A)ttention (C)osts (S)anity
Re: procmail recipe not working
* dman ([EMAIL PROTECTED]) spake thusly: > On Thu, Dec 06, 2001 at 05:32:48PM -0600, shock wrote: > > | i had the same problem with a different spammer. no matter what i did, > | i simply could not get the procmail recipe to properly filter the > | thing. > > at least I'm not a freak ;-) nope, just a procmail user. ;) and procmail recipies are too damned difficult. franky, filtering email simply should *not* be that hard. > | don't get me wrong, i still use procmail. i modified my .procmailrc to > | call a perl filter script i wrote using Mail::Audit and > | Mail::SpamAssassin. Now, rather than stumbling around with procmail's > | recipes, I just filter based on the power of Perl. > > I've been thinking of making a similar thing, just so I can list each > spammer on one line instead of 4. i thought about it long and hard before i finally took the plunge and wrote the script. i can't begin to describe how happy i am with the results. to *finally* be able to filter through perl . . . something i understand . . . email me privately, if you want, and i'll email you my perl script ad the necessary modifications to procmail. -- ) ,_),_) (-(__ |_ _ _ |/ ) | |(_)(_ |\ ( \_, ___ | http://www.exitwound.org : hard to find | ___ | Chocolate chip. | ___ -BEGIN GEEK CODE BLOCK- | Version: 3.1 | | GJ/IT d- s: a C+++>$ UL P+++ L+++ E--- W++| | N+@ o K- w O- M- V PS+ PE Y+ PGP++ t+@ 5@ X++ | | R tv+@ b+ DI D+ G++ e h r+++ y+++ | --END GEEK CODE BLOCK--
Re: procmail recipe not working
dman <[EMAIL PROTECTED]> writes: > On Thu, Dec 06, 2001 at 05:32:48PM -0600, shock wrote: > | On 2001.12.06 20:23 dman wrote: > | > > | > I've been getting a bunch of spam on a certain list. The latest > | > message has the following From: line : > | > | i had the same problem with a different spammer. no matter what i did, > | i simply could not get the procmail recipe to properly filter the > | thing. > > at least I'm not a freak ;-) > > | i finally gave up and ditched procmail recipes altogether. > | > | don't get me wrong, i still use procmail. i modified my .procmailrc to > | call a perl filter script i wrote using Mail::Audit and > | Mail::SpamAssassin. Now, rather than stumbling around with procmail's > | recipes, I just filter based on the power of Perl. > > I've been thinking of making a similar thing, just so I can list each > spammer on one line instead of 4. You do know that you can use a logical "OR" in your rules right? The "|" symbol. For example, :0 * ^From:.*junker.home|^To:[EMAIL PROTECTED]|^Cc:[EMAIL PROTECTED] /dev/null Would cover three addresses that would go to /dev/null. Perhaps you're doing something automated that makes this difficult? Gary
Re: procmail recipe not working
On 2001.12.06 22:18 dman wrote: On Thu, Dec 06, 2001 at 09:01:36PM +, Pollywog wrote: | Maybe Procmail is in a different place than you set in your | procmailrc. What do you mean by this? I also have a long list of other spammer addresses in that same file, and those others get filed properly. Nevermind then :)
Re: procmail recipe not working
On Thu, Dec 06, 2001 at 05:32:48PM -0600, shock wrote: | On 2001.12.06 20:23 dman wrote: | > | > I've been getting a bunch of spam on a certain list. The latest | > message has the following From: line : | | i had the same problem with a different spammer. no matter what i did, | i simply could not get the procmail recipe to properly filter the | thing. at least I'm not a freak ;-) | i finally gave up and ditched procmail recipes altogether. | | don't get me wrong, i still use procmail. i modified my .procmailrc to | call a perl filter script i wrote using Mail::Audit and | Mail::SpamAssassin. Now, rather than stumbling around with procmail's | recipes, I just filter based on the power of Perl. I've been thinking of making a similar thing, just so I can list each spammer on one line instead of 4. I saw a mention of a distributed spam-identification system in the weekly news, so I'll check that out too sometime. -D -- Windows, hmmm, does it come with a GUI interface that works or just pretty blue screens?
Re: procmail recipe not working
On 2001.12.06 20:23 dman wrote: > > I've been getting a bunch of spam on a certain list. The latest > message has the following From: line : i had the same problem with a different spammer. no matter what i did, i simply could not get the procmail recipe to properly filter the thing. i finally gave up and ditched procmail recipes altogether. don't get me wrong, i still use procmail. i modified my .procmailrc to call a perl filter script i wrote using Mail::Audit and Mail::SpamAssassin. Now, rather than stumbling around with procmail's recipes, I just filter based on the power of Perl. So far, it's been *fantastic*. Mail::SpamAssassin is unbelievably accurate, and the filter script behaves exactly as I expect it to. -- ) ,_),_) (-(__ |_ _ _ |/ ) | |(_)(_ |\ ( \_, ___ | http://www.exitwound.org : hard to find | ___ | Mankind is poised midway between the gods | | and the beasts. -- Plotinus | ___ -BEGIN GEEK CODE BLOCK- | Version: 3.1 | | GJ/IT d- s: a C+++>$ UL P+++ L+++ E--- W++| | N+@ o K- w O- M- V PS+ PE Y+ PGP++ t+@ 5@ X++ | | R tv+@ b+ DI D+ G++ e h r+++ y+++ | --END GEEK CODE BLOCK--
Re: procmail recipe not working
On Thu, Dec 06, 2001 at 09:01:36PM +, Pollywog wrote: | On 2001.12.06 20:23 dman wrote: | > | > I've been getting a bunch of spam on a certain list. The latest | > message has the following From: line : | > | > From: "Lisa J." <[EMAIL PROTECTED]> | > | > (some have a different name, but the same address) I want to | > automatically file these in the bit-bucket. Should be | > straightforward, right? In my .procmailrc I have the following : ... | > However the messages keep getting past these recipes and to my | > list-matching recipe. | | Turn on verbose logging to see why they are getting past. (now why didn't I think of that?) I just turned on the logfile so I should see stuff the next time one of them comes through (I already deleted the other ones so I can't bounce it to myself) | Maybe Procmail is in a different place than you set in your | procmailrc. What do you mean by this? I also have a long list of other spammer addresses in that same file, and those others get filed properly. -D -- (E)very (M)inor (A)ttention (C)osts (S)anity
Re: procmail recipe not working
dman wrote: > I've been getting a bunch of spam on a certain list. The latest > message has the following From: line : > > From: "Lisa J." <[EMAIL PROTECTED]> > > (some have a different name, but the same address) I want to > automatically file these in the bit-bucket. Should be > straightforward, right? In my .procmailrc I have the following : > > :0 > * ^From:.*reply.pm0.net > /dev/null > > :0 > * [EMAIL PROTECTED] > /dev/null > > :0 > * ^From:[EMAIL PROTECTED] > /dev/null > > > However the messages keep getting past these recipes and to my > list-matching recipe. Those look like they ought to work. One thing, though I doubt it's causing your problem, is that you ought to be escaping literal dots with a backslash. So the first recipe should look like this: :0 * ^From:.*reply\.pm0\.net /dev/null Otherwise the regexp code will interpret the dots as the "any character" wildcard. Which, of course, should still match successfully for these messages, so it doesn't explain why the recipes are failing. Verbose logging may help to figure out what's going on. Craig
Re: procmail recipe not working
On 2001.12.06 20:23 dman wrote: I've been getting a bunch of spam on a certain list. The latest message has the following From: line : From: "Lisa J." <[EMAIL PROTECTED]> (some have a different name, but the same address) I want to automatically file these in the bit-bucket. Should be straightforward, right? In my .procmailrc I have the following : :0 * ^From:.*reply.pm0.net /dev/null :0 * [EMAIL PROTECTED] /dev/null :0 * ^From:[EMAIL PROTECTED] /dev/null However the messages keep getting past these recipes and to my list-matching recipe. Turn on verbose logging to see why they are getting past. Maybe Procmail is in a different place than you set in your procmailrc. -- Andrew
procmail recipe not working
I've been getting a bunch of spam on a certain list. The latest message has the following From: line : From: "Lisa J." <[EMAIL PROTECTED]> (some have a different name, but the same address) I want to automatically file these in the bit-bucket. Should be straightforward, right? In my .procmailrc I have the following : :0 * ^From:.*reply.pm0.net /dev/null :0 * [EMAIL PROTECTED] /dev/null :0 * ^From:[EMAIL PROTECTED] /dev/null However the messages keep getting past these recipes and to my list-matching recipe. Any clues? TIA, -D -- A)bort, R)etry, B)ang it with a large hammer
