From: Lee Willis <lee@gbdirect.co.uk>
Subject: Re: pgnus 0.83 doesn't do MIME :(
Date: 19 Apr 1999 14:54:01 +0100 [thread overview]
Message-ID: <lzu2ucbts6.fsf@landlord.gbdirect.co.uk> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "19 Apr 1999 15:21:07 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
> Lee Willis <lee@gbdirect.co.uk> writes:
>
> > Hmm, when I try to include an image into a message in 0.83 the sent
> > message just includes the raw MML, it doesn't actually seem to do any
> > encoding, including of files etc. etc.
>
> 0.83 expands MML when sending, but not when Gcc'ing. As an interim
> measure, you might wish to use Bcc rather than Gcc.
Not really I don't mind it not expanding it, it's just I was sure it
used to and I hadn't noticed the change ...
Sorry :(
Lee.
--
I was doing object-oriented assembly at 1 year old ...
For some reason my mom insists on calling it "Playing with blocks"
next prev parent reply other threads:[~1999-04-19 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-19 13:04 Lee Willis
1999-04-19 13:21 ` Kai.Grossjohann
1999-04-19 13:54 ` Lee Willis [this message]
1999-04-19 13:52 ` Kai.Grossjohann
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=lzu2ucbts6.fsf@landlord.gbdirect.co.uk \
--to=lee@gbdirect.co.uk \
/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).