>I have a bunch of general questions about the relatively new personal whitelisting / blacklisting feature. I hppe that this is the start to a small thread where we can have a discussion on this and then come up with a quick explanation summary post which I'll do at the end to benefit the rest of the admins out there who might need clarification. We could also stick this in the admin interface.
>The main question is if [email protected] sends in a whitelist request via the admin interface what exactly happens? Is the address whitelisted for everyone still but also put on ouruser1's personal whitelist so that if it's removed it remains with ouruser1? ----YES. The global entry will be only removed if the last personal white is removed. Also: >1) Does personal whitelisting only happen via the email interface or if [email protected] simply emails [email protected] will that address also go to user1's personal whitelist? ----YES. >2) Along those lines, would [email protected] now be whitelisted for everyone like it used to be before personal whitelisting? I hope so and that user2 could blacklist it if necessary. ----YES. - notice theat personal white has nothing to do with the personal black >3) Let's say that [email protected] is whitelisted (global). Before personal whitelisting, if [email protected] sent an email to [email protected] with a cc to [email protected], [email protected] would be whitelisted. What happens with personal whitelisting - would [email protected] ONLY be whitelisted for [email protected]? ----NO. As long one personal white exists, the global will exist. ----Existing global whites will only be removed, if the last personal white is denied or it is too old. >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" ----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. 5) I see that in the GUI we can now do: [email protected],* to remove that address from everyone's whitelist. Is the ,* required? ----YES if you want to "remove that address from everyone's whitelist" I know Thomas wrote: If a admin wants to remove all records (also the global one) for a address via email-interface, he should use the following syntax: 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. 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 ,* ? >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 I hope this stuff hasn't been clearly answered elsewhere - I've searched but haven't found direct answers. Thanks 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
