From: Karl Kleinpaste <karl@justresearch.com>
Subject: Re: Splitting, crossposts, duplicates, the universe, and everything.
Date: 17 Nov 1998 18:40:18 -0500 [thread overview]
Message-ID: <vxkr9v1lwgt.fsf@beaver.jprc.com> (raw)
In-Reply-To: Lloyd Zusman's message of "17 Nov 1998 18:19:12 -0500"
Lloyd Zusman <ljz@asfast.com> writes:
> To: one@asfast.com, two@asfast.com, three@asfast.com, four@asfast.com
> This causes 4 separate messages to be sent out
It certainly should not. RFC 821, page 3:
When the same message is sent to multiple recipients the SMTP
encourages the transmission of only one copy of the data for all the
recipients at the same destination host.
If you are suffering under an MTA which stupidly generates distinct
SMTP sessions for a single message addressed to multiple recipients at
a single destination, get a new one. Sheesh, talk about trivial
optimizations..."Don't send it more times than absolutely necessary."
next prev parent reply other threads:[~1998-11-17 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-17 16:14 Lloyd Zusman
1998-11-17 19:09 ` Michael Welsh Duggan
1998-11-17 23:19 ` Lloyd Zusman
1998-11-17 23:23 ` Alexandre Oliva
1998-11-18 2:27 ` Lloyd Zusman
1998-11-20 17:02 ` Stephen Zander
1998-11-17 23:40 ` Karl Kleinpaste [this message]
1998-11-17 23:35 ` Alexandre Oliva
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=vxkr9v1lwgt.fsf@beaver.jprc.com \
--to=karl@justresearch.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).