started over with 3.0.0.1 works fine, then upgraded again to 3.0.0.6
SAME Problem. click on any messages after upgrade to 3.0.0.6 and they are blank when you open them up
Mailwatch BLANK after clicking on messages
Re: Mailwatch BLANK after clicking on messages
*testing posting privileges - hopefully this goes through*
I think this is all tied in with the GEOIP piece being broken in 3.0.0.6 - should be fixed in 3.0.0.7 though if I'm reading correctly.
Temp workaround that solved my problem:
go into /var/www/html/mailscanner/temp and delete geoip.*
Simple as that.
*edit* and ok then.. I thought my posting privileges weren't going to be active until my 'introduction post' went through.. show's what I know.
I think this is all tied in with the GEOIP piece being broken in 3.0.0.6 - should be fixed in 3.0.0.7 though if I'm reading correctly.
Temp workaround that solved my problem:
go into /var/www/html/mailscanner/temp and delete geoip.*
Simple as that.
*edit* and ok then.. I thought my posting privileges weren't going to be active until my 'introduction post' went through.. show's what I know.
Re: Mailwatch BLANK after clicking on messages
Yep confirmed as issue.
I guess there are just way to many EFA systems out there that are downloading the GEOIP data from maxdata so they blocked the access.
We will find a way to distribute it from the EFA-Project servers.
I guess there are just way to many EFA systems out there that are downloading the GEOIP data from maxdata so they blocked the access.
We will find a way to distribute it from the EFA-Project servers.
Version eFa 4.x now available!
Re: Mailwatch BLANK after clicking on messages
While not as elegant as an auto-download, I'm thinking this would be more future proof:
Can the users be told where to download the files then prompted with an upload dialog from EFA?
Even if you move the files to the efa-project domain and re-point the auto update to the new location it would be a good backup option in the event the auto-download still fails or servers go offline.
Can the users be told where to download the files then prompted with an upload dialog from EFA?
Even if you move the files to the efa-project domain and re-point the auto update to the new location it would be a good backup option in the event the auto-download still fails or servers go offline.