MARKMIN problem with email addresses

[David Manns]

Using MARKMIN helper, if the string includes something like "... text som...@somewhere.com. Another sentence ..."  the period following the email address is incorrectly included in the email link.

[David Manns]

This can be resolved by changing one line in markmin2html.py

554 regex_auto = re.compile(r'(?<!["\w>/=])(?P<k>\w+://[\w\d\-+_=?%&/:.,;#]+\w|[\w\-.]+@[\w\-.]+)',re.M)

to 

554 regex_auto = re.compile(r'(?<!["\w>/=])(?P<k>\w+://[\w\d\-+_=?%&/:.,;#]+\w|[\w\-.]+@[\w\-.]*\w+)',re.M)

It seems reasonable that a domain name should not end in '.' or '-'

[Massimo Di Pierro]

Actually technically all domain names are supposed to end in . 

http://www.dns-sd.org/trailingdotsindomainnames.html

The . is usually omitted because the DNS understand it anyway.

[David Manns]

Well, yes, interesting. But in the context of email including a '.' at the end of an email address at the end of the address in mailto: does NOT work. RFC 2821 (SMTP) does not seem to address this issue. In practice, it seems that most email servers will not accept the trailing '.' and messages including it in the recipient address get bounced.

I'm using MARKMIN to format the body of emails sent to an application maintained mailing list. These notices often contain or end with something along the lines of "For more information, please contact x...@yyy.com. Its natural to end the sentence that way and tough to remember not to do so. So I'm leaving my app with the modified code!

[Niphlod]

I'm quite +1 . techinicality that just works for domain may not for everything else passed to regex_auto, and since eveybody is still typing www.google.com rather than www.google.com. I'd go with "mainstream" treatment.