Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Mime types and attached files
Date: Mon, 17 Apr 2006 14:32:07 +0200	[thread overview]
Message-ID: <m37j5ojsc8.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <smuodz04egs.fsf@linuxpal.mit.edu>

gdt@work.lexort.com writes:

> It would be cool to have BBDB notice MUAs used by correspondents and
> record them all, and have a function to choose an encoding based on
> that.  That way the standards could still be followed by default, with
> accomodation for lame/unstandard MUAs.

It wouldn't solve the problem of sending to multiple recipients,
forwarding, mailing lists, newsgroups, etc.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




      reply	other threads:[~2006-04-17 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-28 20:43 Fabrice Popineau
2006-04-14 13:28 ` Lars Magne Ingebrigtsen
2006-04-17  1:54   ` Katsumi Yamaoka
2006-04-17  9:04     ` Lars Magne Ingebrigtsen
2006-04-17 10:15       ` Katsumi Yamaoka
2006-04-17 11:12         ` Lars Magne Ingebrigtsen
2006-04-17 11:40       ` gdt
2006-04-17 12:32         ` Lars Magne Ingebrigtsen [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m37j5ojsc8.fsf@quimbies.gnus.org \
    --to=larsi@gnus.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.
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 NNTP newsgroup(s).