In this article

During block page setup you have the option to enter a Notice email that allows users to send feedback via embedded form to request page access, provide feedback, or request review of a filtering policy. 

These emails come from an alerts@ address with the subject “Website Block Notification.” MSP/Whitelabel customers have an option to customize this alert.

A typical email message contains:

• A block notification
• The Site and Policy that blocked the content
• Blocked domain details
• User contact information

Respond to a block page notification

Use these tips to resolve block page notifications:

• Compare the user’s requested domain against your filtering policy: visit the site to see if the content is in violation of the policy
• If the categorization is correct but your users need access for business reasons, add the site to the Allow list
• If the categorization is incorrect, report the miscategorization. Reports are typically processed in 1-2 business days. Add the domain to the Allow list to provide immediate access as needed 

‘Failed to send message, please try again’ error message

When opening the form to submit a dispute against a specific domain, users may see the following error “Failed to send message, please try again”

The most common reason this happens is that the attempt is from blocked.dnsfilter.com, (highlighted in the image above) or the block page preview. 

This is expected behavior: the form submission feature only works after visiting a specific domain. Once you visit a real blocked domain the form should send correctly.

If the “Failed to send message, please try again” error appears from a blocked domain, check these details that can trigger the error:

• Missing deployment element. Both DNS IP and web IP must be present on the Site deployment. You can find the IP address at the bottom of the block page
• Misconfigured networks. A correct DNSFilter configuration is a single Site per physical location, and each Site accepts multiple IP addresses for different network providers at that location. A common error is reversing the configuration, setting each network provider as a different Site, which leads to this error message
• Forwarding email address. Confirm the email address used for block page notifications can receive mail and isn't forwarding to another email address
• The blocked domain was idle for too long. Direct users to navigate to the blocked domain again and attempt to resend the notification