[thelist] mailto: long body text

Tyme nopun at bellsouth.net
Tue Aug 14 17:04:21 CDT 2001


While I appreciate the response, I cannot believe that you so completely
missed several points.  If you are interested, I have pointed them out
inline.

----- Original Message -----
From: aardvark <roselli at earthlink.net>
To: <thelist at lists.evolt.org>
Sent: Tuesday, August 14, 2001 4:48 PM
Subject: Re: [thelist] mailto: long body text


> > From: "Tyme" <nopun at bellsouth.net>
> >
> except if the form has all the copy already in it, probably in a text
> area, there is no cut-n-paste, and there is an opportunity for the
> user to edit it...

TYME} Hello?  That was the point of inserting the text for the body value in
mailto:.  The user can easily modify the letter as desired.

> no offense, but one of the first things i ever made was a re-usable
> ASPMail script that only takes a minute to configure... it has
> to/from/cc/bcc/subject as well as fields to dump into the content
> part of a message... all i do is change the SMTP server and it's
> pretty much ready to go... this is something that is so basic it
> should be in every developers code library... just because you can't
> download one for free doesn't mean you can't make it yourself...
> the fact that you consider that a factor for *not* using it is
> unfortunate...

TYME} As stated in my original post, I too have and use ASPMail script.  It
is very easy to configure.  It is the email form that takes the time to put
together.  And, I had just a few minutes to set up the subject page.
...And, no, since I rarely use form mail on my sites, I do not have a
template form set up as yet.

> > 3.  I personally _hate_ form mail options.  I want a damn "sent mail"
> > message sitting in my desired folder for record and follow-up.  To
>
> your personal preferences are generally irrelevent... i hate the color

TYME}  Well, my personal preferences are shared by others (which I know them
to be), it is important.  And, when the main focus on the subject page is to
email a letter, that preference is something to be considered.  Yes, having
several options available is ideal.  However, 15 minutes of development time
often does not afford one those luxuries.  [Before you lecture me about
planning, twas not my scheduling.]

> > date, I have never encountered a form mail where the web developer has
> > configured it to send a cc: to the Sender.  (Except my own form mail,
>
> so add that into the one you're going to add to your code library...
> now it will never be an issue again...
>
> > when I use it.) Ever tried to print out your completed mail form for
> > record?  Doesn't work. Doesn't show all of your text.  And, of course,
>
> adjust the wrap with CSS or browser-specific tags if it's an issue...
> of course, cc-ing the sender is best, but if you're not going to do
> it...  you could even offer a printable version...
>
> > you don't know until you send the message whether you will be getting
> > a cc: back or not. ...I _rarely_ send email when a form is involved.
>
> if you don't know if you'll get a cc, then you didn't do a very good
> job managing the user's expectations... in fact, you have so many
> issues with it, and they are all so *easy* to address, i'd think you'd
> be happy to build a form that addresses all those problems... a
> form you can actually hold up as an example of how to do it right...

TYME} You so completely missed the point here.  I was speaking of my
experience as a _user_, not a developer.  Those many, many other developers
who failed to manage _my_ expectations.  As stated in my original post, I do
cc: the author when I use form mail.

TYME} Geez, people.  While I welcome constructive responses, I thought that
I had clearly stated my knowledge of form mail options but my desire to use
mailto: in _this particular case_...For a letter that was not to be static,
but to be easily customized by the user.






More information about the thelist mailing list