Jump to content

Recommended Posts

Posted
We are having a weird time with our smoothwall at the moment, where its emailing out blank safe guarding notifications. When looking in safeguarding reports, it is also showing as blank. Looking in the web logs for the user, nothing looks untoward. I have logged it with smoothwall, but expect its going to be a while before anyone contacts me back. Honestly driving my dsl and pastoral team mad.
Posted
We sometimes get random entries where the notification email is blank for that entry only on a browser and on the report page of the Smoothwall but shows correctly on a mobile mail client.
Posted
Weird - is the Smoothwall up to date? We did have a formatting issue some time back which was corrected. When you get the blank email, is it blank or is it white on white e.g.?
Posted

This is Leeds-46 for us - the other entries in the email are all as expect but then one is totally blank when viewed on a PC or on the Smoothie's report page but is visible fine on a mobile client.

 

The text doesn't appear to even be there - I've tried highlighting it to see etc.

Posted
Weird - is the Smoothwall up to date? We did have a formatting issue some time back which was corrected. When you get the blank email, is it blank or is it white on white e.g.?
The table for the report and username is there, but no url or category set. Same in the safeguarding reports. We are on the latest Leeds 47.
Posted
Any specific tags or type of entry - user search or 'just' a URL?

 

Here is a screen shot of the email:

Email sreenshot.PNG

 

Here is the screenshot of what it looks like in Safeguarding report:

Smoothwall screenshot.PNG

Posted
Hmm, obviously a parser issue there - no time discernible on anything? Was thinking to go hunting for the actual log entry so see what it was.
Posted
Its not happening to all of the notifications, but most are showing like this. Looking through the web logs, I can't find anything that would have caused the notification.
Posted
Smoothwall support have fixed my issue. Turns out there was a bug between scanning and reporting, where adverts were causing the safeguarding breach, but the reporting engine was excluding the adverts. Which cleared the results.
  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...