Posted by Dave Smithz on 07/20/05 18:07
"Philip Ronan" <invalid@invalid.invalid> wrote in message
>> I'm going to try it again with a real link now (link to this posting)
>>
>> <http://groups.google.co.uk/group/comp.lang.php/browse_thread/thread/1cb1b4c32
>> adc20ac/6734c79bc12f98e8?q=Re:+Email+URL+to+plaintext+receivers+-+URL+being+tr
>> uncated(UsingPHP+Mailer)&rnum=1&hl=en#6734c79bc12f98e8>
>
> Oops. that didn't work for me either -- the link ended at "...Mailer)".
> :-(
That is sad, because that time it did work for me. It's a funny one that.
Might as well add the angle brackets anyway.
> Well like I said it isn't a massive amount of work. But as long as your
> links are RFC 2396 compliant then you can at least defend your work when
> the
> client complains ;-)
>
>> Looks like I'll have to create a HTML email and then a text part to that
>> email that has a text box where the user just types in their code into a
>> form text box. Unless any other good ideas.
>
> A text part with a text box? You lost me there...
Did not explain very well. In summary I will make the page for an invalid
code be a form with a text box. In that text box the user can enter their
unique code that is the end part of the URL so in my emails I might send out
goto this URL
www.example.com/longparameters
if you have problems enter this code
longparameters.
or something similar. OK still a lazy explanation I know but hopefully makes
sense.
Thanks again.
Navigation:
[Reply to this message]
|