unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chetan Pandya <pandyacus@sbcglobal.net>
To: Jason Rumney <jasonr@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Change in rmail-reply
Date: Fri, 30 Jan 2009 19:53:48 -0800 (PST)	[thread overview]
Message-ID: <785436.96522.qm@web83207.mail.mud.yahoo.com> (raw)
In-Reply-To: 4983C273.4060201@gnu.org

Jason Rumney <jasonr@gnu.org> wrote:


> Chetan Pandya wrote:

>> One thing I don't like about this command is the potential for misuse - unless this is one of the intended uses.
>> The problem is that the recipient of the message may have no idea that the message is not really received from what it claims to be, if the recipient MUA does not look at the resend headers.  This might look like deception. Granted it is already possible to do it by other means, but the question is whether it should be made easier to do so.
>>  

>If the intention is to deceive, then it is trivially easy to forge email headers, especially in an environment as configurable as Emacs. The resend command is very useful to a small minority of users who deal with mailing list moderation or catch-all mailboxes and want to forward mail in a way that keeps the original headers intact. The feature is provided by other mail clients, either as standard or as an optional extension, so its inclusion in rmail is not unique.

The usefulness in some situations is not disputed.  However, the fact still remains that as it is, it has a limited usefulness for ordinary users. Like other commands that may be confusing to users, it could be disabled by default, unless explicitly enabled by the user. Within emacs itself, mh-e also seems to provide the feature, so it certainly isn't unique. Irrespective of what is done on the send side, it might make sense to show resent-from, especially if it is different from from field. Similar situation exists wrt "sender:", but in that case it is not conditional. Of course, it could be argued that it is configurable, but the default configuration should be not be a cause for confusion to users who may not be familiar with all the issues, IMO.

Chetan




  reply	other threads:[~2009-01-31  3:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 16:30 Change in rmail-reply Richard M Stallman
2009-01-26 17:39 ` Glenn Morris
2009-01-27  6:10   ` Richard M Stallman
2009-01-27  6:44     ` Don Armstrong
2009-01-27 18:18       ` Stefan Monnier
2009-01-27 22:58       ` Richard M Stallman
2009-01-27 23:22         ` Harald Hanche-Olsen
2009-01-29 14:32           ` Richard M Stallman
2009-01-29 15:08             ` Stefan Monnier
2009-01-29 16:36             ` Stephen J. Turnbull
2009-01-30  7:25               ` Richard M Stallman
2009-01-30  8:04                 ` Stephen J. Turnbull
2009-01-30 23:05                   ` Richard M Stallman
2009-01-31  0:50                     ` Chetan Pandya
2009-01-31  1:01                       ` Chetan Pandya
2009-01-31  3:16                         ` Jason Rumney
2009-01-31  3:53                           ` Chetan Pandya [this message]
2009-01-31  6:32                             ` Stephen J. Turnbull
2009-01-31  9:52                               ` Chetan Pandya
2009-02-01  6:30                               ` Richard M Stallman
2009-01-31  3:18                     ` Jason Rumney
2009-01-31  3:31                     ` Jason Rumney
2009-02-01  6:30                       ` Richard M Stallman
2009-01-31  4:57                     ` Stephen J. Turnbull
2009-01-27 23:35         ` Don Armstrong

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=785436.96522.qm@web83207.mail.mud.yahoo.com \
    --to=pandyacus@sbcglobal.net \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=rms@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).