Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.acorn.programmer > #1666 > unrolled thread

e-mail links in HTML

Back to article view | Back to comp.sys.acorn.programmer

Contents

  e-mail links in HTML Roger Darlington <rogerarm@freeuk.com> - 2012-04-26 07:09 +0100
    Re: e-mail links in HTML Robin Hounsome <robin@hounsome.org.uk> - 2012-04-26 07:23 +0100
      Re: e-mail links in HTML Roger Darlington <rogerarm@freeuk.com> - 2012-04-26 08:52 +0100
        Re: e-mail links in HTML "John Williams (News)" <UCEbin@tiscali.co.uk> - 2012-04-26 10:52 +0200
        Re: e-mail links in HTML jgharston <jgh@arcade.demon.co.uk> - 2012-04-26 14:32 -0700
          Re: e-mail links in HTML Roger Darlington <rogerarm@freeuk.com> - 2012-04-27 08:11 +0100
          Re: e-mail links in HTML "Derek.Moody" <derek.moody@casterbridge.net> - 2012-05-07 16:48 +0100
            Re: e-mail links in HTML Rick Murray <heyrickmail-usenet@yahoo.co.uk> - 2012-05-08 04:26 +0200
            Re: e-mail links in HTML Jeremy Nicoll - news posts <jn.nntp.scrap007@wingsandbeaks.org.uk> - 2012-05-08 03:48 +0100

#1666 — e-mail links in HTML

Several people say that they cannot click on an e-mail link on my 
webpage and get it to instigate an e-mail ready for sending.

Here is the code I use:

<a href="mailto:rogerarm@freeuk.com?subject=Submitted: Flower Photos 
for Contributions">
Submit Your Flower Photo Contributions
</a>

they turn out to be using gmail for e-mail.

Is gmail broken? Does it not understand HTML?

Is my HTML code out of date? (It works here with MessengerPro as 
e-mail client)

Should I complain to Google?

-- 

Cheers
Roger
If you start nowhere, you'll finish up in the same place

[toc] | [next] | [standalone]

#1667

In article <d272538652.rogerarm@rogerarm.freeuk.com>,
   Roger Darlington <rogerarm@freeuk.com> wrote:

> Several people say that they cannot click on an e-mail link on my 
> webpage and get it to instigate an e-mail ready for sending.

> Here is the code I use:

> <a href="mailto:rogerarm@freeuk.com?subject=Submitted: Flower Photos 
> for Contributions">
> Submit Your Flower Photo Contributions
> </a>

Try this:

<a href="mailto:rogerarm@freeuk.com?subject=Submitted:%20Flower%20Photos
%20for%20Contributions">

HTH

Robin

-- 
Remote - http://www.hounsome.org.uk
TV display software for the Iyonix

[toc] | [prev] | [next] | [standalone]

#1668

On 26 Apr 2012, Robin Hounsome  wrote:
> In article <d272538652.rogerarm@rogerarm.freeuk.com>,
>    Roger Darlington <rogerarm@freeuk.com> wrote:

>> Several people say that they cannot click on an e-mail link on my
>> webpage and get it to instigate an e-mail ready for sending.

>> Here is the code I use:

>> <a href="mailto:rogerarm@freeuk.com?subject=Submitted: Flower Photos
>> for Contributions">
>> Submit Your Flower Photo Contributions
>> </a>

> Try this:

> <a href="mailto:rogerarm@freeuk.com?subject=Submitted:%20Flower%20Photos
> %20for%20Contributions">


OK, thanks Robin, I will. It was just a case of Google not liking 
spaces, but MessPro doesn't mind, eh?


:-))


-- 

Cheers
Roger
The PC standard: no two machines alike.

[toc] | [prev] | [next] | [standalone]

#1669

In article <69e55c8652.rogerarm@rogerarm.freeuk.com>,
   Roger Darlington <rogerarm@freeuk.com> wrote:

> >> Here is the code I use:

> >> <a href="mailto:rogerarm@freeuk.com?subject=Submitted: Flower Photos
> >> for Contributions">
> >> Submit Your Flower Photo Contributions
> >> </a>

> > Try this:

> > <a href="mailto:rogerarm@freeuk.com?subject=Submitted:%20Flower%20Photos
> > %20for%20Contributions">

Interestingly, Pluto stops before the colon with your first href, giving a
subject of 'Submitted'.

Robin's version looks as though it would give the whole subject line were
it not for the line breaks, ie, the as-quoted above gives 'Submitted:
Flower Photos', but can't include the rest as a line-break has crept in.

I can demonstrate this by extracting the mailto and editing out the line
break and the quote bit to make it all one line:

mailto:rogerarm@freeuk.com?subject=Submitted:%20Flower%20Photos%20for%20Contributions

That works as expected.

John

-- 
John Williams, Brittany, Northern France - no attachments to these addresses!
Non-RISC OS posters change user to johnrwilliams or put 'risc' in subject!
Who is John Williams? http://petit.four.free.fr/picindex/author/

[toc] | [prev] | [next] | [standalone]

#1670

Roger Darlington wrote:
> > Try this:
> > <a href="mailto:roger...@freeuk.com?subject=Submitted:%20Flower%20Photos
> > %20for%20Contributions">
>
> OK, thanks Robin, I will. It was just a case of Google not liking
> spaces, but MessPro doesn't mind, eh?

It's not that Google doesn't like spaces, but URIs are defined to
not have spaces in them. Any spaces must be encoded, as in the
example given. See http://www.rfc-editor.org/rfc/rfc1738.txt

Additionally, in the above example the colon should also be
encoded.

JGH

[toc] | [prev] | [next] | [standalone]

#1671

On 26 Apr 2012, jgharston  wrote:
> Roger Darlington wrote:
>>> Try this:
>>> <a href="mailto:roger...@freeuk.com?subject=Submitted:%20Flower%20Photos
>>> %20for%20Contributions">
>>
>> OK, thanks Robin, I will. It was just a case of Google not liking
>> spaces, but MessPro doesn't mind, eh?

> It's not that Google doesn't like spaces, but URIs are defined to
> not have spaces in them. Any spaces must be encoded, as in the
> example given. See http://www.rfc-editor.org/rfc/rfc1738.txt

> Additionally, in the above example the colon should also be
> encoded.
To %3A


> JGH


-- 

Cheers
Roger
I'm a mitochondriac

[toc] | [prev] | [next] | [standalone]

#1697

In article <54370e48-bc5c-4d14-818b-264042f2ebcd@l3g2000vbv.googlegroups.com>,
jgharston <URL:mailto:jgh@arcade.demon.co.uk> wrote:
> Roger Darlington wrote:
> > > Try this:
> > > <a href="mailto:roger...@freeuk.com?subject=Submitted:%20Flower%20Photos
> > > %20for%20Contributions">
> >
> > OK, thanks Robin, I will. It was just a case of Google not liking
> > spaces, but MessPro doesn't mind, eh?
> 
> It's not that Google doesn't like spaces, but URIs are defined to
> not have spaces in them. Any spaces must be encoded, as in the
> example given. See http://www.rfc-editor.org/rfc/rfc1738.txt

Better see rfc 2368

> Additionally, in the above example the colon should also be
> encoded.

Slightly better might be:

<a href="&#109;&#097;&#105;&#108;&#116;&#111;&#058;&#114;&#111;&#103;&#101;&#114;&#097;&#114;&#109;&#064;&#102;&#114;&#101;&#101;&#117;&#107;&#046;&#099;&#111;&#109;&#063;&#115;&#117;&#098;&#106;&#101;&#099;&#116;&#061;&#083;&#117;&#098;&#109;&#105;&#116;&#116;&#101;&#100;&#032;&#070;&#108;&#111;&#119;&#101;&#114;&#032;&#080;&#104;&#111;&#116;&#111;&#115;&#032;&#102;&#111;&#114;&#032;&#067;&#111;&#110;&#116;&#114;&#105;&#098;&#117;&#116;&#105;&#111;&#110;&#115;">Submit Your Flower Photo Contributions</a>

 - as it'll fool most of the address harvesting spiders.

Hth. Cheerio,

-- 
>> derek.moody@casterbridge.net

[toc] | [prev] | [next] | [standalone]

#1698

On Mon, 7 May 2012 16:48:35 +0100, "Derek.Moody" 
<derek.moody@casterbridge.net> wrote:
> <a href="&#109;&#097;&#105;&#108;&#116;&#111; etc
>  - as it'll fool most of the address harvesting spiders.

Not mine. I wrote a little BASIC proggy many years ago as a proof of 
concept as to why Argonet's user directory was an invitation. It 
built a list of pages and scanned them, plus subpages three levels 
deep (unless linked away from Argo (determined by IP lookup)). From 
that, it extracted all mailto links and decoded glyphs, nospam 
inserts, and the like. It also looked for text "at" and "@" to try to 
retrieve non-link addresses. It found some, and decoded them. ;-) It 
also filtered out common bogus addresses (whitehouse.gov, localhost, 
etc).

The only thing it completely skipped was emails in images, 'cos my 
maths isn't up to OCR code. Wouldn't have thought that'd be a laugh 
in BASIC anyway. ;-)

I guess the level of result from a spambot depends upon the 
competence of the programmer...


Best wishes,

Rick.

PS: The secret? Run the scan on a subset and ask it to keep 
everything that "looks like" an address. Then go through it manually 
coding rules. Then let loose, for most people munge their addresses 
in very similar ways. God, imagine giving it "wiki recent changes" as 
the input!

PPS: Don't think I have the code, it'll be on my dead 2Gb drive. It 
was, however, a rainy Sunday's worth of code. It isn't hard, just a 
bloody big array and a heap of decode rules. If I wrote it again, I'd 
dump likely addresses to a file and process them afterwards, instead 
of doing it during the scan...

[toc] | [prev] | [next] | [standalone]

#1699

"Derek.Moody" <derek.moody@casterbridge.net> wrote:

> Slightly better might be:
>
><a href="&#109;&#097;&#105;&#108; .... >
>
> - as it'll fool most of the address harvesting spiders.

Will it?  Surely anything that simple valid HTML is going to be easy to
decode.

-- 
Jeremy C B Nicoll - my opinions are my own.

Email sent to my from-address will be deleted. Instead, please reply
to newsreplyaaa@wingsandbeaks.org.uk replacing "aaa" by "284".  

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.acorn.programmer

csiph-web