John Hardin <jhar...@impsec.org> wrote:

> On Wed, 4 Mar 2009, Andrzej Adam Filip wrote:
>
>>> This would be an entirely different application, not SA, wouldn't it?
>>
>> It can be developed using the same "spam score" logic, based subset of
>> all tests requiring only the subset of "final data" available during
>> "classic run".
>
> So in other words something like SMTP-time DNSBL tests that score
> points towards rejection rather than being pass/fail? That sounds like
> a good idea.
>
>> I do think that promoting tools that encourage postmaster to care very
>> much about mail server (IP address) reputation can make real difference
>> e.g. caring to be above reputation "none" in DNSWL to avoid grey-listing.
>
> Agreed. But, performing major redesign of SA to achieve this pre-RCPT
> is going to be a tough sell.
>
>>> Well, this probably could be done in SA using a multi-level protocol
>>> capable of returning values at different stages. However, this seems
>>> perfectly suited for a lightweight tool, rather than a hog that is
>>> designed to scan and process entire messages. :)
>>
>> During initial tests/deployment *much* simpler implementation can be
>> used with recommended action based on spam score:
>>
>> It would require redesign of 50_scores.cf structure.
>>  e.g. instead of
>>    score RCVD_IN_DNSWL_HI 0 -8 0 -8
>>  something like that
>>    # N - Network, B - Bayes, nX - no X, R - "RCPT TO:"
>>    score RCVD_IN_DNSWL_HI nNnB=0 NnB=-8 nNB=0 NB=-8 R=-8
>>  or shorter
>>    score RCVD_IN_DNSWL_HI N=-8 R=-8
>
> Why would SA be served by _major_ modifications like this, rather than
> writing a new milter that focuses on determining the reputation of an
> IP? Are you really willing to break _all_ existing SA installations
> for this?
>
> Please don't try to make SA a "do everything" tool, you'll likely
> weaken what it does an outstanding job of today.

0) Such _major_ modification means introducing it in next _major_
   spamassassin release unless it can be made "downward compatible"
   e.g. by using *separate* "score file" for at "RCPT TO:" tests.

   Where there's a Will, there's a way

1) I want milter(s) (MIMEDefang's filtering script in perl) to use
   spamassassin in such role. I personally prefer such tools from teams
   with well established "maintenance reputation". I also believe that
   SA "score tuning methodology" would fit very well too.
2) Anyway limiting scores to *only* four cases *SHOULD NOT* "stay forever".

-- 
[pl>en: Andrew] Andrzej Adam Filip : a...@onet.eu
"All the people are so happy now, their heads are caving in.
I'm glad they are a snowman with protective rubber skin"
  -- They Might Be Giants

Reply via email to