KeithMcL — Wed, 16 Nov 2005 17:51:02 +0000

A point I'd like to add is always make sure you validate any content entered into forms. You don't want to be the subject of an email injection attack or an sql injection attack either. Validate, validate, validate

timjpriebe — Tue, 15 Nov 2005 13:54:22 +0000

Right. So never store an email address statically in a hidden field. Of course, if it's from a text field on a previous page's form (which is what I was talking about), then there will be no email address in there when a harvester looks at it.

Busy — Mon, 14 Nov 2005 21:32:05 +0000

Just to add if you have a Javascript based email form with hidden fields (like a lot do), email harvestors will get your email address as it's there in plain view - well if you look at view source

timjpriebe — Mon, 14 Nov 2005 13:53:15 +0000

You can always have hidden form fields. In other words, if page one had a text field named EMAIL, and that was it, the next page would have a hidden field also named EMAIL, and it would read in the value from the submitted form and make it the value on the new field.

The biggest downside is you would accumulate hidden fields, and could end up having a lot of fields that are increasing download time of the page, but are not actually being shown.

JeevesBond — Mon, 14 Nov 2005 13:25:45 +0000

Well all you're doing there is sending an e-mail with the contents of a form right?

You could use multiple forms setup across different pages with each of these sending an e-mail. This would be the simplest way of doing things, if you need all the data to be collated then sent together at the end of the process then you need to learn PHP or some other server-side scripting language, things start to get a bit complicated here so it much depends on how much you're willing to learn