From owner-freebsd-security@FreeBSD.ORG Thu May 13 14:48:39 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EF9916A4CE for ; Thu, 13 May 2004 14:48:39 -0700 (PDT) Received: from redix.it (host49-169.pool8172.interbusiness.it [81.72.169.49]) by mx1.FreeBSD.org (Postfix) with SMTP id 7D81643D46 for ; Thu, 13 May 2004 14:48:33 -0700 (PDT) (envelope-from roberto@redix.it) Received: (qmail 26779 invoked by uid 72); 13 May 2004 21:48:31 -0000 Received: from 151.31.34.32 (SquirrelMail authenticated user roberto) by mail.redix.it with HTTP; Thu, 13 May 2004 23:48:31 +0200 (CEST) Message-ID: <3063.151.31.34.32.1084484911.squirrel@mail.redix.it> In-Reply-To: <1886.213.112.193.11.1084410012.squirrel@mail.hackunite.net> References: <1886.213.112.193.11.1084410012.squirrel@mail.hackunite.net> Date: Thu, 13 May 2004 23:48:31 +0200 (CEST) From: roberto@redix.it To: freebsd-security@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Re: How do fix a good solution against spam.. X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2004 21:48:39 -0000 > Heya folks > > First of all, sorry if this isn't the correct list, but yet, I think spam > is a kind of network attack and should be treated as a security issue.. > I run a working mail server using Postfix, MySQL, Courier-IMAP, >SpamAssassin and ClamAV (amavisd-new) ... > Regards, > Jesper Wallin > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to > "freebsd-security-unsubscribe@freebsd.org" > I'm trying to solve the spam problem on my email server too. I'm glad to share my and your ideas on the topic. At the moment I can suggest the following: 1) use Realtime Black List (see http://spamhaus.org for example); 2) use Sender Policy Framework (see http://spf.pobox.com); 3) accept email only after the sender had confirmed your reply; 4) use spamassasin; N.B.: only 1,2 save your bandwidth as the SMTP transaction is blocked if necessary; Any comments are welcome, Regards, Roberto