Hi!
Chris Knowles skrev:
Plus you're still putting the
email address in the source code albeit a modified version. If this
became a popular way to handle mailtos a harvester is sure to be written
to pattern match http://.../com/... or http://.../com/au/... or whatever
at some stage and attempt to construct an email address from it.
You could either use a key in the URL.
http://example.com/mail/key
which the server resolves to an emailaddress stored in a database
backend, or you could add some arbitrary string to make it more
difficult for harvesters:
http://example.com/mail/me/arbitrary/stuff/to/confuse/harvesters
The domain shouldn't be needed, your server sould already know it.
It's a pity that the support for mailto: locations isn't better, though.
As for now I still wouldn't attempt using it.
/anders
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
