Currently a static filter restrictions is determined from "handle-user-access" configuration

<handle-user-access>true|false</handle-user-access>

• if true the user is taking into account to display the content (not cacheable filter)
• if false the limitation of content's pages should be the same as the current page

When there is no current page (case of static filter, newsletter) the content should be available to anonymous user to be displayed.

What we need:
For static filter that is computed from a schedulable (no current user), such as automatic newsletter, we need an access limitation mode that will allowed all contents that is accessible to anyconnected users