From: DaMouse <damouse@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: bkbits - "@" question
Date: Sat, 23 Oct 2004 12:10:18 +0100 [thread overview]
Message-ID: <1a56ea3904102304103d2a3fbf@mail.gmail.com> (raw)
In-Reply-To: <20041023125943.266b658c.khali@linux-fr.org>
On Sat, 23 Oct 2004 12:59:43 +0200, Jean Delvare <khali@linux-fr.org> wrote:
> > On Sat, Oct 23, 2004 at 12:14:52PM +0200, Jean Delvare wrote:
> > > > * Larry McVoy asked:
> > > > The web pages on bkbits.net contain email addresses. This is
> > > > probably about a 4 year too late question but would it help reduce
> > > > spam if we did something like s/@/ (at) / for all those
> > > > addresses?
> > > >
> > > > * Christoph Hellwig answered:
> > > > No.
> > >
> > > Why not, please?
> >
> > Because spambots parse all this replacements anyway, and it makes cut
> > & pasting mail addresses if you want to reply to a change much easier.
>
> Strongly depends on how this is done. Of course, replacing
> user@domain.org by user(at)domain.org or even user AT domain DOT org
> won't help. However, I wonder what amount of spambots will spot user:
> domain org as a valid e-mail address.
>
> There are also HTML+CSS tricks that should work well. Split the address
> over right-floating span elements, these will display in the reverse
> order. I doubt that the spambots will get it right.
>
> I don't think that the cut'n'paste ability argument weights much here.
> How often do you do that?
>
> Thanks.
>
>
>
> --
> Jean Delvare
> http://khali.linux-fr.org/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Why not just have a PHP contact form instead with some of the well
known PHP security things in it such as an auth number box or whatnot.
-DaMouse
--
I know I broke SOMETHING but its there fault for not fixing it before me
next prev parent reply other threads:[~2004-10-23 11:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2SmNe-6MO-1@gated-at.bofh.it>
[not found] ` <2SqR0-10Q-9@gated-at.bofh.it>
2004-10-23 10:14 ` bkbits - "@" question Jean Delvare
2004-10-23 10:20 ` Jan Engelhardt
2004-10-23 10:43 ` Måns Rullgård
2004-10-23 10:21 ` Christoph Hellwig
2004-10-23 10:30 ` Toni Spets
2004-10-23 10:59 ` Jean Delvare
2004-10-23 11:10 ` DaMouse [this message]
2004-10-24 15:40 ` Martin J. Bligh
2004-10-23 4:26 Larry McVoy
2004-10-23 9:52 ` Christoph Hellwig
2004-10-23 11:12 ` Andrew Walrond
2004-10-23 11:36 ` Jon Masters
2004-10-23 11:52 ` Jesper Juhl
2004-10-23 15:56 ` Adrian Bunk
2004-10-25 6:20 ` Jeff Garzik
2004-10-28 17:48 ` Mark Frazer
2004-10-28 18:13 ` Måns Rullgård
2004-10-28 18:47 ` Mark Frazer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1a56ea3904102304103d2a3fbf@mail.gmail.com \
--to=damouse@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.