site address:
github.com/JoshData/python-email-validator/issues/77 redirected to: github.com/JoshData/python-email-validator/issues/77
site title:
email_validator.EmailSyntaxError: The email address contains invalid characters before the @-sign: (, ), .. · Issue #77 · JoshData/python-email-validator · GitHub
|
|
|
Our opinion (on Wednesday 18 November 2026 20:30:30 UTC):
- no comments
|
|
|
|
After content analysis of this website we propose the following hashtags:
|
|
|
|
Meta tags:
description= Currently validate_email raises an exception on valid emails with the form john.smith(comment)@example.com and (comment)john.smith@example.com due to the parenthesis, which are actually valid at the beginning and end of the local portion...;
Headings (most frequently used words):
navigation, the, metadata, footer, email_validator, emailsyntaxerror, email, address, contains, invalid, characters, before, sign, 77, menu, repository, description, activity, issue, actions, joshdata, commented, on, apr, 22, 2022, assignees, labels, projects, milestone, relationships, development,
Text of the page (most frequently used words):
the (35), and (20), github (14), that (13), #address (13), email (12), comment (11), sign (9), this (7), for (7), comments (6), you (5), not (5), security (5), copilot (5), issue (5), actions (5), joshdata (5), should (5), support (5), john (5), smith (5), example (5), com (5), are (5), with (5), code (5), projects (4), might (4), spec (4), before (4), your (4), navigation (3), labels (3), have (3), closed (3), then (3), part (3), think (3), what (3), new (3), which (3), valid (3), apr (3), 2022 (3), copy (3), link (3), email_validator (3), emailsyntaxerror (3), contains (3), invalid (3), characters (3), quality (3), another (3), tab (3), window (3), refresh (3), session (3), reload (3), developers (3), changelog (3), customer (3), enterprise (3), grade (3), features (3), all (3), build (3), can (2), time (2), community (2), status (2), footer (2), pull (2), requests (2), development (2), milestone (2), one (2), metadata (2), mailbox (2), supporting (2), according (2), permitted (2), other (2), interpreted (2), because (2), recipient (2), used (2), behavior (2), specification (2), clear (2), semantically (2), case (2), content (2), message (2), but (2), see (2), says (2), space (2), also (2), implementations (2), more (2), insights (2), repository (2), python (2), validator (2), signed (2), universe (2), training (2), integrations (2), stories (2), center (2), documentation (2), learn (2), business (2), fixes (2), products (2), secret (2), perform, action, share, personal, information, manage, cookies, contact, docs, privacy, terms, 2026, inc, open, app, branches, none, yet, relationships, assigned, assignees, already, account, join, conversation, free, jan, 2023, completed, reason, believe, separate, from, yes, consider, probably, software, implements, intent, facto, state, things, meaningful, hand, tried, sending, myself, added, start, was, considered, bounced, didn, match, thunderbird, client, side, once, postfix, server, second, gmail, muas, mtas, different, seems, contrary, pretty, addresses, cannot, contain, library, correct, per, main, use, project, based, web, login, forms, really, want, actual, deliverable, without, extraneous, mime, discarded, parenthesized, allowed, various, places, rfc, isn, super, purpose, although, runs, fws, cfws, occur, between, lexical, tokens, structured, field, header, single, character, take, mean, essentially, ignored, especially, since, would, section, some, legacy, interpret, generally, fields, avoid, confusing, such, again, means, may, appear, within, rfc2822, owner, commented, activity, currently, validate_email, raises, exception, emails, form, due, parenthesis, actually, beginning, end, local, portion, body, opened, erika, humu, description, items, wiki, issues, dismiss, alert, switched, accounts, out, appearance, settings, search, pricing, event, talks, workshops, next, partners, about, company, forum, events, webinars, blog, resource, connect, resources, premium, advanced, add, ons, trust, why, evaluate, industries, government, manufacturing, financial, services, healthcare, industry, nonprofits, startups, team, enterprises, stage, businesses, source, latest, improvements, across, place, developer, articles, sponsors, trending, repos, explore, customize, certifications, scanning, leak, prevention, protection, vulnerability, detection, remediation, secure, cloud, environments, codespaces, analysis, enforcement, automation, ship, coding, agent, tasks, automated, work, hosting, review, collaboration, platform, menu, skip,
Text of the page (random words):
email_validator emailsyntaxerror the email address contains invalid characters before the sign issue 77 joshdata python email validator github skip to content navigation menu sign in products platform github repository hosting code review and collaboration copilot ai coding agent for tasks projects and automated work build ship actions ci cd and automation code quality quality analysis fixes and enforcement codespaces cloud development environments secure code security vulnerability detection and remediation secret protection secret scanning and leak prevention all features developers learn documentation training certifications build build with copilot customize copilot integrations explore trending repos github sponsors developer articles changelog changelog your source for the latest features improvements and fixes across github products all in one place businesses by stage enterprises team startups nonprofits by industry healthcare financial services manufacturing government see all industries evaluate github why github customer stories business insights trust center add ons github advanced security enterprise grade code security copilot for business enterprise grade ai features premium support enterprise grade 24 7 support resources learn connect documentation resource center blog events webinars community forum customer stories integrations support customer support training github status company about partners changelog github universe github universe the event for developers by developers talks workshops and what s next for github pricing search sign in sign up appearance settings you signed in with another tab or window reload to refresh your session you signed out in another tab or window reload to refresh your session you switched accounts on another tab or window reload to refresh your session dismiss alert message joshdata python email validator repository navigation code issues 12 12 pull requests 5 5 actions projects wiki security and quality insights more items email_validator emailsyntaxerror the email address contains invalid characters before the sign 77 new issue copy link new issue copy link closed closed email_validator emailsyntaxerror the email address contains invalid characters before the sign 77 copy link description erika humu opened on apr 22 2022 issue body actions currently validate_email raises an exception on valid emails with the form john smith comment example com and comment john smith example com due to the parenthesis which are actually valid at the beginning and end of the local portion of the email address activity joshdata commented on apr 22 2022 joshdata on apr 22 2022 owner more actions this is new to me i see in rfc2822 3 2 3 that parenthesized comments are allowed in various places the rfc isn t super clear what the purpose of comments is although it says that runs of fws comment or cfws that occur between lexical tokens in a structured field header are semantically interpreted as a single space character which i take to mean that comments should essentially be ignored especially since a space would not be valid in an email address in section 3 4 address specification it also says also because some legacy implementations interpret the comment comments generally should not be used in address fields to avoid confusing such implementations which again i think means that a comment may appear within an address but it is not a part of the address i think the specification then is pretty clear that email addresses cannot semantically contain a comment so i think the behavior of this library is correct per the spec the main use case for this project is supporting email based web login forms and in that case what we really want is an actual deliverable email address without extraneous content that might be permitted in a mime message but according to the spec should be discarded on the other hand i tried sending myself an email that added comment at the start or before the sign in my address and the comment was interpreted i e considered a part of the address and the email bounced because it didn t match a recipient mailbox i used thunderbird on the client side and once with a postfix server and a second time with gmail as the recipient other muas and mtas might have different behavior so this seems to be contrary to the spec it might be that no software implements comments according to the intent of the spec and the de facto state of things might be that comments are permitted and are a meaningful part of the address do you have reason to believe that john smith comment example com can be a separate mailbox from comment john smith example com and john smith example com if yes then i should consider supporting it if no then i probably should not support it joshdata closed this as completed on jan 16 2023 sign up for free to join this conversation on github already have an account sign in to comment metadata metadata assignees no one assigned labels no labels no labels projects no projects milestone no milestone relationships none yet development no branches or pull requests issue actions open in github copilot app footer 2026 github inc footer navigation terms privacy security status community docs contact manage cookies do not share my personal information you can t perform that action at this time
|
|
| Thumbnail images (randomly selected): * Images may be subject to copyright. | |  |
|
Verified site has: 51 subpage(s). Do you want to verify them? Verify pages:
|
The site also has references to the 4 subdomain(s)
|
The site also has 4 references to external domain(s).
|
|
|
Pages verified in the last hours (randomly selected):
|
|
Top 50 hastags from of all verified websites.
| |
|
|
|
|
|
|
Load Info| page size | 40996 | | load time (s) | 0.696104 | | redirect count | 1 | | speed download | 58902 | | server IP | 140.82.121.3 |
|
|
|
|
|
|
|
|
* Image may be subject to copyright.
|
|