That's a rather broken CGI-parameter POST reader, not an RFC 822 email message header parser. It probably won't help. :)

On a side note, as that snippet has several flaws visible in ten seconds (does not verify the content length, is subject to large POST denial of service attacks, does not appear to handle properly encoded entities, ignores the valid ';' separator for form values, and does not allow '0' as a valid form value), I would advise against using it even when accepting CGI parameters. use CGI or die; offers a better suggestion.