-
-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update-ngxblocker email routine doesn't support gmail username aliases user+alias@gmail.com #157
Comments
Thanks @centminmod for reporting this, I'm sure Stuart @itoffshore can sort this out in the next update |
* sanitizing + breaks google aliases fixes mitchellkrogza#157
@itoffshore @mitchellkrogza seems the bug is still happening for me looks like updater didn't update update-ngxblocker it's missing the fix outlined at https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/pull/158/files manually run update twice 1st run
2nd run
debug run - looks like updater didn't update update-ngxblocker it's missing the fix outlined at https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/pull/158/files
are we meant to manually update it https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker/blob/master/update-ngxblocker#L23-L26 ?
i..e
if i manually update then looks like your updated check works
|
* finishes fixing mitchellkrogza#157
I also needed to alter I've also got some improvements to come on how the scripts are updated & how mail is sent |
When i use an email with an alias i.e. user+alias@gmail.com, the update-ngxblocker script removes the
+
sign so that email is sent touseralias@gmail.com
instead ofuser+alias@gmail.com
The text was updated successfully, but these errors were encountered: