==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.3.2
- Deployed with iRedMail Easy or the downloadable installer? No
- Linux/BSD distribution name and version: RHEL 8.3
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): NGNIX
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

When a activating # Access control under section [location ~ ^/iredadmin(.*)] to certain IP-addresses in /etc/nginx/templates/iredadmin.tmpl then newsletter subscription page is also applied same rules.

The rewrite goes to iredadmin so this behavior is expected. Can we do something about it?
 
Is it possible to have access control for /iredadmin and the same time allow all IP addresses to location ~ ^/newsletter ?

UPDATE: Even better solution would be to have 2FA for the iredadmin login.

/etc/nginx/templates/iredadmin.tmpl:

...
# Python scripts
location ~ ^/iredadmin(.*) {
    rewrite ^/iredadmin(/.*)$ $1 break;

    include /etc/nginx/templates/hsts.tmpl;

    include uwsgi_params;
    uwsgi_pass 127.0.0.1:7791;
    uwsgi_param UWSGI_CHDIR /opt/www/iredadmin;
    uwsgi_param UWSGI_SCRIPT iredadmin;
    uwsgi_param SCRIPT_NAME /iredadmin;

   # Access control
    allow nnn.nnn.nnn.nnn;
    deny  all;
}

[...]

# Handle newsletter-style subscription/unsubscription supported in iRedAdmin-Pro.
location ~ ^/newsletter/ {
    rewrite /newsletter/(.*) /iredadmin/newsletter/$1 last;
}