Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Attachment problems.
Date: 29 Nov 2000 21:27:27 -0500	[thread overview]
Message-ID: <2n1yvui48g.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <m3ofz2sxhh.fsf@paranoia.ahnberg.pp.se>

Mattias Ahnberg <mattias@ahnberg.pp.se> writes:

> I have some serious problems with my mailfolders. Someone forwarded a
> mail to me, including another mail with all its headers, and after
> that things have been messy++. Instead of showing the other mail as an
> attachment with all there is in it, it does the following:

If the mail is forwarded as message/rfc822, it is not an attachment.
It is shown inline.

Another possible problem is the MIME boundary is munged. It should be
"--ELM975106191-91841-0_" instead of "- --ELM975106191-91841-0_".

> You can find my .gnus file at http://ahnberg.pp.se/ahnberg.gnus if
> there could be something in there that could mess things up. Thanks
> in advance.

Your .gnus looks OK.

ShengHuo



      reply	other threads:[~2000-11-30  2:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-26 12:56 Mattias Ahnberg
2000-11-30  2:27 ` ShengHuo ZHU [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=2n1yvui48g.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).