unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: rgm@gnu.org, monnier@iro.umontreal.ca, 46472@debbugs.gnu.org
Subject: bug#46472: Make lisp/mail/uce.el obsolete
Date: Tue, 12 Oct 2021 19:44:17 +0300	[thread overview]
Message-ID: <83pmsap50e.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnPJ90Gf00y0DjA1ywvhG=EDOk4cGXC_UvW55yujmwuEg@mail.gmail.com> (message from Stefan Kangas on Tue, 12 Oct 2021 09:12:02 -0700)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 12 Oct 2021 09:12:02 -0700
> Cc: 46472@debbugs.gnu.org, rgm@gnu.org, monnier@iro.umontreal.ca
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > No, please leave unnecessary changes out of emacs-28.
> 
> Even documentation changes?

These are not just documentation changes, these are changes of the
semantics of the package.  It's not like they are typos or
inaccuracies in the documentation.  And the new defcustom is
definitely not a documentation change.

> I'd suggest installing the change as attached on emacs-28.  If that's
> not possible, I'd like to install it on master, but add the same text to
> the package "Commentary" section on emacs-28.

On master, please.  And I don't see why have the same text twice.

> > So I think the same message could be usefully conveyed with much fewer
> > words.
> 
> I've tried shortening it in the attached.

It is still too repetitive, IMO:

> +- You will confirm that your email address is valid, thus ensuring
> +  you get more spam.
> +
> +- You will leak information (e.g. on your email server and
> +  setup), thus opening yourself up for further attack.  They are
> +  likely to find your IP and \"geolocation\"), which often makes
> +  it trivial to find e.g. your home address and phone number.

The first paragraph is a special case of the second one.

> +- The sender address is likely fake.  The abuse@domain is
> +  unlikely to be able to do anything.
> +
> +- You open yourself up to various kinds of social engineering.
> +
> +- You confirm that the email did not land in your spam folder.
> +  (This helps them refine their methods of spamming.)

This is also the same as what you already said.

> +- Scammers have been known to threaten, intimidate, and use other
> +  forms of criminal manipulation.  Replying to spam can lead down
> +  a path that you may not want to be on.

This is the same as "open yourself to ..." paragraph.





  reply	other threads:[~2021-10-12 16:44 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
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 [this message]
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=83pmsap50e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46472@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@gnu.org \
    --cc=stefan@marxist.se \
    /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).