Your message dated Sun, 14 Feb 2016 07:09:21 -0500
with message-id <[email protected]>
and subject line Re: Bug#738958: mutt: should split Mail-Followup-To into To
and Cc while replying
has caused the Debian Bug report #738958,
regarding mutt: should split Mail-Followup-To into To and Cc while replying
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
738958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738958
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mutt
Version: 1.5.21-6.4
Severity: normal
Tags: upstream
Hi,
When the honor_followup_to option is set, mutt will use all addresses in
Mail-Followup-To as To while replying. I think mutt should recognize
which addresses are To and which are Cc, or lots of Cc addresses will be
noticed unnecessarily.
Like this:
1, recognize addresses in &in->mail_followup_to but not in &in->cc, append to
&out->to
2, if &out->to is not empty now, recognize addresses in &in->mail_followup_to
but not in &out->to, append to &out->cc
3, else if &out->to is empty now, append addresses in &in->mail_followup_to to
&out->to
-- Package-specific info:
Mutt 1.5.21 (2010-09-15)
Copyright (C) 1996-2009 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 3.12-1-amd64 (x86_64)
ncurses: ncurses 5.9.20140118 (compiled with 5.9)
libidn: 1.28 (compiled with 1.28)
hcache backend: tokyocabinet 1.4.48
Compile options:
-DOMAIN
+DEBUG
-HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK
+USE_POP +USE_IMAP +USE_SMTP
-USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO
+HAVE_REGCOMP -USE_GNU_REGEX
+HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET
+HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME
-EXACT_ADDRESS -SUN_ATTACHMENT
+ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET
+HAVE_LANGINFO_YESEXPR
+HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"
MIXMASTER="mixmaster"
To contact the developers, please mail to <[email protected]>.
To report a bug, please visit http://bugs.mutt.org/.
misc/am-maintainer-mode
misc/autoconf-remove-am-c-prototypes.patch
features/ifdef
features/xtitles
features/trash-folder
features/purge-message
features/imap_fast_trash
features/sensible_browser_position
features-old/patch-1.5.4.vk.pgp_verbose_mime
features/compressed-folders
features/compressed-folders.debian
debian-specific/Muttrc
debian-specific/Md.etc_mailname_gethostbyname.diff
debian-specific/use_usr_bin_editor.diff
debian-specific/correct_docdir_in_man_page.diff
debian-specific/dont_document_not_present_features.diff
debian-specific/document_debian_defaults
debian-specific/assumed_charset-compat
debian-specific/467432-write_bcc.patch
debian-specific/566076-build_doc_adjustments.patch
misc/define-pgp_getkeys_command.diff
misc/gpg.rc-paths
misc/smime.rc
upstream/531430-imapuser.patch
upstream/537818-emptycharset.patch
upstream/543467-thread-segfault.patch
upstream/542817-smimekeys-tmpdir.patch
upstream/548577-gpgme-1.2.patch
upstream/553321-ansi-escape-segfault.patch
upstream/568295-references.patch
upstream/547980-smime_keys-chaining.patch
upstream/528233-readonly-open.patch
upstream/228671-pipe-mime.patch
upstream/383769-score-match.patch
upstream/578087-header-strchr.patch
upstream/603288-split-fetches.patch
upstream/537061-dont-recode-saved-attachments.patch
upstream/608706-fix-spelling-errors.patch
upstream/620854-pop3-segfault.patch
upstream/611412-bts-regexp.patch
upstream/624058-gnutls-deprecated-set-priority.patch
upstream/624085-gnutls-deprecated-verify-peers.patch
upstream/584138-mx_update_context-segfault.patch
upstream/619216-gnutls-CN-validation.patch
upstream/611410-no-implicit_autoview-for-text-html.patch
upstream/path_max
misc/579967-fixes-german-translation.patch
mutt.org
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (2, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mutt depends on:
ii libassuan0 2.1.1-1
ii libc6 2.17-97
ii libcomerr2 1.42.9-3
ii libgnutls26 2.12.23-11
ii libgpg-error0 1.12-0.2
ii libgpgme11 1.4.3-0.1
ii libgssapi-krb5-2 1.12+dfsg-2
ii libidn11 1.28-1
ii libk5crypto3 1.12+dfsg-2
ii libkrb5-3 1.12+dfsg-2
ii libncursesw5 5.9+20140118-1
ii libsasl2-2 2.1.26.dfsg1-8
ii libtinfo5 5.9+20140118-1
ii libtokyocabinet9 1.4.48-2
Versions of packages mutt recommends:
pn default-mta | mail-transport-agent <none>
ii libsasl2-modules 2.1.26.dfsg1-8
ii locales 2.17-97
ii mime-support 3.54
Versions of packages mutt suggests:
ii aspell 0.60.7~20110707-1
ii ca-certificates 20130906
ii gnupg 1.4.16-1
pn mixmaster <none>
ii openssl 1.0.1f-1
ii urlview 0.9-19
Versions of packages mutt is related to:
ii mutt 1.5.21-6.4
pn mutt-dbg <none>
pn mutt-patched <none>
-- no debconf information
--
Adam Lee
http://adam8157.info
--- End Message ---
--- Begin Message ---
tag 738958 +wontfix
thanks
On Fri, Feb 14, 2014 at 05:14:13PM +0800, Adam Lee wrote:
> Hi,
>
> When the honor_followup_to option is set, mutt will use all addresses in
> Mail-Followup-To as To while replying. I think mutt should recognize
> which addresses are To and which are Cc, or lots of Cc addresses will be
> noticed unnecessarily.
Hi Adam,
unfortunately that's not the behavior it is expected for Mail-Followup-To, what
mutt is doing is also pretty close to what other MUA are doing.
For more details see section 2.4 here:
https://www.ietf.org/proceedings/42/I-D/draft-ietf-drums-mail-followup-to-00.txt
Cheers
Antonio
--- End Message ---
