Noticed problems after auto-updated to 3.0.1.9

Report bugs and workarounds
Post Reply
maxkmv
Posts: 53
Joined: 28 Apr 2015 14:40

Noticed problems after auto-updated to 3.0.1.9

Post by maxkmv »

Came to office this Monday and have the following problems with EFA after auto-update to 3.0.1.9

1) Adding new values to White/Black Lists spawns this error after clicking on Add button:
"Error: unable to validate security token"


(cleaned all history and cookies from Chrome, yet still persists even for newer messages that were just received)
The error happens nearly every time. Usually I click Back button in Chrome, re-add to list and it works from second (sometimes third) attempt.

UPDATE: This seems to be happening only when I am trying to add from 2 separate windows.. doesn't seem to happen when you add only using one open Chrome window. (Previously I could add dozens of addresses nearly simultaneously by opening 10 Chrome windows...but now it is taking considerably longer using this new approach..)

2) Clicking "Add to White / Blacklist" opens the lists but occasionally doesn't display address in From or Domain field. Athough in message details there is definitely a valid address/domain. So have to manually Copy/Paste it. Not a big deal but when working with hundreds of addresses every hour it eats valuable time.

UPDATE: I noticed this only happens when address is something very long, e.g.: From: 64-74-9688127.ljeymc40my4xnzg-pm-1-1-29929-216-oaquc5771@sdufsd88.vip

3) Occasionally webinterface just won't let me in at all - an error comes up "Error: unable to validate security token" even when I am presented with Login page and I type correct username/password. Usually closing EVERY open window in Chrome and re-launching it again resolves it, but inconvenient as I have to close all my open sessions with other websites. When reopening Chrome it just goes straigt to webinterface without asking for username/password again!

4) Occasionally when trying to click on Add to Whitelist/Blacklist (both for domain and IP address) the following error comes up: "Forbidden, you don't have permission to access /mailscanner/lists.php on this server." The only way to resolve this is to close Chrome completely and reopen.

5) Some filters don't work any more and that is a BIG ISSUE for me. For example, when I select "is Blacklisted greater than "" - previously it would show me all blacklisted ones, but not anymore! When I click Add button it simply doesn't create that filter. It's first time I started to think that I should revert back to previous version and disable auto-update. Guys PLEASE HELP!!!

6) Web-interface sporadically logs out without possibility to log back in (dreadful "security token" error)... This sometimes happens twice in 5 mins... Really annoying as have to close all open Chrome windows again... grrrr..

7) Today I couldn't add one specific domain to blacklists: @createchsuk.co.uk - I click add and it just says "Forbidden, you don't have permission to access /mailscanner/lists.php on this server." I can add other domain names but not this one - for completely unexplained reasons.
User avatar
shawniverson
Posts: 3783
Joined: 13 Jan 2014 23:30
Location: Indianapolis, Indiana USA
Contact:

Re: Noticed problems after auto-updated to 3.0.1.9

Post by shawniverson »

I will be tackling all of these issues and plan to release 3.0.2.0 this weekend. I would like to have you give it a try once it goes live and provide us feedback.
User avatar
shawniverson
Posts: 3783
Joined: 13 Jan 2014 23:30
Location: Indianapolis, Indiana USA
Contact:

Re: Noticed problems after auto-updated to 3.0.1.9

Post by shawniverson »

I spent considerable time on this post to identify these issues and resolve. Look forward to you trying 3.0.2.0 in your environment and see if this issues are resolved for you.
Post Reply