Re the doublequote: that appears to be a typographic dblquote -- the kind that M$ Word sticks into one of its docs when thus configured. If you, OP, are using Word to write code, abandon all hope ... or switch to one of M$ text editors... or, better, pick one that does what you say it should; not what the maker/seller wants it to do.

Which one: depends on what you try and like. Editor preference tends to be right up there with religion when folks disagree. But -- at the (very high) risk of incurring the wrath of some folk (for my obscene failure to mention their favorite), here are just a few of the many, possibly useful (mostly free) choices:

• Notepad++ (windows)
• editpadlite ('doze)
• Atom (non-denominational as to OS)
• Vi/Vim (*nix including apple's variant/windows)
• emacs (ditto)
• Light Table (GGIFY)
• Bluefish (definitely Linux, not sure about other OSen)
• gedit (likewise)
  

  ... and my own (widely dismissed) choice:

• NoteTab (windows; pro version is not free but if you try the lite and like it, well worth the upgrade price -- < 20 USD)

This -- because I'm out of ambition -- is only a small sample what what you may want.

Now, some observations that may help you avoid having to repeat your statement that you "have no idea what is wrong here."

Your perl toolkit offers a variety of ways to find out what those messages mean. The one that leaps to mind, as simple and helpful (albeit not perfect) is use diagnostics; or even use diagnostics -verbose;. The latter will -- as the argument suggests -- offer a more extensive explanation of that's going wrong and/or how to fix it.

Heed Corion's answer -- fixing the doublequote may solve most of your problems and his warning against the deprecated and dangerous sendmail is gospel.

But.... as gently as I know how, you need to understand that listing single lines of code doesn't give us much to go on to help you. You reference $FORM{name} repeatedly, but don't show us the form's code. Please read On asking for help and How do I post a question effectively? (among other site-specific documents).

Also note that what seems likely to be an attempt to produce a newline at LN 35 with the slash trailing the 'n' instead of preceding it. Fixing the typographic quote isn't going to fix that.