From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: Prolem with attachments.
Date: Wed, 20 Feb 2002 23:04:36 +1100 [thread overview]
Message-ID: <87y9hoz7e3.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <vpqeljgfpl2.fsf@ubaye.imag.fr> (Matthieu Moy's message of "Wed, 20 Feb 2002 10:51:53 +0100")
On Wed, 20 Feb 2002, Matthieu Moy wrote:
> krause@sdbk.de (Sebastian D.B. Krause) writes:
>
>> Matthieu Moy <Matthieu.Moy@imag.fr> writes:
>>> message exceeds message-send-mail-partially-limit. Send in parts ?
>>>
>>> And I answered yes.
>>
>> If you say Gnus that it should send the mail in parts it does so. So
>> just say 'no' here.
>
> But why should it send it in parts ?
Because there are /still/ a lot of email gateways that bounce large
messages or, worse, drop them silently or return a permanent fatal error
when one is sent through them.
> When is asked the question, I thought about multipart ?
Maybe you could suggest a better way of phrasing a question that means:
Should Gnus split this message up into smaller parts
for transmission to avoid problems with mail gateways?
> Is the real question "Should I send the message in a readable format?"
Depends on your point of view. Many people who read the alt.binaries.*
hierarchy can read 'message/partial'[1] mail.[2]
> None of Gnus,
Sure it can, at least with a recent Gnus. Hitting 'b' when viewing the
first part of, say, a 'message/partial' tiff works fine for me. :)
> Yahoo mail,
That doesn't surprise me, because they suffer the same disease as
every Windows MUA that I have met: they assume that messages are
structured in one very simple way, so don't bother with a real MIME
parser or display system.
> and mutt seem to be able to read these multipart messages, so ...
metamail should be able to put them together. I am actually surprised
that Mutt can't, though. Are you /sure/ that it can't reassemble the
attachment?
Daniel
Footnotes:
[1] Er, is it 'message', 'application' or what? I can't remember. *sigh*
[2] At least, I presume they can. There are certainly enough of them
going through the thing. :)
--
Maybe I am not very human - What I wanted to do was
to paint sunlight on the side of a house.
-- Edward Hopper
next prev parent reply other threads:[~2002-02-20 12:04 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:51 ` Matthieu Moy
2002-02-20 12:04 ` Daniel Pittman [this message]
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
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 9:51 ` Matthieu Moy
2002-02-20 9:46 ` Sebastian D.B. Krause
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=87y9hoz7e3.fsf@inanna.rimspace.net \
--to=daniel@rimspace.net \
/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).