Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
mail a form
- Thread starter jjinx
- Start date
Hi mate,
What server side languages can you use?
There is a mailto: function but it is very unreliable so you are better to process it server side.
Hope this helps
Wullie
The pessimist complains about the wind. The optimist expects it to change.
The leader adjusts the sails. - John Maxwell
What server side languages can you use?
There is a mailto: function but it is very unreliable so you are better to process it server side.
Hope this helps
Wullie
The pessimist complains about the wind. The optimist expects it to change.
The leader adjusts the sails. - John Maxwell
EdwardMartinIII
Technical User
jjinx,
I had this same need, but I wasn't permitted to install anything on the server, so I had to do it all in JavaScript. But bear with me -- this is actually pretty straightforward.
I needed the contents of a bunch of text windows e-mailed to me. This solution required two forms on the same page and one small separate .js file:
First, the "Entry" document:
Obviously, this uses an external stylesheet called "Style.css", which you can tell from the class calls, but don't let that bother you -- it's just things like background colors, etc. Also, it should be obvious that I trimmed away a bunch of content that is proprietary, but again, it shouldn't be a problem.
Here's the external JavaScript file, which should be saved as "sample.js":
Sends all that junk in e-mail, neat as you please.
The tiniest caveat is that the browser -- depending upon your security settings -- pops up a warning that you are about to send e-mail via the web page.
I have not tested this in anything other than IE, as this client insisted on using only IE on all their machines.
Good luck!
Edward "Do not read this sentence."
I had this same need, but I wasn't permitted to install anything on the server, so I had to do it all in JavaScript. But bear with me -- this is actually pretty straightforward.
I needed the contents of a bunch of text windows e-mailed to me. This solution required two forms on the same page and one small separate .js file:
First, the "Entry" document:
Code:
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"[URL unfurl="true"]http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">[/URL]
<html xmlns="[URL unfurl="true"]http://www.w3.org/1999/xhtml"[/URL] xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></meta>
<title>Send Out The Data</title>
<link rel="stylesheet" href="Style.css" type="text/css"></link>
<script src="sample.js" type="text/javascript"></script>
</head>
<body>
<h3>Submissions Form</h3>
<form name="SubmissionForm" action="mailto:HungryMan@DonnerParty.com" enctype="multipart/form-data">
<table class="Fatscope">
<tr>
<td class="DescriptorCell">Function Name:</td>
<td class="ContentCell"><input type="text" size="100" id="FunctionName"></input></td>
</tr>
<tr>
<td class="DescriptorCell">Module which contains Function:</td>
<td class="ContentCell"><input type="text" size="100" id="ModuleName"></input></td>
</tr>
<tr>
<td class="DescriptorCell">Module Location:</td>
<td class="ContentCell"><input type="text" size="100" id="ModuleLocation"></input></td>
</tr>
<tr>
<td class="DescriptorCell">Function Description:</td>
<td class="ContentCell"><textarea cols="75" rows="5" id="FunctionDescription"></textarea></td>
</tr>
<tr>
<td class="DescriptorCell">Function Parameters:</td>
<td class="ContentCell"><input type="text" size="100" id="FunctionParameters"></input></td>
</tr>
<tr>
<td class="DescriptorCell">Function Example Call:</td>
<td class="ContentCell"><input type="text" size="100" id="FunctionExample"></input></td>
</tr>
<tr>
<td class="DescriptorCell">Programmer Name:</td>
<td class="ContentCell"><input type="text" size="100" id="ProgrammerName"></input></td>
</tr>
</table>
<p class="CenteredContent"><input type="reset" value="Clear All Entries" class="PDButton"></input></p>
</form>
<form name="ProxyForm" enctype="text/plain" method="post" action ="mailto:HungryMan@DonnerParty.com?subject=Reuseable Code Library Submission" onsubmit="update_message_body();return true;">
<p class="CenteredContent"><input type="submit" value="Submit New Function" class="PDButton"></input></p>
<input type="hidden" id="MessageBody" name="MessageBody"></input>
</form>
</body>
</html>Obviously, this uses an external stylesheet called "Style.css", which you can tell from the class calls, but don't let that bother you -- it's just things like background colors, etc. Also, it should be obvious that I trimmed away a bunch of content that is proprietary, but again, it shouldn't be a problem.
Here's the external JavaScript file, which should be saved as "sample.js":
Code:
function update_message_body()
// This function composes an e-mail message using the contents of
// another form on the same page.
{
var FunctionName = document.SubmissionForm.FunctionName.value;
var ModuleName = document.SubmissionForm.ModuleName.value;
var ModuleLocation = document.SubmissionForm.ModuleLocation.value;
var FunctionDescription = document.SubmissionForm.FunctionDescription.value;
var FunctionParameters = document.SubmissionForm.FunctionParameters.value;
var FunctionExample = document.SubmissionForm.FunctionExample.value;
var ProgrammerName = document.SubmissionForm.ProgrammerName.value;
var CurrentDate = new Date();
document.ProxyForm.MessageBody.value = "\n\n" + "-= Start of Message =-" + "\n\n"
+ "Reuseable Code Library Submission" + "\n\n"
+ "Time received: " + CurrentDate + "\n\n"
+ "Function Name: " + FunctionName + "\n\n"
+ "Module Name: " + ModuleName + "\n\n"
+ "Module Location: " + ModuleLocation + "\n\n"
+ "Function Description: " + FunctionDescription + "\n\n"
+ "Function Parameters: " + FunctionParameters + "\n\n"
+ "Function Example Call: " + FunctionExample + "\n\n"
+ "Submitted by: " + ProgrammerName + "\n\n" + "-= End of Message =-";
return true;
}Sends all that junk in e-mail, neat as you please.
The tiniest caveat is that the browser -- depending upon your security settings -- pops up a warning that you are about to send e-mail via the web page.
I have not tested this in anything other than IE, as this client insisted on using only IE on all their machines.
Good luck!
Edward "Do not read this sentence."
Hi guys,
Just a little warning to anyone deciding to use the mailto method.
If a client does not have a default mail client installed, they will not be able to send mail from a mailto: link.
The biggest problem I can see with this method is that a lot of people do not like providing their e-mail address through forms of this type.
Personally, I use many different e-mail accounts (Personal and a few business)and I might want to send the e-mail from a certain account. This is not possible with mailto: as it only launches the default client.
Overall, mailto: links are very commonly thought of as unproffesional.
Take a look at
Hope this helps Wullie
The pessimist complains about the wind. The optimist expects it to change.
The leader adjusts the sails. - John Maxwell
Just a little warning to anyone deciding to use the mailto method.
If a client does not have a default mail client installed, they will not be able to send mail from a mailto: link.
The biggest problem I can see with this method is that a lot of people do not like providing their e-mail address through forms of this type.
Personally, I use many different e-mail accounts (Personal and a few business)and I might want to send the e-mail from a certain account. This is not possible with mailto: as it only launches the default client.
Overall, mailto: links are very commonly thought of as unproffesional.
Take a look at
Hope this helps Wullie
The pessimist complains about the wind. The optimist expects it to change.
The leader adjusts the sails. - John Maxwell
EdwardMartinIII
Technical User
Well, I suppose it depends on one's definition of "professional". 8)
In my case, I was instructed to not use any server-side programming. The environment is controlled (all on an internal network), every terminal has a mail client, and no one is allowed to "hide" their e-mail addresses, nor would they want to.
When I do this sort of thing for the WWW, I usually use Perl and sendmail running on the server.
But this solution didn't require knowing anything about the server.
If jjinx knows that Perl is accessible on the server, then I'm sure someone (or me) will post a terrific solution that uses Perl.
Cheers,
Edward "Do not read this sentence."
In my case, I was instructed to not use any server-side programming. The environment is controlled (all on an internal network), every terminal has a mail client, and no one is allowed to "hide" their e-mail addresses, nor would they want to.
When I do this sort of thing for the WWW, I usually use Perl and sendmail running on the server.
But this solution didn't require knowing anything about the server.
If jjinx knows that Perl is accessible on the server, then I'm sure someone (or me) will post a terrific solution that uses Perl.
Cheers,
Edward "Do not read this sentence."
Hi mate,
My post was not aimed at you or anyone else, it was just adding a caution for people thinking of using this method.
In my personal opinion, there is no need to use a mailto: link other than for a simple link. When you start to require the addition of body text, a subject or bcc, etc then you should use a server side script to process the information.
If your current server does not offer you any way to send mail from your site, upgrade to one that is inline with current technologies. I have yet to see any decent host that does not either offer a generic script or the support for a language that you can use to create your own.
Having said all that, if you are producing this, or anything else for an intranet or any other tightly controlled environment then a lot of the common design problems like this one don't matter.
Hope this helps Wullie
The pessimist complains about the wind. The optimist expects it to change.
The leader adjusts the sails. - John Maxwell
My post was not aimed at you or anyone else, it was just adding a caution for people thinking of using this method.
In my personal opinion, there is no need to use a mailto: link other than for a simple link. When you start to require the addition of body text, a subject or bcc, etc then you should use a server side script to process the information.
If your current server does not offer you any way to send mail from your site, upgrade to one that is inline with current technologies. I have yet to see any decent host that does not either offer a generic script or the support for a language that you can use to create your own.
Having said all that, if you are producing this, or anything else for an intranet or any other tightly controlled environment then a lot of the common design problems like this one don't matter.
Hope this helps Wullie
The pessimist complains about the wind. The optimist expects it to change.
The leader adjusts the sails. - John Maxwell
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question