On Wed, 6 Aug 2003 01:23:56 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
> On Sun, 3 Aug 2003 19:46:25 +0200 (CEST) Robert Vazan > <[EMAIL PROTECTED]> wrote: > > RV> I am talking about that challenge/response spam filter I mentioned > when I > RV> first came here. > > I've just seen it in action after writing to you directly :-( Annoying. Yes, but it filters *all* spam and loses *no* personal mail (in theory). People do confirm autoresponses and I am willing to reply to messages sent by other people's autoresponders. > Right, but this is not a simple filter, it's a rather complicated system > (especially when you have to handle all the errors which can occur along > the way somehow). By "simple" I meant that there is a point in development when the filter can be considered finished. Heuristic filters are never finished and they must be in separately developed program like SpamAssasin. It isn't that much code anyway. It's mostly about doing it right. Most of the extra code comes from making it fast enough to search megabytes of filtered messages (I personally never delete anything). > What exactly is needed for this challenge/response? If we write a rule > to > run an external program (or just revive Python support to make it again > possible to write filter tests in Python), it could be used to check > whether the senders address is already in your whitelist. If it's not, we > could also have a filter action which would send a challenge message > (and, > presumably, move the message to some "Queue" temporary folder). This sort of filter must not be done manually by users. It's not only wasted duplicate effort (and consequently demotivating), it's extremely dangerous. Mail loops, autoresponses to lists, "you dirty spammer" messages, ignoring other autoresponders, multiple mail addresses (on either end), subfolder addresses, un/wanted daemon errors, different sent and recognized password, forgetting to do manual tasks. There is a million ways to do it wrong. That's why I want it smoothly integrated. > a) recognize the incoming response to your challenge (how??) I am using password, which is easy to match in procmail, but C++ filter should use message identifiers too. Btw, that confirmation you sent me was lacking password (it was empty message) and I didn't see it. I added you to whitelist anyway and found your messages in autoresponse archive. > b) delete it and move the message (which one??) from "Queue" back to > Inbox I don't delete anything. I currently find filtered messages manually, but this should be automated. They can be identified by source address and possibly also by message id and subject. > I don't see how are you going to do it and I really think that the only > way to do it reliably is at MTA level, it is too late to do it in the > MUA... I don't quite undestand why do you think so. I certainly cannot do anything with the Exchange server that receives mail for this IP address. Even if remote MTA supports procmail, there is no easy way to automate it and, as I said before, procmail/shell is too unreliable for this task. ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
