You do know you're making an email, not a website right?
When you're going to build a sandbox in your backyard, do you rent a backhoe?
I think at times people need perspective. This is an email. It's not a website. Why would you use Foundation for Email? It's got it's own proprietary markup language and compiler. If you're gonna do that, go use Campaign Monitor or Mailchimp's WYSIWYG builder. You're doing the same thing.
I'm also against Foundation for websites, but for that, you'd need to see my web framework. getshipwright.com
This is why you should never use frameworks for email.
Use a boilerplate, use some code snippets, but for god's sake, WHY are you using a framework for an email?!
It's an EMAIL! It's not a website, it's not a landing page, it's not a webapp, it's an EMAIL!
I showed the time I needed to do testing manually with various devices on my desk plus opening and having to install and get licenses for various software like versions of Outlook, etc. The mess on my desk of different devices ranging from Windows Phones, iPhones, and old blackberries made the desk unsightly in the office, and I kept pushing for Litmus to be used as a replacement.
You really shouldn't attempt forms in emails, IMHO. Instead, you should have links that are unique to each recipient and each option, and that will in itself lead into a larger form. Read about my workaround to this, which I codenamed 'Laser', here:
I've talked directly with the Litmus team, Justine specifically, at least year's TEDC about how much time should be dedicated to this problem. Less than 1 percent of all email recipients print their emails. I think the answer is, if there's something to be printed, have it hosted on a landing page versus the email itself.