From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: sending mime attached files
Date: 25 Feb 2001 18:10:28 -0500 [thread overview]
Message-ID: <5bn1baqryz.fsf@curlew.cs.rochester.edu> (raw)
In-Reply-To: <m3wvaeo1x6.fsf@h0050bad6338d.ne.mediaone.net> (Nick Papadonis's message of "25 Feb 2001 17:03:49 -0500")
Nick Papadonis <npapadon@yahoo.com> writes:
> When sending a mime attached file to multiple recipients, is the file
> encoded base64 for each recipient? It seems like this is
> happening.
>
> I could be wrong.
The file is encoded more than once if Gcc exists. It should not
depend on the number of recipients.
ShengHuo
prev parent reply other threads:[~2001-02-25 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 22:03 Nick Papadonis
2001-02-25 23:10 ` 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=5bn1baqryz.fsf@curlew.cs.rochester.edu \
--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).