name.lastname@gmail.com parsed as 2 urls

Question

name.lastname@gmail.com parsed as 2 urls

ddosoff opened this issue 8 years ago · comments

Kirill Kostyuchenko commented 8 years ago

name.lastname@gmail.com parsed as:

davidthemarsh · Answer 1 · Thu Dec 29 2016 02:37:30 GMT+0800 (China Standard Time)

I am also seeing this - are there plans to fix it?

kodjo baah · Answer 2 · Tue Feb 21 2017 01:21:24 GMT+0800 (China Standard Time)

seeing the same problem as @davidthemarsh.

Bill Orpet · Answer 3 · Thu May 04 2017 00:36:18 GMT+0800 (China Standard Time)

I am impacted by this also. Dot containing emails are much more common than I had realized.

Tzu-Han Jan · Answer 4 · Fri May 19 2017 11:55:29 GMT+0800 (China Standard Time)

Hmm this is a greedy evaluator, so it matches whatever completes a url first. What should be the correct behavior in this case in your opinions? Should it be one url as name.lastname@gmail.com with an identifier saying that the URL is an email?

Bill Orpet · Answer 5 · Mon May 22 2017 22:48:07 GMT+0800 (China Standard Time)

@tzuhanjan: Expected behavior for me would be "name.lastname@gmail.com" is detected as a single Url with host gmail.com and username name.lastname.

capnbab · Answer 6 · Thu Oct 12 2017 21:28:46 GMT+0800 (China Standard Time)

@tzuhanjan Also having this issue. I agree with @worpet, it would be ideal if "name.lastname@gmail.com" was detected as a URL with host gmail.com and username name.lastname. For my use case, I need to exclude hits that look like pure e-mail addresses. So after detecting, I only include where url.getUsername().isEmpty(). This breaks for me on any e-mail address with a dot in the local part.