Am 26.05.2011 23:28, schrieb Ulrich Kautz:
> Hello Thomas
>
> Thanks for your feedback.
>
>> after a bit of reading on the project site, there is one thing, i see a
>> little bit critical:
>>
>> On the "about" page there is a "Simple Setup" example. In this you describe:
>> - Postfix accepts and receives (or rejects) the mail and delivers it to the
>> Detective.
>> - The Detective might reject the mail, which will force postfix to bounce
>> it, or passes it again and re-inject it into another postfix process.
>>
>> I i understand this right, postfix would bounce the mail after it was
>> accepted for delivery. This would cause backscatter.
>> And a backscattering spamfilter is as bad as a real spamserver.
>
> Ok, that was not lucid, i agree. I clarified this on the about page,
> respectively left it the reject-part out to prevent misunderstandings.
> However, the Detective server actually can bounce the mail, if he is
> configured to do so in the spam.handle directive. There are four different
> handlers:
> 1) tag: Default handle. Mail will be tagged (with a X-Decency-header and
> possibly a Subject-header prefix, if configured).
> 2) ignore: Nothing happens to the mail. For testing (and log analysis).
> 3) delete: Mail will be silently deleted. I clarify that this is not a good
> idea in the docu. However, there is the possibility to send a mail to the
> recipient ("You received SPAM, we deleted it").
> 4) bounce: The recognized SPAM mail is bounced back to the sender. The valid
> scenario for this is an outbreak-prevention mailserver in which the sender
> wants to know whether the mail he send himself would be recognized as SPAM.but none of the cases REJECTS spam-mails the spamfilter has to answer with 5xx to the sending server 1) and 2) does finally nothing 3) MUST NOT happen 4) SHOULD NOT happen
signature.asc
Description: OpenPGP digital signature
