Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: Prolem with attachments.
Date: Wed, 20 Feb 2002 07:18:31 -0500	[thread overview]
Message-ID: <a5049i$9uk$1@quimby2.netfonds.no> (raw)
In-Reply-To: <vpqeljgfpl2.fsf@ubaye.imag.fr> (Matthieu Moy's message of "Wed, 20 Feb 2002 10:51:53 +0100")

Matthieu Moy <Matthieu.Moy@imag.fr> writes:
> But why  should it send it  in parts ?

To avoid problems with excessive message size.

> Is the real question "Should I send the message in a readable format?" 

No.  The real question is, "Will the destination mailer transport, or
any intermediate mail transport, refuse to ship this message in a
single block due to excessive size?"

> None  of Gnus, Yahoo  mail, and  mutt seem  to be  able to  read these
> multipart messages, so ...

Gnus should certainly be able to.  As you said, you get a button:
	[1. message/partial]...
If you hit `b', Gnus should shovel the partial content to somewhere
under /tmp/your-login-name, and give you a message about "1 of N parts
processed."  When you do this with the 2nd through Nth parts, Gnus
will notice that the partials are now complete, and offer to do
something sensible with it based on the content type.

As for Yahoo mail, well, that's a disastrous excuse for a web-based
mail interface.  And mutt, it's cute and useful but in some ways it's
really not up to par.

The deeper question you need to be asking is, "Is there any mail
transport these days that is so backward as to be unable to handle a
megabyte or two in attachment content?" and the answer is probably
"No."  So ultimately, what you *really* want is

(setq message-send-mail-partially-limit nil)



  parent reply	other threads:[~2002-02-20 12:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20  9:35 Matthieu Moy
2002-02-20  9:46 ` Sebastian D.B. Krause
2002-02-20  9:46 ` Sebastian D.B. Krause
2002-02-20  9:51   ` Matthieu Moy
2002-02-20  9:51   ` Matthieu Moy
2002-02-20 12:04     ` Daniel Pittman
2002-02-20 12:09       ` Sean Neakums
2002-02-20 12:09       ` Sean Neakums
2002-02-20 12:13         ` Sean Neakums
2002-02-20 12:13         ` Sean Neakums
2002-02-20 12:24         ` Matthieu Moy
2002-02-20 12:24         ` Matthieu Moy
2002-02-20 12:04     ` Daniel Pittman
2002-02-20 12:18     ` Karl Kleinpaste
2002-02-20 12:18     ` Karl Kleinpaste [this message]
2002-02-20 14:14     ` Frank Tegtmeyer
2002-02-20 14:14     ` Frank Tegtmeyer
2002-02-20 15:25       ` Jesper Harder
2002-02-20 15:25       ` Jesper Harder
2002-02-20 20:37       ` Kai Großjohann
2002-02-20 20:37       ` Kai Großjohann
2002-02-20 13:11 ` ShengHuo ZHU
2002-02-20 13:11 ` ShengHuo ZHU
2002-02-20  9:35 Matthieu Moy

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='a5049i$9uk$1@quimby2.netfonds.no' \
    --to=karl@charcoal.com \
    /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).