Gnus development mailing list
 help / color / mirror / Atom feed
From: "Jérôme Marant" <jerome.marant@fr.thalesgroup.com>
Subject: Re: Split attachments
Date: Fri, 8 Mar 2002 16:34:52 +0100	[thread overview]
Message-ID: <a6asik$qj3$1@quimby.gnus.org> (raw)
In-Reply-To: <2nvgc7jdk7.fsf@zsh.cs.rochester.edu>; from zsh@cs.rochester.edu on Fri, Mar 08, 2002 at 10:15:36AM -0500

On Fri, Mar 08, 2002 at 10:15:36AM -0500, ShengHuo ZHU wrote:

> It is not the behaviour Gnus is supposed to do.  But from your
> description, I can not tell where the problem is.  Could you post the
> headers of the messages?  It would be better to include a few lines of
> the bodies too.

In advance, sorry for the noise.

The first one :

To: jerome.marant@fr.thalesgroup.com
Subject: perso (1/2)
From: jerome.marant@free.fr (=?iso-8859-1?q?J=E9r=F4me?= Marant)
Date: Fri, 08 Mar 2002 07:38:19 +0100
User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.1
 (i386-debian-linux-gnu)
Mime-Version: 1.0
Content-Type: message/partial; id="<87elivbm3b.fsf@marant.org>";
number=1; total=2
Message-ID: <87d6yfbm3b.fsf@marant.org>
Lines: 12997
Sender: =?iso-8859-1?Q?J=E9r=F4me_Marant?= <jerome@marant.org>

To: jerome.marant@fr.thalesgroup.com
Subject: perso
From: jerome.marant@free.fr (=?iso-8859-1?q?J=E9r=F4me?= Marant)
Date: Fri, 08 Mar 2002 07:38:19 +0100
Message-ID: <87henrbm3o.fsf@marant.org>
Lines: 9
User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.1
 (i386-debian-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="

--=-=-=
Content-Type: application/octet-stream
Content-Disposition: attachment;
  filename=perso.tar.gz
Content-Transfer-Encoding: base64

H4sIACFUiDwCA+w8aXcaSZL+Cm/+wXzJ1soLeKlScUhIsmeekCzZtHU9IY3tt29nlFQlkFJdrkOI
/tC/fSIy64QCgaz29ts1M21BVWZkRGbcEVUTahvMM0M/UJqa1tRa2q62ozW3Dm8+9F+90EdraNpO

...


The second one :

To: jerome.marant@fr.thalesgroup.com
Subject: perso (2/2)
From: jerome.marant@free.fr (=?iso-8859-1?q?J=E9r=F4me?= Marant)
Date: Fri, 08 Mar 2002 07:38:19 +0100
User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.1
 (i386-debian-linux-gnu)
Mime-Version: 1.0
Content-Type: message/partial; id="<87elivbm3b.fsf@marant.org>";
number=2; total=2
Message-ID: <87bsdzbm3b.fsf@marant.org>
Lines: 3006
Sender: =?iso-8859-1?Q?J=E9r=F4me_Marant?= <jerome@marant.org>
Content-Transfer-Encoding: Quoted-Printable

IyVatW2BHL1VVeIt5USms/QG0yiqxinohsUoxhl7otrhEDYWy8g0tsY5bWrLm1y11WRCCTefj=
Wv1
RjUp8BE7bS8KSJkKLCc5fbniohHq2yFqGG1PuV4s9MEz3CoEsTP2OmUcsVYawAK3KihRkfV/Y=
zpN

...


I hope this helps.

Cheers,

-- 
Jérôme Marant




  parent reply	other threads:[~2002-03-08 15:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-08 12:23 Jérôme Marant
2002-03-08 15:15 ` ShengHuo ZHU
2002-03-08 15:15 ` ShengHuo ZHU
2002-03-08 15:34   ` Jérôme Marant
2002-03-08 18:51     ` Matthieu Moy
2002-03-08 18:51     ` Matthieu Moy
2002-03-08 23:05     ` ShengHuo ZHU
2002-03-08 23:05     ` ShengHuo ZHU
2002-03-08 15:34   ` Jérôme Marant [this message]
2002-03-08 16:30   ` Matthieu Moy
2002-03-08 16:30   ` Matthieu Moy
2002-03-08 12:23 Jérôme Marant

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='a6asik$qj3$1@quimby.gnus.org' \
    --to=jerome.marant@fr.thalesgroup.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).