From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46472@debbugs.gnu.org
Subject: bug#46472: Make lisp/mail/uce.el obsolete
Date: Sat, 13 Feb 2021 06:25:19 -0600 [thread overview]
Message-ID: <CADwFkm=XPCv_3UTkK=2L66hj1-q-qM-2NtdtkUO5C3jvhWcw8g@mail.gmail.com> (raw)
In-Reply-To: <83im6we6v8.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> What you say above was always true: replying to spam bears an inherent
> risk. This didn't change in any way, so how will we justify
> obsoleting this package now?
I think the methods for dealing with spam has developed quite a bit
since 1996, so I'm not quite sure I follow this argument. The
justification is that no one should waste time replying to spam; they
should use a spam filter.
If you are looking for strictly technical reasons for obsoleting it, of
course they exist too: Anyone that wants to reply to an email using
pre-written drafts can do so using skeleton, tempo, abbrev, etc. Those
are better tools that cover this use-case.
> I don't think our personal opinions on which is or isn't useful
> practices are reasons good enough to make it harder for others to use
> those practices if they so wish.
Whether or not replying to spam is good or bad is not really a matter of
personal opinion; it is objectively bad. You can find any number of
security and privacy experts that could explain why:
- You will confirm your email address is valid, ensuring you get more
spam.
- Sender address is probably fake. (For example, you might unwittingly
participate in flooding someones mailbox. The abuse@domain and
postmaster@domain is also unlikely to be able to act on your reply.)
- You open yourself up to various kinds of social engineering.
- You might leak information (e.g. on your email server and setup).
Encouraging this bad practice by shipping uce.el puts unknowing users at
risk, and promotes a bad method of dealing with spam. We should instead
discourage this bad practice by moving it to obsolete/.
> It isn't our prerogative to tell others what to do or not to do in
> these circumstances.
Anyone would of course still free to continue doing whatever they want
(for example by making a copy of the obsolete libary for their own use).
But I think we should be equally free to (strongly) recommend against
bad practices.
next prev parent reply other threads:[~2021-02-13 12:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 21:58 bug#46472: Make lisp/mail/uce.el obsolete Stefan Kangas
2021-02-13 7:58 ` Eli Zaretskii
2021-02-13 12:25 ` Stefan Kangas [this message]
2021-02-13 14:00 ` Eli Zaretskii
2021-03-04 19:27 ` Glenn Morris
2021-03-04 21:12 ` Eli Zaretskii
2021-03-06 17:14 ` Stefan Kangas
2021-03-06 17:25 ` Eli Zaretskii
2022-06-17 13:07 ` Lars Ingebrigtsen
2021-10-12 4:33 ` Stefan Kangas
2021-10-12 13:52 ` Eli Zaretskii
2021-10-12 16:12 ` Stefan Kangas
2021-10-12 16:44 ` Eli Zaretskii
2021-10-12 17:29 ` Stefan Kangas
2021-10-12 18:50 ` Eli Zaretskii
2021-10-14 20:45 ` Stefan Kangas
2021-10-15 6:12 ` Eli Zaretskii
2021-10-15 8:50 ` Stefan Kangas
2021-10-15 10:46 ` Eli Zaretskii
2021-10-16 12:48 ` Stefan Kangas
2021-10-16 12:50 ` Eli Zaretskii
2021-10-17 23:56 ` Stefan Kangas
2021-10-16 12:32 ` Stefan Kangas
2021-03-03 21:22 ` Stefan Monnier
2021-03-04 3:39 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=XPCv_3UTkK=2L66hj1-q-qM-2NtdtkUO5C3jvhWcw8g@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=46472@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).