-
Notifications
You must be signed in to change notification settings - Fork 57
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
Accept all email addresses matching *@*.* #48
Comments
Hi, thanks for reporting. Can you please provide an example email adress that causes the described problem? |
[email protected] is apparently invalid. |
azett
added a commit
that referenced
this issue
Dec 25, 2019
Fixed with a9eeb2f, thanks for reporting! |
Thanks for the Christmas present! It looks like now there is no upper limit in the regex pattern, so I'm going to assume this can't be exploited for nefarious purposes. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nowadays, there are lots of TLDs with weird names and lots of characters. I'm working with such a domain name right now and I'm forced to fill in a dummy email addres to get the software working, I think because my TLD is too long or not recognized.
Also FYI, using HTML comments (
<!-- -->
) around BBCode tags seems to break the whole blog.Aside from those things, everything seems nice so far. :)
The text was updated successfully, but these errors were encountered: