Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of me@junc.eu designates
 80.162.68.54 as permitted sender)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Jun 2013 04:25:40 +0200
From: Benny Pedersen <me@junc.eu>
To: <users@spamassassin.apache.org>
Subject: Re: Massive spamruns
Organization: Jersore Underground Network Center
In-Reply-To: 
 <CAB1R3sjvfYB6efMGiE_KUSTjq-Pc_UkE73kimogb3fSjN5m0pg@mail.gmail.com>
References: 
 <CAB1R3sjwdu+RTCPuhjzx79BMjVW_dedRS3kSw+duNZu7WaYP4Q@mail.gmail.com>
 <CDDE2E26.62385%dan.mcdonald@austinenergy.com>
 <CAB1R3sjvfYB6efMGiE_KUSTjq-Pc_UkE73kimogb3fSjN5m0pg@mail.gmail.com>
Message-ID: <41846fe4a90f63f70f38202a0018509e@junc.eu>
User-Agent: Roundcube Webmail/0.8.1

Alex skrev den 2013-06-14 00:42:

> I'm thinking this is sounding like a better option. The IPs change 
> way
> too quickly for me to be able to keep up with updating a DNSBL. It's
> funny -- despite all MXs having the same weight, mail03 is really the
> one that's pounded with these pump-and-dump spams. Maybe I'll start
> with implementing greylisting there.

try with one mx hostname that have multiple ips first

so you test with just one mx priority

-- 
senders that put my email into body content will deliver it to my own 
trashcan, so if you like to get reply, dont do it