No no, not an arbitrary From: field. I'm assuming that he's trying to do a single email form for multiple sites or domains. He could check the REFERER to make sure its an allowed domain and then send an email with the from field being an address at that domain. So if foo.com is allowed to send mail through his form and a request comes from foo.com he sends the email with the From field with someone@foo.com where someone@foo.com is a real person expecting a reply perhaps.

That would work for most cases and where a client isn't sending the REFERER or its wrong then the connection is dropped, eleminates spammers. Maybe I should have been more clear.

On another note, companies that are hosting multiple websites do this sort of thing all the time (I know mine does) do you consider it to be SPAM? Even if the email goes to a real person and the person receiving the email knows they are getting it?

If he is concerned with offloading the emails because he wants to avoid strain on his email system, then I would strongly suspect that the people who he is trying to send emails for are from companies that his email server doesn't normally forward emails for.

Therefore he would be forging emails for domains that are unassociated with his server, and would be flagged as spam.

If the emails are forged for his own domain, then externally this issue goes away. I know why this is useful, and I have forged emails myself. However he still may have an unusual characteristic which causes his email to be flagged by some as a sign of spam. (Been there, done that as well...)