Well, I really wonder why this restriction (outside the RFC specs) was implemented in the first place.
So, there seems to be not much of a chance to get an official version working correctly anytime soon. What about your fix? Is it in one of the current experimental builds?
No idea why it was done like it was in 1st place, would have to ask martin. I'd guess it was assumed a valid email address should follow patter email@example.com
as that's what the regex that determines if the address is considered valid or not.
No the change is not in the latest experimental. It was in just 1 special build:
*** SPECIAL BUILD - DO NOT USE UNLESS NEEDED ***
*** SPECIAL BUILD -DO NOT USE unless you want emails over 1MB delayed until after 9pm! ***
* Mod'd hmail regex to allow domains without suffixes such as localhost or workflow@noreply for MS Sharepoint services
* Block SPF +ALL special build patch removed
As you can see that was a few months ago and unless you want emails over 1MB delayed until 9pm you wouldn't want to use it.
Quite a few changes have occured in hmail since then too so I probably need to post an updated build based on the latest & greatest with the change. If I recall the reason I didn't leave the change in the experimentals was because I wanted to confirm if it was RFC compliant and wasn't sure if it'd break anything for other people. (Unlikely it'd break anything but it could potentially allow more spam/viruses in since searching logs I found it blocked a lot of junk.)
I had been tempted to add an INI setting to allow people to define their own regex but didn't want to bother if no one would use it or if the change became permanent.