From: phil@edgedesign.us (Philip Edelbrock)
To: lm-sensors@vger.kernel.org
Subject: Obscured email addresses in tickets
Date: Thu, 19 May 2005 06:24:02 +0000 [thread overview]
Message-ID: <3F00723D.4040000@edgedesign.us> (raw)
I tweaked the perl in the ticket system to obscure email addresses (e.g.
"this@that.com" is now "this at that dot com"). There aren't any
mailto: links, so I'm hoping that will be good enough to thwart most
spam harvesting engines. I thought about removing the email addresses
completely, but I still would like folks to be able to contact each
other freely to discuss troubles w/o having to use us as an in-between
each time.
Does this sound OK?
Phil
next reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 Philip Edelbrock [this message]
2005-05-19 6:24 ` Obscured email addresses in tickets Mark Studebaker
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=3F00723D.4040000@edgedesign.us \
--to=phil@edgedesign.us \
--cc=lm-sensors@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.