> I just saw, in some cases the reported whitelist state was wrong reported in the GUI - the next release will fix this bug. Thank you Thomas. I'm still sorry that you found my request annoying, but I'm glad my persistence paid off.
The change to the lists gui is nothing short of fantastic. - Not only is the reporting at the top now corrected, but it's much more detailed now and far easier to read. - The delete functionality is really what I was looking for - The search functionality will help immensely when a whole slew of addresses get erroneously added (like pesky Amazon AWS one time use reply emails My suggestion for the manual part of the GUI on the lists page and anywhere you list syntax, is to remove periods at the end of the line and maybe a different font for the actual entry. For example: To add or remove a global whitelist entry, use sen...@senderdomain.org . To add or remove a domain whitelist entry, use sen...@senderdomain.org,@ localdomain.org . To add or remove a private whitelist entry, use sen...@senderdomain.org, u...@localdomain.org . To delete a global whitelist entry and all domain and private entries, use sen...@senderdomain.org,* . To delete a domain whitelist entry and all private entries, use sen...@senderdomain.org,@localdomain.org . To delete a private whitelist entry, use sen...@senderdomain.org, u...@localdomain.org . To renew an entry (e.g. extend the expriation date), add or remove it again (expiration is spelled incorrectly) simply to (no period and different font for the syntax) To add or remove a global whitelist entry, use sen...@senderdomain.org To add or remove a domain whitelist entry, use sen...@senderdomain.org,@ localdomain.org To add or remove a private whitelist entry, use sen...@senderdomain.org, u...@localdomain.org To delete a global whitelist entry and all domain and private entries, use sen...@senderdomain.org,* To delete a domain whitelist entry and all private entries, use sen...@senderdomain.org,@localdomain.org To delete a private whitelist entry, use sen...@senderdomain.org, u...@localdomain.org To renew an entry (e.g. extend the expiration date), add or remove it again I'm so used to looking at regular expressions, that when I see something like use sen...@senderdomain.org,* . (with that the trailing period) it's easy to convert that in my head to senderdomain.org,.* There are a couple other places in the GUI that would benefit from this basic change too. On Thu, Sep 26, 2019 at 9:16 AM Thomas Eckardt <thomas.ecka...@thockar.com> wrote: > >I see there is a difference between "removal" and "deletion" > > Yes there is one - and I think the difference is clearly explaned in the > manual an the GUI. > > Depending on the level of the whitelist privacy setting, there are many > different (resulting) records in the whitelist. > > action remove: > > this action marks the selected whitelist entries (DB-records) as 'NOT > whitelisted' > > this make it possible to have different whitestates for the same > senderaddress and different recipients, domains or globaly (every time > depending on the whitelist privacy level setting) > whitelist reports are giving all results - it is on the admin to know the > consequences for the used privacy level > > example: > > sender@senderdomain - whitelisted (global) > sender@senderdomain,@localdomain1 - NOT whitelisted > sender@senderdomain,@localdomain2 - whitelisted > sender@senderdomain,user1@localdomain1 - NOT whitelisted > sender@senderdomain,user2@localdomain1 - whitelisted > sender@senderdomain,user1@localdomain2 - whitelisted > sender@senderdomain,user2@localdomain2 - NOT whitelisted > > sender@senderdomain2 - NOT whitelisted (global) > sender@senderdomain2,@localdomain1 - NOT whitelisted > sender@senderdomain2,@localdomain2 - NOT whitelisted > sender@senderdomain2,user1@localdomain1 - whitelisted > sender@senderdomain2,user1@localdomain2 - whitelisted > > entries with a full recipient addresses are based on PRIVATE user requests > - removing global or domain based entries will NOT touch private entries > (global will not touch domain based) > > action delete: > > this action deletes the matching entries (DB-records) form the whitelist > database - so, deleting globalized ( ,*) records, will also delete all > other matching records (e.g. domain and private) > as notice in the GUI - deleting records can lead in to unwanted > whitelisting results for recipients and recipient domains at the configured > whitelist privacy level > > in short: > remove marks records > delete deletes records > > > I just saw, in some cases the reported whitelist state was wrong reported > in the GUI - the next release will fix this bug. > > Thomas > > > > > Von: "Daniel Miller via Assp-test" <assp-test@lists.sourceforge.net > > > An: assp-test@lists.sourceforge.net > Kopie: "Daniel Miller" <dmil...@amfes.com> > Datum: 26.09.2019 05:45 > Betreff: Re: [Assp-test] Trouble removing from whitelist (global > and personal) > ------------------------------ > > > > From EmailWhitelistRemove (and also the /Lists screen): > > Per default a removal request is processed. To delete records from > whitelistdb, write "delete" (unquoted) into the subject of the report mail. > NOTICE: removing whitelist entries will mark the records as NOT > whitelisted! > NOTICE: deleting whitelist entries will DELETE ALL related records! For > example: an emailaddress is globaly whitelisted but markted as not > whitelisted for a specific domain. Now if you DELETE the domain based > record, all domain related records will be deleted - but because of the > global whitelisting, all emailaddresses from this domain are now treated > as whitelisted! > > > I see there is a difference between "removal" and "deletion" - and > testing confirms that only "deletion" actually deletes entries from the > Whitelist database. I do not understand the purpose of "remove" instead > of "delete". Can you please expand on this? > > Daniel > > On 9/25/2019 8:28 AM, Thomas Eckardt wrote: > > RTM RTM RTM - or simply the GUI information completely > > > > 2018-05-29 > > fixed in assp 2.6.2 *Fortress* build 18148: > > > > > > changed: > > > > - admins are now able to remove global and domain based entries from > > whitelist using the emailinterface > > admins are now able to delete global and domain based database > > records from the whitelistdb using the emailinterface > > admins are now able to delete global and domain based database > > records from the whitelistdb using the webinterface (GUI) > > > > 'EmailWhitelistRemove','Remove from Whitelist Address' > > 'Any mail sent by local/authenticated users to this username will be > > interpreted as a request to remove addresses from the whitelist. Do not > > put the full address here, just the user part. > > For example: asspnotwhite > > > > EmailAdmins and EmailAdminReportsTo are able to force global or > > domain based removal and deletion requests as well as removal and > > deletion requests for other users - like: > > > > sen...@domain.org,* > > sen...@domain.org,@localdomain.org > > sen...@domain.org,otheru...@localdomain.org > > > > * Per default a removal request is processed. To delete records from > > whitelistdb, write "delete" (unquoted) into the subject of the report > > mail.* > > * NOTICE: removing whitelist entries **will mark the records**as NOT > > whitelisted!* > > * NOTICE: deleting whitelist entries will DELETE ALL related records! > > For example: an emailaddress is globaly whitelisted but markted as not > > whitelisted for a specific domain.* > > * Now if you DELETE the domain based record, all domain related records > > will be deleted - but because of the global whitelisting,* > > * all emailaddresses from this domain are now treated as whitelisted!* > > > > > > Ken, you are annoying. > > > > Thomas > > > > > > > > > > > > Von: "K Post" <nntp.p...@gmail.com> > > An: "ASSP development mailing list" <assp-test@lists.sourceforge.net> > > Datum: 25.09.2019 15:05 > > Betreff: Re: [Assp-test] Trouble removing from whitelist (global and > > personal) > > ------------------------------------------------------------------------ > > > > > > > > SUMMARY: I'm in a worse spot than I thought. I don't seem to be able to > > remove any address from the whitelist. I don't remove addresses > > frequently. I don't know how long this has been an issue. *I'm > > concerned that a verify in the list GUI shows different results that the > > address GUI and that I can't remove addresses at all it seems.* What > > could I have misconfigured? What could I be doing wrong? > > > > I've been using the lists GUI forever, long before the address icon > > became an option. I like that the lists feature shows personal lists > > and that I can do things in bulk. I also go there for tuplets. But > > your suggestion is a good one, check somewhere else. I entered that > > address into the address GUI, and incredibly, the only whitelist option > > is to add. I assume that if the address GUI has ADD to Whitelist, that > > it doesn't think an address is whitelisted. I don't know if that's > > looking at the personal whitelists too. > > > > If I enter the same thing in the lists screen, it still shows > > _scammer@gmail.com_ <mailto:scam...@gmail.com <scam...@gmail.com> > > Whitelisted > > _scammer@gmail.com_ <mailto:scam...@gmail.com > > <scam...@gmail.com>>,@OurCharity.org > personal > > Whitelisted > > _scammer@gmail.com_ <mailto:scam...@gmail.com <scam...@gmail.com> > >,oneu...@ourcharity.org > > personal not Whitelisted > > So there's conflicting information as far as I understand it. And I > > don't know what to do to fix this and figure out why it's happening. > > > > Just to see if this would fix it, from the address window, I added to > > whitelist. Then I removed from whitelist from there. I went back to > > the lists window and did a verify. Unfortunately, there's no change, it > > still shows the 3 lines above. > > > > I've never experienced /anything/ like with with ASSP before. To test > > further, I found another whitelisted address (this one was legitimate). > > I tried simply entering > > _otheraddress@outsidesender.org_ > > <mailto:otheraddr...@outsidesender.org <otheraddr...@outsidesender.org>>(I > also tried with > > _otheraddress@outsidesender.org_ > > <mailto:otheraddr...@outsidesender.org <otheraddr...@outsidesender.org>>,* > based on the gui instructions) > > I selected whitelist and remove and hit submit. > > I get a message: > > *_otheraddress@outsidesender.org_* > > <mailto:otheraddr...@outsidesender.org <otheraddr...@outsidesender.org>>* > > removed > from Whitelist* > > as I would expect. > > > > However, doing a verify still shows > > _otheraddress@outsidesender.org_ <mailto:scam...@gmail.com > <scam...@gmail.com>>, Whitelisted > > _otheraddr...@outsidesender.org _ > > <mailto:scam...@gmail.com <scam...@gmail.com>>,@OurCharity.org personal > Whitelisted > > _otheraddr...@outsidesender.org _ > > <mailto:scam...@gmail.com <scam...@gmail.com>>,us...@ourcharity.org > personal Whitelisted > > _otheraddr...@outsidesender.org _ > > <mailto:scam...@gmail.com <scam...@gmail.com>>,us...@ourcharity.org > personal Whitelisted > > > > The lists GUI says: > > To add global whitelist entries use emailaddress . > > To remove or delete global whitelist entries use emailaddress,* . > > To add, remove or delete domain whitelist entries use > > emailaddress,@domain . > > > > I usually only use the email address, not emailaddress,* to remove from > > all. Have I been using the wrong removal syntax since the introduction > > of the personal whitelists all those years ago???? Maybe so and I > > never noticed because the gui seems to say I was successful on submit. > > Verify says otherwise. > > > > > > On Tue, Sep 24, 2019 at 7:49 PM Daniel Miller via Assp-test > > <_assp-test@lists.sourceforge.net_ > > <mailto:assp-test@lists.sourceforge.net > <assp-test@lists.sourceforge.net>>> wrote: > > On 9/24/2019 9:25 AM, K Post wrote: > >> Our users got a CEO spoofing email from a Gmail address. One user > >> replied, whitelisting the gmail address. All is reported, now I just > >> want to remove the address from the whitelist. > >> > >> I can't get the address out of the whitelist. I've got no idea why. > >> I've done stuff like this for more than a decade on a regular basis. > >> Have I gone mad, is something corrupted? I'm stuck. > >> > >> I did a verify first and got: > >> > >> _scammer@gmail.com_ > > <mailto:scam...@gmail.com <scam...@gmail.com>>< > mailto:_scammer@gmail.com_ <_scammer@gmail.com_> > > <mailto:scam...@gmail.com <scam...@gmail.com>>> Whitelisted > >> _scammer@gmail.com_ > > <mailto:scam...@gmail.com <scam...@gmail.com>>< > mailto:_scammer@gmail.com_ <_scammer@gmail.com_> > > <mailto:scam...@gmail.com <scam...@gmail.com>>>,@OurCharity.org > >> personal Whitelisted > >> _scammer@gmail.com_ > > <mailto:scam...@gmail.com <scam...@gmail.com>>< > mailto:_scammer@gmail.com_ <_scammer@gmail.com_> > > <mailto:scam...@gmail.com <scam...@gmail.com>>>,oneu...@ourcharity.org > >> personal Whitelisted > > > > I admit it took me a bit to find what you're talking about - because I > > don't use the "Lists" screen. Instead - I generally use the "Address > > Actions" screen. If you know it and have already tried it then ignore > > the paragraph. > > > > Try opening the Address Actions, typing "_scammer@gmail.com_ > > <mailto:scam...@gmail.com <scam...@gmail.com>>" into the > > field, and press <TAB>. Regardless of what appears in the matches below > > - click the drop down and review the available actions. If you see, > > "Remove from Whitelist" it's still there - try submitting from this > > screen. If you see "Add to Whitelist" - the entry was deleted previously. > > > > I'm curious as to the results of the above. > > -- > > Daniel > > > > > > > > _______________________________________________ > > Assp-test mailing list_ > > __Assp-test@lists.sourceforge.net_ < > mailto:Assp-test@lists.sourceforge.net <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 > > > > > > _______________________________________________ > 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 >
_______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
