Login proccess speed #73

[svencc]

Now we do not load all stores on startup. This should help a bit to improve startup performance, but more improvements don´t seem to be possible. It´s up to ExtJS that so many things have to be loaded.

[piwats]

Thanks a lot. That is definitely a good improvement.

Now the login process is very instantly :)

[svencc]

Great ;) Am 06.07.2014 01:14 schrieb "piwats" notifications@github.com:

Thanks a lot. That is definitely a good improvement.

Now the login process is very instantly :)

— Reply to this email directly or view it on GitHub https://github.com/teqneers/Greyface/pull/77#issuecomment-48098769.

[piwats]

Hello Sven,

I noticed today, that the per-user Greylis stopped working. I will test it further to be assured that this is a bug.

Is it possible, that this is related to the login-speed-improvement?

-Paul

[svencc]

What exactly is not working anymore?

• Is there no user-list at all?
• Or is the greylist not loaded if you select a user?

[piwats]

Hi,

when I am logged in as a normal user, (not as admin), the greylist ist completely empty. (that was not the case before) When I am logged in as the admin, I see the greylist, and also adressess mapped to the user correctly (that is what #72 was about, right?)

[svencc]

I think now I know whats the Problem.

If you are logged in as a normal user and you have mails which are sent to an alias of you, you don´t see them in your greylist.

right?

[piwats]

Nope, unfortunately: if user's email address is user@example.com and if the same address is set as the user's address then greyface used to show all those sender email addresses which intended to deliver to the user's email address.

normal is if bad-sender@spammmmm.org wants to send to user@example.com, than afterwards user@example.org gets to see only those senders in in the greyface greylist, which really were intended for him.

Now there is a completely empty list in the user's greyface greylist. Admin's one is filled as ever :)

I have not played with aliases yet...

[svencc]

Hi, unfortunatly I cannot reproduce this behaviour on my machine. But I have an idea.

Please go in your /greyface.ini file and activate the both options in the [application] section by removing the leading ";" characters:

[application] ;Defines if the error logging to /Greyface/log/greyface.log should be activated logging = true ;Defines if errors will be shown in the returne JSON objects which the server will send back displayErrors = true

Then go in the subfolder/file /log/greyface.log

Now errors will be logged to this file and there will be outputs to your brwosers javascript console. Please test now again if there are any errors messages.

Unfortunatly I did not implemented timestamping to the greyface.log, so please empty the file first and check than if there are any errors.

I will open a new ticket for improving error logging in the next minutes.

Please give me than some feedback

[svencc]

now i added timestamps to the logging (greyface.log), so it should be easier to find the issues.

[svencc]

ah wait, i found the error - please test

[piwats]

Hello and thank you very much :)

Now it works without any problems.

-Paul