Hi Leo,

email encryption to block spam would be a nice feature for future releases.

Hi Planepix,

it's already there... Take a look at your source code...

Regards
Leo

wow, nice to know this - great!!

Hi Leo,

I understand this is extremely old post, but…

I’ve read on the features page (http://typolight.org/features.html) that there is automatic e-mail encryption (SPAM Protection) and you did re-confirm it above.

What I would like to know – how does it work? I’ve installed TL2.7 on my test/local server. I’ve tried putting e-mail address into “text” content element, “HTML” content element, tied putting it as a “link” element.

E-mail in the “text” element got output as it is, just a text with no link.
With “HTML” and “Link” elements e-mail address was published as <a href=mailto:email@address.com>email@address.com</a>

I’m not a developer, but as far as I understand, e-mail harvesting bots look for the “mailto:” part in particular. How do I enable e-mail encryption?

Thanks

hi ravenblack,
email encryption on typolight, as follows:

use the typolight 'insert tags' into text body or anywhere suitable.

{{email::address}}

example: {{email::joe@blogs.com}}
this will send email to joe@blogs.com, if you look at your website source code afterwards, you will see the difference.

reference page from: http://dev.typolight.org/wiki/EnglishInserttags

Hi Leo,

tnx for the tip, I gave it a go...
I must be missing something somewhere

I've put {‎{email::myname@domain.com}} and in the source code it is translated to <a href="myname@domain.com">myname@domain.com</a>

Where is the encryption?

Hi ravenblack,

did you type the brackets manually or copy-pasted from forum?

Type it manually and it should work.

Anyway the encryption isn't a 'real' encryption...

We should gather some information, scripts to improve the encryption...
At the moment it seems like Javascript is the only solution but as TL tries to comply with 'Accessibilty' this shouldn't be our goal

So if anyone of you out there's got a nice idea - feel free

Hi planepix,

yes, I did enter the "{{email::myname@domain.com}}" manually. After reading you comment I tried copy pasting it from the forum, just out of curiosity. Pasted into WYSIWYG editor as well as in HTML mode. Neither one worked.

And again, even entering {{email::myname@domain.com}} manually, source code in the frontend is <a href="myname@domain.com">myname@domain.com</a> and it is accessible to the e-mail harvesting bots, isn't it?

The encryption of TL will write your e-mail adress in ascii code...
So anyway you won't have any protection from harvesting bots at all!

Hi Toflar,

I'm not fussed about the encryption being 'real' or not, as long as e-mail addresses get protected in some way. I understand, that sophisticated harvesting bots will be able to 'decode' e-mail addresses like myname&#64 ;domain&#46 ;com

The problem is, I can't see any level of e-mail protection at the moment. None at all.

Maybe I'm looking at the wrong place. How do protected e-mail addresses appear in TL? Or could you explain method of e-mail addresses protection in TL?

Toflar:

The encryption of TL will write your e-mail adress in ascii code...
So anyway you won't have any protection from harvesting bots at all!

I see.

So what does "Automatic e-mail encryption (spam protection)" mean? It's listed as a feature in http://www.typolight.org/features.html

Any plans on inducing protection from e-mail harvesting in the future?

Well, what Toflar says is wrong (again). TYPOlight does not write your e-mail in ASCII characters but converts it into Unicode entities, which of course consist of ASCII characters but are not readable by bots.

That is as good a spam protection solution as any.

To see the effect, you need to look at the source code of the page! Do not check it in the status bar, do not use Firebug or any other plugin, just click on "view page source". If the e-mail address is not encoded in the plain source code, there is a problem with your local installation. In this case reupload or synchronize the files.

Hi Leo,

thanx for the reply, now I get it!

I've been using firebug to check the source code and it would show ASCII symbols, instead of the codes representing them.