Munging电子邮件地址 [英] Munging e-mail addresses

问题描述

我在HTML源文件中都有电子邮件地址作为评论

信息信息，也作为电子邮件链接的一部分。当然，

我想把它们从收割机中隐藏起来以阻止更多的垃圾邮件。


标准方法只是使地址人类可读，但不是

机器可读。例如，我的地址是：


brownh @hartford-hwp.com


我认为我确实比

brownh at hartford-hwp dot com


因为当收获软件开始应对这些技巧时，它将会是b $ b b / b第二个比第一个没有问题。因为

只是在收割者不是那么短暂的时间内很容易被骗了，所以我正在寻找一种更好的方法。


一种技巧是给我们一个javascript来加密地址。我已经尝试了

Hivewire Enkoder并且它工作正常，除了显着的b / b
百分比的浏览器禁用了javascript。所以这个选项是

out。


另一种方法是将地址设为图形文件。我想我可以用em来定义这些图形的尺寸，这样当用户改变字体大小时它就会变化，它也会改变。但是，

我关心的地址只在网页上，所以

a图形替代没有帮助。


有没有任何方法（我正在运行debian）不依赖于

javascript而且很可能会阻塞收割机很长一段时间

来吧？如果它由样式表控制会很好，所以

数千个实例不需要逐个更新

。如果需要的话。 />

-

海恩斯·布朗

解决方案

>> ;>>> "海恩斯" == Haines Brown< br **** @ teufel.hartford-hwp.com>写道：


海恩斯>一种技术是给我们一个javascript来加密地址。我试过了

Haines> Hivewire Enkoder它工作正常，除了重要的

Haines>浏览器的百分比已禁用javascript。所以这个选项是

Haines> out。


是的，不要这样做。


海恩斯>另一种方法是使地址成为图形文件。我想我

海恩斯>可以根据em定义这些图形的尺寸，以便

Haines>当用户更改其字体大小时，它也会更改。但是，

Haines>我关注的地址仅在网页来源中，所以

Haines>图形替代品没有帮助。


不，也可以。盲人用户会起诉你的屁股。


到目前为止，我还没有看到任何收割者甚至打扰

HTML-de-entitizing，因为有这么多低悬的水果

不需要太多的CPU处理。如果有人能告诉我他们是否已经收获了：


发送邮件给我

< a href =" mailto：[e-mail]> merlyn @ stonehen ge.com< / a>！


然后我会停止推荐。但严重的是，这足以让b $ b阻止到目前为止所有人。为了加倍安全，编码一些

" mailto："还有。


如果那些地址少了1000万*那不是* b $ b那样，我会改变我的建议。 :)


-

Randal L. Schwartz - 巨石阵咨询服务公司 - [phone]

< ;我**** @ stonehenge.com> < URL：http：//www.stonehenge.com/merlyn/>

Perl / Unix /安全咨询，技术写作，喜剧等。

请参阅PerlTraining.Stonehenge.com进行现场和开放式注册Perl培训！

" Haines Brown" <峰; br **** @ teufel.hartford-hwp.com>在消息中写道

news：87 ************ @ teufel.hartford-hwp.com ...

我有电子邮件HTML源文件中的地址既可以作为评论信息信息，也可以作为电子邮件链接的一部分。当然，
我想把它们从收割机中隐藏起来以阻止更多的垃圾邮件。

我有一个简单而有效的解决方案。使用电子邮件表格，带有一些

标准的邮件程序;在您通常会指定的字段中

收件人的电子邮件地址，放入代码;然后修改formmail

程序将代码映射到您想要的电子邮件地址。


这样就完全删除了HTML中的电子邮件地址，使其成为

收割机无法找到它。这也可以防止你的formmail

程序被垃圾邮件发送者劫持。


缺点是有些主机不允许你自定义他们的邮件
程序。 （这意味着你，蒂娜，这是唯一的东西是

阻止我把我的客户转给你！叹息。）

< br>

[e-mail] （Randal L. Schwartz）写道：
< blockquote class =post_quotes>到目前为止，我还没有看到任何收割者甚至打扰HTML / de-entitizing，因为有很多低悬的果实
需要大量CPU处理。如果有人能告诉我他们是否已被收获：

发送邮件至< a
href =" mailto：[e-mail]> merlyn @ stonehen ge.com< / a>！

然后我会停止推荐。但严重的是，这足以阻止所有人到目前为止。为了加倍安全，编码一些
mailto：同样。

优雅的解决方案！可能是因为它没有发生在我身上;-)我只是等待潜伏者跳入并解释为什么你的假设

是错误的，但到目前为止，这么好（我还没有在IE下试过）。


虽然我不能用它来放在一个电子邮件地址中

在页面源代码中发表评论，我认为任何人都足够讽刺

snoop那里有足够的技巧来理解我可能会花的任何技巧

play地址。


-

海恩斯·布朗

I have e-mail addresses in HTML source files both as commented
information information and also as part of an e-mail link. Naturally,
I''d like to hide them from harvesters to discourage more spam.

The standard approach simply makes the address human readable, but not
machine readable. For example, my address would be:

brownh @hartford-hwp.com

Which I assume is really no more secure than

brownh at hartford-hwp dot com

because when harvesting software begins to cope with these tricks, it
will have no more problem with the second than the first. Because
that''s only a matter of a short time before harvesters are not so
easily fooled, I''m looking for a better method.

One technique is to us a javascript to encrypt the address. I''ve tried
Hivewire Enkoder and it works fine, except that a significant
percentage of browsers have javascript disabled. So this option is
out.

An alternative is to make the address a graphical file. I suppose I
could define the dimensions of this graphics in terms of em, so that
when a user changes his font size, it will change as well. However,
the addresses of concern to me are only in the webpage source, and so
a graphical substitute is no help.

Is there any method (I''m running debian) that will not depend on
javascript and yet is likely to block a harvester for quite some time
to come? It would be nice to have it controlled by a style sheet, so
that the thousands of instances do not have to be updated one by one
as need arises.

--
Haines Brown

解决方案

>>>>> "Haines" == Haines Brown <br****@teufel.hartford-hwp.com> writes:

Haines> One technique is to us a javascript to encrypt the address. I''ve tried
Haines> Hivewire Enkoder and it works fine, except that a significant
Haines> percentage of browsers have javascript disabled. So this option is
Haines> out.

Yes, don''t do that.

Haines> An alternative is to make the address a graphical file. I suppose I
Haines> could define the dimensions of this graphics in terms of em, so that
Haines> when a user changes his font size, it will change as well. However,
Haines> the addresses of concern to me are only in the webpage source, and so
Haines> a graphical substitute is no help.

No, do that either. Blind users will sue your ass.

So far, I''ve not seen any harvesters even bother with
HTML-de-entitizing, since there are so many "low hanging fruits" that
don''t require much CPU processing. If someone could tell me if
they''ve been harvested as:

Send mail to me at
<a href="mailto:[e-mail]>merlyn@stonehen ge.com</a>!

then I''ll stop recommending that. But seriously, this is enough to
thwart everyone out there so far. To be doubly safe, encode some of
"mailto:" as well.

When there are 10 million fewer addresses that *aren''t* written
that way, I''ll change my recommendation. :)

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - [phone]
<me****@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

"Haines Brown" <br****@teufel.hartford-hwp.com> wrote in message
news:87************@teufel.hartford-hwp.com...

I have e-mail addresses in HTML source files both as commented
information information and also as part of an e-mail link. Naturally,
I''d like to hide them from harvesters to discourage more spam.

I have a simple and effective solution. Use an email form, with some
standard formmail procedure; in the field where you would normally specify
the recipient''s email address, put in a code; then modify the formmail
procedure to map the code into your desired email address.

This completely removes the email address from your HTML, making it
impossible for harvesters to find it. This also prevents your formmail
procedure from being hijacked by spammers.

The downside is that some hosts don''t let you customize their formmail
procedure. (This means YOU, Tina, and it''s the only thing which is
preventing me from switching my clients to you! Sigh.)

me****@stonehenge.com (Randal L. Schwartz) writes:

So far, I''ve not seen any harvesters even bother with
HTML-de-entitizing, since there are so many "low hanging fruits"
that don''t require much CPU processing. If someone could tell me if
they''ve been harvested as:

Send mail to me at <a
href="mailto:[e-mail]>merlyn@stonehen ge.com</a>!

then I''ll stop recommending that. But seriously, this is enough to
thwart everyone out there so far. To be doubly safe, encode some of
"mailto:" as well.

Elegant solution! Probably the reason it didn''t occur to me ;-) I''m
only waiting for a lurker to jump in and explain why your assumptions
are wrong, but so far, so good (I haven''t tried it yet under IE).

While I can''t use this for the e-mail address that is placed in a
comment in the page source, I figure anyone who is savy enough to
snoop there is sophisticated enough to understand any tricks I might
play with the address.

--
Haines Brown

这篇关于Munging电子邮件地址的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！