Is this what I think it is? A resurrection of those free hosted formmail scripts we used when I started writing web pages in the late 20th century?<p>Edit: <a href="http://www.formmail.com/" rel="nofollow">http://www.formmail.com/</a> still seems to be going, in fact.
Another option is to host your static site on BitBalloon (<a href="https://www.bitballoon.com" rel="nofollow">https://www.bitballoon.com</a>) - we make the forms on the site work without any backend programming.<p>This doesn't leave your email in the HTML and we also do spam filtering on the form submissions (get a bit of traffic and your contact form will get lot of spam).
We did something similar a year ago but it didn't get any traction.
<a href="http://instant.jotform.com" rel="nofollow">http://instant.jotform.com</a>
Great idea. I'm not sure about the pricing though. I'd expect anyone who reaches 1000 submissions per month to probably make the effort to get their own form handler. I'd make it 100/month or maybe 1000 submissions total until you have to pay. Then make it an annual fee so that customers think "OK, I'll pay $X not to have to deal with this for another year."
I've been using SimpleForm(<a href="http://getsimpleform.com/" rel="nofollow">http://getsimpleform.com/</a>) for my static site forms, It's quite easy to set up and you can add some spam prevention with Akismet.<p>This project looks interesting because there no need to register unlike SimpleForm.
Cool idea -- what kind of spam protection can it offer though?<p>I'm not worried about the email address being in the open, but my original contact page form was getting hundreds (thousands?) of spam submissions a day until I implemented some simple javascript 'traps' to filter out the bots.<p>I've still not worked out why a bot wants to fill in a contact form with spam anyway, seems like a real waste of time.
The example says <i>...action="//...</i> shouldn't this be <i>...action="<a href="http://" rel="nofollow">http://</a> ...</i> ?<p>This is so seemingly simple but so useful, thanks a lot!<p>EDIT thanks for explaining, all! :)
Regarding the issue of having your email address in the open. This could easily be solved by requiring registration and generating an encrypted URL for each email address that a user associated with their account. I know this highers the barrier for entry, but putting an email address in the open is foolish and making it <i>too</i> easy for the dumbest of email harvesters.
There's a problem here. browsers do not send Referrer when on an https site. And they refuse to work without the header<p><i></i>For geeks: could not find "Referrer" header.
I was recently looking for a nice simple implementation of this for a client. Didn't really find any that I liked so we decided to build this ourselves. Now we have the flexibility of either emailing them the results or storing in our local database for later processing. This looks really nice though.
I don't know who would want this. Is it really a demand from people? It is programmers who love static sites who use this? Or the non-coders everywhere?