You can, but it isn't a good approach to use on a large scale basis. I
have a similar setup in my home PC for my user. You can create a general
block by dumping mail not specifically addressed to your domain:
(Note: negative values are for lists and my personal email addresses for
mail to ALLOW. Positive values are to block specific spammers).
# The following recipe is for spam or people I don't want mail from.
:0 H
* -5^0 ^TO_.*@myisp.com
* 15^0 ^TO_.*chejugo.co.kr
* 15^0 Subject:.*Save up to 75% on International Calling
* 15^0 Subject:.*Hot and nasty cum guzzling teens!
* 15^0 from ympi@localhost
* 15^0 Message-Id:.*@baldbons
* 15^0 @jgrim
* 2^0
/dev/null
But this also blocks all mail from lists and legitimate redirected mail
including mail Bcc:'d to you by friends, so they have to be added in on an
individual basis:
* -5^0 ^TO_.*@redhat.com # List mail
* -5^0 ^TO_.*@perluser.net # Mail I have forwarded to my ISP
* -5^0 ^From.*[EMAIL PROTECTED]
As you can see doing this for all your users isn't realistic.
A more realistic approach is to modify /etc/mail/access by adding in
specific spammers as the letters come in. Here's a portion of my access
file:
localhost.localdomain RELAY
localhost RELAY
127.0.0.1 RELAY
192.168.0 RELAY
[EMAIL PROTECTED] 550 Spam is not accepted at this site
backwire.com 550 Attempts to unsubscribe from your list failed
dn.net 550 Spam is not accepted at this site
exactis.com 550 Attempts to unsubscribe from your list failed
[EMAIL PROTECTED] 550 Spam is not accepted at this site
I believe you can get a list of known spammers from the web, but I don't
know where it is.
Please DON'T use the dul filter from mail-abuse.org. It discriminates
against Linux users with dial up accounts by blocking mail sent from dial
up IP addresses - it checks the header for the IP address of the sender,
and if it is listed in the dial up IP address directory the mail is
blocked. That's like assuming that all people with green skin are
murderers (hope none of you have green skin).
Glen
On Wed, 4 Oct 2000, Eric Clover wrote:
>is there any way to use the procmailrc in /etc to block email that is
>not really sent to whom it says it should be sent to(SPAM)???
>please look at this header:
>
>Return-Path: <[EMAIL PROTECTED]>
>Received: from mx.ama.mpe.co.jp ([203.178.109.34]) by mail.nnex.net
>(8.9.3/8.8.7) with ESMTP id VAA01805 for <[EMAIL PROTECTED]>; Wed, 4 Oct
>2000 21:19:22 -0500
>Received: from host [168.191.126.152] by mx.ama.mpe.co.jp with ESMTP
>(SMTPD32-4.10) id A1CF40A01C0; Thu, 05 Oct 2000 11:00:47 +090
>From: "Kevin Brokins" <[EMAIL PROTECTED]>
>Subject: Give your Spouse a Lifetime of Income #75A6
>To: [EMAIL PROTECTED]
>X-Mailer: Microsoft Outlook Express 4.72.1712.3
>X-MimeOLE: Produced By Microsoft MimeOLE VÐßD.1712.3
>Mime-Version: 1.0
>Date: Wed, 04 Oct 2000 21:59:38 -0500
>Content-Type:
>multipart/mixed;boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0"
>Content-Transfer-Encoding: 7bit
>Message-ID: <20001005110212.SM00131@host>
>Status:
>X-Mozilla-Status: 0000
>X-Mozilla-Status2: 00000000
>X-UIDL: 37586bc300002ccd
>
>ok, to [EMAIL PROTECTED]???
>sorry, my email is [EMAIL PROTECTED]
>i have been getting these for a while
>and have about 30-50 of these kinds of emails.
>
>is there any way to send these to /dev/null if the "To:" does not match
>who it really goes to? by using procmailrc or anything that can do the
>job?
>please help.
>
>note: i work for an isp and have a large user base
>and want to be able to block this spam.
>
>thank you.
>eric
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
