Excellent and clear to all. Thanks.
On Wed, May 26, 2010 at 11:02 AM, Thomas Eckardt <[email protected] > wrote: > >What if we changed the DoBlackDomain setting from block to score? Does > that affect the personal blacklist functionality too? > > No, personal black is "personal" and has nothing to do wtih any other > setting in assp. > > >1) Addresses on wach personal whitelist can be either > a) Listed as whitelisted for that user or > b) Listed as deleted for that user (what you're calling whitelist deny in > your last email) > 2) The personal black list is completely separate and acts the same way in > which blackListedDomains works? > > Yes. But as long as one personal white entry exists, the global will > exists (for any not personal listed user - like before the p-w-l). > > >What threw me off is the part where you said the address without the ,* > would modify the admins own entry and you said it's true of the GUI too. > Is > that no longer the case? > > I think there was a small missunderstanding between us. > The email interface must have an option to manage all (also the admins) > entries. For this reason the ',*' is used there. To be compatible with the > email interface, the GUI accepts the same syntax, but it is not needed, > because the GUI does not know the email address of the user that is logged > on. > > >Some day you'll explain to me how you consistently have the time to reply > to > my queries with such detail. Thank you. > > >From 4.30 to 7 AM - having some coffee, light on a ciggar and be rid of > the world. > > Thomas > > > > > Von: K Post <[email protected]> > An: ASSP development mailing list <[email protected]> > Datum: 26.05.2010 16:08 > Betreff: Re: [Assp-test] Personal whitelist / blacklist general > questions > > > > Some day you'll explain to me how you consistently have the time to reply > to > my queries with such detail. Thank you. > > Your reply highlighted some of my confusion. So that I'm sure that I'm > now > clear. Is it true that: > 1) Addresses on wach personal whitelist can be either > a) Listed as whitelisted for that user or > b) Listed as deleted for that user (what you're calling whitelist deny in > your last email) > 2) The personal black list is completely separate and acts the same way in > which blackListedDomains works? > > > What if we changed the DoBlackDomain setting from block to score? Does > that affect the personal blacklist functionality too? > > > Back when you requested testing assistance for the personal white feature, > you wrote: > >u...@domain,* > If the address is written without the ',*' his own entry > 'u...@domain,ad...@localdomain' will be maked as deleted. > This belongs also to the GUI. > > What threw me off is the part where you said the address without the ,* > would modify the admins own entry and you said it's true of the GUI too. > Is > that no longer the case? > > > On Wed, May 26, 2010 at 12:30 AM, Thomas Eckardt > <[email protected] > > wrote: > > > >> ----The whitelisted flag is a global flag per email - this flag will > > only > > >> be removed from an email, if all envelope do not deni the sender in > > there > > >> personal white. > > >> > > >So 1 person having it whitelisted and another blacklisted (personally), > > the > > >white will win and the email will get through to both people right? > > > > Person A has it whitelisted, Person B has it white denied - the > > whitelisted flag will be removed after the 'RCPT TO:' command. The mail > > will be processed without the 'whitelisted' flag. > > > > Person A has it whitelisted. Person B has it 'personal black listed' (it > > does not play a rule if B has it white or white deni) - the sender will > > get a '450 mailbox B unavailable' for 'RCPT TO: B' , the mail will be > not > > delivered to B but to A and it will remain whitelisted as long there is > no > > C who has it 'white denied'. > > > > >Still though, with the personal blacklist, email from a user > blacklisted > > >entry would add to the corpus? Any way to toggle that option? > > > > personal blacklisted senders will be blocked after the 'RCPT TO:' > command > > - so the mail will be never received, as long there is no other > recipient > > who wants to get the mail. > > personal black - is 'personal' , which meens that it does not belong to > > any other (global) check or score in assp. > > > > > ----Is it too much to write a ,* ? > > > > You do not need to write the ',*' to remove all entries for an address. > > Try it. The hint to the ',*' is only in the GUI to support the same > syntax > > like in the email interface where we need it (no other way). > > > > > > Thomas > > > > > > > > > > > > Von: K Post <[email protected]> > > An: ASSP development mailing list <[email protected]> > > Datum: 25.05.2010 21:44 > > Betreff: Re: [Assp-test] Personal whitelist / blacklist general > > questions > > > > > > > > Thanks as alwasy Thomas. Almost everything you said is not only > clear, > > but also how I hoped it would work. Shouldn't be a suprise - everything > > you > > seem to do makes sense... > > > > Followup questions: > > > > > > >4) Say [email protected] is whitelisted globally but > [email protected] > > has > > that address blacklisted. If [email protected] sends a single email to > > [email protected] and [email protected], will it get through to > > neither, > > both, or only user1? If blocked to user2 but not user1 will > > [email protected] still get a notification that it was blocked? > > > > > >that address blacklisted !!!! ---- "not white" meen not "black" > > > > > > Huh? You lost me on "not white meaning not black". > > > > > > > ----The whitelisted flag is a global flag per email - this flag will > > only > > > be removed from an email, if all envelope do not deni the sender in > > there > > > personal white. > > > > > So 1 person having it whitelisted and another blacklisted (personally), > > the > > white will win and the email will get through to both people right? > > > > > > > > > > I strongly recommend and request that we change the GUI > functionality. > > I > > > regularly remove 10-20 addresses from the whitelist at a time, > intending > > > to > > > remove them for everyone. It would be nice to continue being able to > > just > > > stick the addresses in there from an email header, whithout having to > > > clean > > > them up and put ,* after each. If as an admin I want to edit only my > > > personal list, I can use the email interface just like everyone else. > > > > > > If this won't work, maybe we could add a radio button to "Remove from > > > master > > > whitelist and personal whiteliststs" and let that use the old syntax > and > > > affect everyone? > > > > > > ----Is it too much to write a ,* ? > > > > > > > > Of course not, not for a single entry, but what about copying something > > from > > the headers of an email where it's like: > > To: "person name" ([email protected]), Joe [email protected], > > [email protected], [ 200 other addresses] > > > > We catch stuff like this every once in a while, where a whitelisted > sender > > has their account hijacked at hotmail. Then they send a message to 200 > > people including one of our recipients with a viagra link. When we > catch > > it, we want to remove the 200 people from the globabl whitelist. Having > > to > > edit the string of addresses is a pain. Previously we could just copy > > paste > > and ASSP would parse the string to pull out the email addresses. > > > > Would it be hard to have the code assume that removals are global from > the > > GUI unless the address,user syntax is used (in which case it would be > per > > user). > > > > > > Along the same lines, whitelist additions from the gui should go to the > > master whitelist IMO and only also go to personal whitelists if using > > email,user syntax. Why have the extra overhead if it's not necessary? > > > > > > > > > > > >6) On the personal blacklist, if some user blacklists *[email protected] > (out > > of > > > stupidity), clearly they won't get email from anyone from yahoo. > > However, > > > will this idiot mistake cause these rejected emails in the same way > that > > > the > > > master blackListedDomains does? Is so, that would allow a stupid user > > to > > > corrupt the corpus pretty quickly. This is why I changed wildcardUser > > to > > > something that no user would be able to guess. I assume that > > wildcardUser > > > is used with the personal white and blacklists too? > > > > > > >*[email protected] > > > > > > ----wildcards are not supported for this reason > > > > Still though, with the personal blacklist, email from a user blacklisted > > entry would add to the corpus? Any way to toggle that option? > > > > > > In all this sure seems like a great addition! > > Thanks > > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > Assp-test mailing list > > [email protected] > > 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 > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Assp-test mailing list > [email protected] > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-test > > ------------------------------------------------------------------------------ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
