Handling of email address using a literal IP address instead of a domain name is inconsistent #12

Closed
opened 2020-04-12 13:44:19 +02:00 by reinhard-mueller · 2 comments
reinhard-mueller commented 2020-04-12 13:44:19 +02:00 (Migrated from github.com)

I noticed a small inconsistency, which I consider not urgent or important at all, but still wanted to note it:

While the 'regex' checker spends extra effort for accepting email addresses lke example@[1.2.3.4] as well, the 'mx' checker will refuse such addresses because the dns lookup will find no domain server for [1.2.3.4].

I noticed a small inconsistency, which I consider not urgent or important at all, but still wanted to note it: While the 'regex' checker spends extra effort for accepting email addresses lke `example@[1.2.3.4]` as well, the 'mx' checker will refuse such addresses because the dns lookup will find no domain server for [1.2.3.4].
karolyi commented 2020-04-12 18:59:39 +02:00 (Migrated from github.com)

Again, PR welcomed :)

Again, PR welcomed :)
reinhard-mueller commented 2020-04-13 22:30:57 +02:00 (Migrated from github.com)

FWIW, I'm going look into this soon, but I first need to find a server which actually accepts emails by the ip address notation so I can test this.

FWIW, I'm going look into this soon, but I first need to find a server which actually accepts emails by the ip address notation so I can test this.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: karolyi/py3-validate-email#12
No description provided.