I think we all speeking about different things! >So, the 99 users who believe that the message is black
I speek about the Whitelist - (not black, blue or yellow ....) . If a there is a negative personal entry in the Whitelist, this meens only, that the sender is not whitelisted for this recipient - nothing else. >So, the 99 users who believe that the message Until now, all have to live with the decission of one person, that an address is whitelisted. Thomas Von: Маллиндайн Стивен (Steve Mallindine) <st...@sc.ru.ru> An: GrayHat <gray...@gmx.net>, ASSP development mailing list <assp-test@lists.sourceforge.net> Datum: 04.05.2010 17:33 Betreff: Re: [Assp-test] test for personal whitelist wanted So, the 99 users who believe that the message is black should each add a rule (in the case of outlook/exchange) or add to personal BL because of 1 minority guy who believes it should be white? (And in the case of multiple recepients, this 1 guy wouldn't get it anyway) Sorry, but it reminds me of Spock... 'the needs of the many out-weighs the needs of the few...or the one' However, I do think there's a good solution somewhere (that fits all scenarios)... We just haven't found it yet :) What if: when multiple receipents are received, each is checked in whitelist for sender/recepient match. If matched, put into whitelist array, if not, blacklist array. Then, the message could be passed for the whitelist array, dropped for the blacklist array. Just a thought. Steve Sent from my iPhone On 04.05.2010, at 14:25, "GrayHat" <gray...@gmx.net> wrote: >>> someone doesn't want to receive some messages (s)he may just add >>> a given sender to his/her personal BL (which will probably be >>> smaller) > >> But this (personal blacklist) is provided by every mail client - or >> not? > > That's different; if you do it at client level then you'll have to > accept the > incoming email and then let the client handle it; also, and since we > are > at it, a personal whitelist (or blacklist) may be "cool" but I wonder > how > it may impact on the ASSP corpus, see, let's say 100 users decided > that a given email is JUNK and ONE decided it's fine and he wants it, > now, ASSP will be forced to accept such a message and it will end > up in the notspam corpus... and this in turn may *pollute* it > > > --- > --- > --- > --------------------------------------------------------------------- > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-test ------------------------------------------------------------------------------ _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test DISCLAIMER: ******************************************************* This email and any files transmitted with it may be confidential, legally privileged and protected in law and are intended solely for the use of the individual to whom it is addressed. This email was multiple times scanned for viruses. There should be no known virus in this email! *******************************************************
------------------------------------------------------------------------------
_______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
