Gmail says "Error processing your email to Lighthouse"
Reported by Tom Herz | October 17th, 2008 @ 08:24 AM
We received an email from this address that had problems being processed into a new Lighthouse ticket:
Failed for "tom.herz@gmail.com" to tom_herz: the scheme http does not accept registry part: tom_herz.lighthouseapp.com (or bad hostname?)
TROUBLESHOOT http://lighthouseapp.com/help/ho...
FILE BUG http://activereload.lighthouseap...
Comments and changes to this ticket
-

Tom Herz October 17th, 2008 @ 08:26 AM
Hi,
Gmail won't let me create a ticket by email. I could have something to do with my username being Tom_Herz.
Let me know.
Tom
-
Will October 17th, 2008 @ 08:29 AM
- → Tag changed from to email tickets
- → State changed from new to open
Can you respond to this ticket via email? have you successfully used that email address with Lighthouse before?
Lastly, does that email/profile have access to the account in question?
-

Tom Herz October 17th, 2008 @ 08:35 AM
This is a trial Reply to the 'gmail' issue I just opened. I appreciate the quick response.
In answer to your question: It's the email address I used to register for lighthouse and the one associated with my account.
While you're diagnosing on that end, I'll work it from this end.
Best, Tom
-
Will October 17th, 2008 @ 08:49 AM
and you are using the email address generated by your Lighthouse project? http://help.lighthouseapp.com/fa...
-

Tom Herz October 17th, 2008 @ 08:55 AM
Yes.
On Fri, Oct 17, 2008 at 11:49 AM, Lighthouse support@lighthouseapp.comwrote:
-
rick October 17th, 2008 @ 01:45 PM
Wow, so apparently underscores aren't in the spec for domain names (yet browsers happen to support them). The ruby URI library also barfs, as you've seen in your emails.
I think I can fix this relatively easy in the lighthouse-api that the email tool uses.
-
rick October 17th, 2008 @ 03:10 PM
Okay, i just confirmed that emailing to a Lighthouse account with an underscore works. Try it now.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
