GMX script (2015-03-20) is buggy

By Kono14 , 23 March 2015

The GMX.net script (with navigator) from 2015-03-20 is not working properly. It works only for a few hours, after I cleared all GMX coookies. But after a while the mail notification for GMX turns red and stops working. Something in the cookies must be causing this. Because when I clear all GMX cookies again, it works fine.

Could you have a second look at this script?

Forums
Script Request

RpD

11 years 3 months ago

I have a trivial nitpick... "not working properly" is not the same as "buggy".
'Buggy' implies bad programming... whereas 'not working' can be because some login factor was overlooked, omitted.
Either way, it may not work properly. 

 

Kono14

11 years 3 months ago

Unfortunately this problem is very persistent. I have to delete all gmx cookies at least one time per day, sometimes two times. It's super annoying. 

Is there anything I should provide to help solving this?

tobwithu

11 years 3 months ago

I want to fix this.

But the problem is that I cannot reproduce this.

How long is your check interval?

Kono14

11 years 3 months ago

My check intervall is only 1min, which always worked just fine for the many years that I used X-Notifier with GMX. 

I think the issue with the 2015-03-20 script has something to do with a timeout. Because when I clear my cookies in the morning it works fine for the rest of the day, when I'm at home and have my PC & Chrome running all day. The problem only appears on the next mornig, after my PC was in hibernate for like 9 hours. I also have to say, I never close my browser window and never restart or shutdown my PC. I just leave the browser open and hibernate when I leave my house. 

But sure, I will test the 2015-03-25 script and report back.

Kono14

11 years 3 months ago

After my last post I deleted all gmx cookies, installed the 2015-03-25 script and now, only a few hours later without any hibernate/standby inbetween, the script stopped working again. This is causing the problems:

http://www.imgbox.de/users/public/images/qIhY9oirjn.PNG

I have 71 of these session id cookies, accumulated in only 3-4h. Somehow you have to stop the script from creating new sessions. but rather use the existing session cookies. (if that makes any sense)

Kono14

11 years 3 months ago

I tested the 2015-03-26 script. It worked yesterday at first, I saw only one session id cookie. But later that day it stopped working again, the session id cookies got stacked up till 113.

http://www.imgbox.de/users/public/images/UOxuycAWqi.png

My sister and a friend use X-Notifier in combinatin with this GMX script as well. They have exactly the same problems. Both of them use 1min check intervall too. I just wonder why not more people complain about this?! The script got downloaded nearly 1000 times, in little more than 24h. 

I'm not telling you what to do, but just suggesting trying something different to see what happens....

What if you change your check interval (not the "Default check interval")  ...to perhaps 3 minutes? Maybe it would not have the same problem/effect.  This would also give the developer more information to work with...

A one minute interval would be known as 'hammering the server'... some mail providers will not allow that short of an interval. Microsoft enforces an interval of about 15 minutes. 

Kono14

11 years 3 months ago

I tried 3min and even 10min check intervall. Sadly that doesn't help, problem is still remains the same. 

But also, I like to get Email notifications right away, like IMAP push notifications on my Android phone. So 1min check intervall was just right, not true push notifications, but as close as it gets. And like I said, I have been using X-Notifier and it's predecessor WebMail Notifier for many years. Always with GMX and always with 1min check intervall. The last major script version was from September 2013, up until now this worked just perfect.