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

Reply via email to