Gnus development mailing list
 help / color / mirror / Atom feed
From: Jack Vinson <vinson@unagi.cis.upenn.edu>
Subject: Re: extra .ATT attachments?
Date: 16 Sep 1999 10:20:12 -0500	[thread overview]
Message-ID: <wkyae6hoib.fsf@chevax.ecs.umass.edu> (raw)
In-Reply-To: Jaap-Henk Hoepman's message of "16 Sep 1999 09:19:41 +0200"

>>>>> "JH" == Jaap-Henk Hoepman <hoepman@cs.utwente.nl> writes:

JH> When I send mail with attachments to people using MS Outlook, they see
JH> an extra attachment <blurp>.ATT included in the file. They cannot open
JH> this file, and this causes quite some confusion. Apparently its my
JH> signature that is contained in this attachment (as it does not show up
JH> in elsewhere in their message pane).

JH> What is the problem and how can it be solved?

I have noticed this problem as well when sending myself binary files for
fun (to see how well Outlook worked).

The basic problem is that Outlook does not understand multipart messages.
It can deal happily with multiple attachments.  But any time you place text
after an attachment, you will get a *.ATT file.

I assume this has something to do with putting inlined text between
attachments.  Outlook seems to expect all attachments to be at the end of
the MIME message.  When there is extra stuff it gets confused.  I assume
the "correct" behavior is for it to treat the extra stuff as plain old
text.

-- 
Jack Vinson
Bart: I will not grease the monkey bars.



  parent reply	other threads:[~1999-09-16 15:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-16  7:19 Jaap-Henk Hoepman
1999-09-16 15:08 ` Nathan Williams
1999-09-16 15:34   ` Lee Willis
1999-09-16 15:40     ` Nathan Williams
1999-09-16 18:27       ` Robert Bihlmeyer
1999-09-25  9:28       ` Lars Magne Ingebrigtsen
1999-09-16 15:20 ` Jack Vinson [this message]
1999-09-16 16:57 ` Toby Speight
1999-09-16 17:25   ` Jody Klymak
1999-09-16 18:28     ` David S. Goldberg
1999-09-18 21:07       ` Kai Großjohann
1999-09-17 21:40 ` Jack Vinson

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=wkyae6hoib.fsf@chevax.ecs.umass.edu \
    --to=vinson@unagi.cis.upenn.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).