[Mutt] #2936: description of $use_envelope_from is ambiguous

#2936: description of $use_envelope_from is ambiguous

 The description of $use_envelope_from is ambiguous. The manual says:
 ''When set, mutt will use $envelope_from_address as the envelope sender if
 that is set, otherwise it will attempt to derive it from the "From:"
 header. Note that this information is passed to sendmail command using the
 "-f" command line switch ![...]''

 The "otherwise" seems to correspond to the "when": ''When set, mutt will
 ![...], otherwise it will ![...]''.

 I propose: ''When this option is set, Mutt will set the envelope sender,
 using the value of $envelope_from_address if it is set, else the address
 of the "From:" header. Note that this information is passed ![...]''

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2936>

Re: [Mutt] #2936: description of $use_envelope_from is ambiguous

* Mutt <fleas <at> mutt.org> [01-08-2007 00:21]:

> #2936: description of $use_envelope_from is ambiguous
> 
>  The description of $use_envelope_from is ambiguous. The manual says:
>  ''When set, mutt will use $envelope_from_address as the envelope sender if
>  that is set, otherwise it will attempt to derive it from the "From:"
>  header. Note that this information is passed to sendmail command using the
>  "-f" command line switch ![...]''
> 
>  The "otherwise" seems to correspond to the "when": ''When set, mutt will
>  ![...], otherwise it will ![...]''.
> 
>  I propose: ''When this option is set, Mutt will set the envelope sender,
>  using the value of $envelope_from_address if it is set, else the address
>  of the "From:" header. Note that this information is passed ![...]''

Why not split it up in two sentences, for even more clarity?  (In
addition, some other minor changes)

''When this option is set, Mutt will set the envelope sender using
the value of $envelope_from_address, if that is set.  If this option
is not set, Mutt will set the envelope sender to the "From:" header.
Note that this information is passed ![...]''

My 2 cents,

--

-- 
René Clerc                      - (rene <at> clerc.nl) - PGP: 0x9ACE0AC7

Re: [Mutt] #2936: description of $use_envelope_from is ambiguous

* René Clerc [Wed, 01 Aug 2007 09:47:06 +0200]:

> * Mutt <fleas <at> mutt.org> [01-08-2007 00:21]:

> > #2936: description of $use_envelope_from is ambiguous

> >  The description of $use_envelope_from is ambiguous. The manual says:
> >  ''When set, mutt will use $envelope_from_address as the envelope sender if
> >  that is set, otherwise it will attempt to derive it from the "From:"
> >  header. Note that this information is passed to sendmail command using the
> >  "-f" command line switch ![...]''

> >  The "otherwise" seems to correspond to the "when": ''When set, mutt will
> >  ![...], otherwise it will ![...]''.

> >  I propose: ''When this option is set, Mutt will set the envelope sender,
> >  using the value of $envelope_from_address if it is set, else the address
> >  of the "From:" header. Note that this information is passed ![...]''

> Why not split it up in two sentences, for even more clarity?  (In
> addition, some other minor changes)

> ''When this option is set, Mutt will set the envelope sender using
> the value of $envelope_from_address, if that is set.  If this option
                                                        ^^^^^^^^^^^^^^
> is not set, Mutt will set the envelope sender to the "From:" header.
  ^^^^^^^^^^
> Note that this information is passed ![...]''

The underlined text seems to refer to "$use_envelope_from" itself. I

Re: [Mutt] #2936: description of $use_envelope_from is ambiguous

#2936: description of $use_envelope_from is ambiguous

Comment (by Adeodato Simó):

 {{{
 * René Clerc [Wed, 01 Aug 2007 09:47:06 +0200]:

 > * Mutt <fleas <at> mutt.org> [01-08-2007 00:21]:

 > > #2936: description of $use_envelope_from is ambiguous

 > >  The description of $use_envelope_from is ambiguous. The manual says:
 > >  ''When set, mutt will use $envelope_from_address as the envelope
 sender if
 > >  that is set, otherwise it will attempt to derive it from the "From:"
 > >  header. Note that this information is passed to sendmail command
 using the
 > >  "-f" command line switch ![...]''

 > >  The "otherwise" seems to correspond to the "when": ''When set, mutt
 will
 > >  ![...], otherwise it will ![...]''.

 > >  I propose: ''When this option is set, Mutt will set the envelope
 sender,
 > >  using the value of $envelope_from_address if it is set, else the
 address
 > >  of the "From:" header. Note that this information is passed ![...]''

 > Why not split it up in two sentences, for even more clarity?  (In

Re: [Mutt] #2936: description of $use_envelope_from is ambiguous

On 2007-08-01 11:59:48 +0200, Adeodato Simó wrote:
[...]
> > >  I propose: ''When this option is set, Mutt will set the
> > >  envelope sender, using the value of $envelope_from_address if
> > >  it is set, else the address of the "From:" header. Note that
> > >  this information is passed ![...]''
> 
> > Why not split it up in two sentences, for even more clarity?  (In
> > addition, some other minor changes)
> 
> > ''When this option is set, Mutt will set the envelope sender using
> > the value of $envelope_from_address, if that is set.  If this option
>                                                         ^^^^^^^^^^^^^^
> > is not set, Mutt will set the envelope sender to the "From:" header.
>   ^^^^^^^^^^
> > Note that this information is passed ![...]''
> 
> The underlined text seems to refer to "$use_envelope_from" itself. I
> recommend "If this second option is not set" instead.

Yes, but only when the first option is set. One can say:

  When this option is set, Mutt will set the envelope sender.
  Mutt will set it using the value of $envelope_from_address
  if this value is defined. If this value is not defined, Mutt
  will use the address in the "From:" header instead.

  Note that this information is passed [...]

--

-- 

Re: [Mutt] #2936: description of $use_envelope_from is ambiguous

#2936: description of $use_envelope_from is ambiguous

Comment (by Vincent Lefevre):

 {{{
 On 2007-08-01 11:59:48 +0200, Adeodato Simó wrote:
 [...]
 > > >  I propose: ''When this option is set, Mutt will set the
 > > >  envelope sender, using the value of $envelope_from_address if
 > > >  it is set, else the address of the "From:" header. Note that
 > > >  this information is passed ![...]''
 >
 > > Why not split it up in two sentences, for even more clarity?  (In
 > > addition, some other minor changes)
 >
 > > ''When this option is set, Mutt will set the envelope sender using
 > > the value of $envelope_from_address, if that is set.  If this option
 >                                                         ^^^^^^^^^^^^^^
 > > is not set, Mutt will set the envelope sender to the "From:" header.
 >   ^^^^^^^^^^
 > > Note that this information is passed ![...]''
 >
 > The underlined text seems to refer to "$use_envelope_from" itself. I
 > recommend "If this second option is not set" instead.

 Yes, but only when the first option is set. One can say:

   When this option is set, Mutt will set the envelope sender.
   Mutt will set it using the value of $envelope_from_address
   if this value is defined. If this value is not defined, Mutt

Re: Mutt ignoring Reply-To

[moving from mutt-users]

Jukka Salmi --> mutt-users (2007-08-02 13:41:13 +0200):
> Rado S --> mutt-users (2007-08-01 19:34:48 +0200):
> > =- Jukka Salmi wrote on Wed  1.Aug'07 at 11:53:41 +0200 -=
> > 
> > > I'm using Mutt 1.5.16. When replying to a mail which has a
> > > Reply-To header while reply_to is set, the address from the From
> > > header instead of the one from the Reply-To header ends up as the
> > > recipient address. I'd expect this behaviour only if reply_to is
> > > unset.
> > 
> > Have a look at mutt-dev archives, reply-to behaviour has been
> > discussed there in more detail.
> 
> Thanks for the hint. For the archives:
> 
> 	http://dev.mutt.org/trac/ticket/2934

Hmm, glancing at the code, wouldn't the attached patch make everybody
happy?

Regards, Jukka

--

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~

diff -r 6bc60516fffa send.c

[Mutt] #2937: mutt segfaulted when I pressed 'i' from within the pager

#2937: mutt segfaulted when I pressed 'i' from within the pager

 mutt segfaulted when I pressed 'i' to exit the pager. This is the error
 message I received.

 error: unknown op 180 (report this error).Segmentation fault

 Output from mutt -v:
 Mutt 1.4.2.2i (2006-07-14)
 Copyright (C) 1996-2002 Michael R. Elkins and others.
 Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
 Mutt is free software, and you are welcome to redistribute it
 under certain conditions; type `mutt -vv' for details.

 System: Linux 2.6.18-1.2798.fc6 (i686) [using ncurses 5.5]
 Compile options:
 -DOMAIN
 -DEBUG
 -HOMESPOOL  -USE_SETGID  -USE_DOTLOCK  -DL_STANDALONE
 +USE_FCNTL  -USE_FLOCK
 +USE_POP  +USE_IMAP  +USE_GSS  +USE_SSL  +USE_SASL
 +HAVE_REGCOMP  -USE_GNU_REGEX
 +HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET
 +HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM
 +HAVE_PGP  -BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT
 +ENABLE_NLS  -LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET
 +HAVE_LANGINFO_YESEXPR
 +HAVE_ICONV  -ICONV_NONTRANS  +HAVE_GETSID  +HAVE_GETADDRINFO
 -ISPELL
 SENDMAIL="/usr/sbin/sendmail"

Re: [Mutt] #2936: description of $use_envelope_from is ambiguous

#2936: description of $use_envelope_from is ambiguous

Changes (by brendan):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 (In [aefdab8fad80]) Clarify the documentation for $use_envelope_from
 (closes #2936).
 Thanks to Vincent Lefevre for the suggestions.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2936#comment:3>

Re: [Mutt] #2890: SMTP support: "...sending in background"

#2890: SMTP support: "...sending in background"

Comment (by brendan):

 Did you ever reproduce this with vanilla mutt?

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2890#comment:4>