From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] (n)upas/ml quirks
Date: Mon, 26 Sep 2016 09:31:48 +0200 [thread overview]
Message-ID: <0bc335e99d3fc7580e4fba3d14aa7055@felloff.net> (raw)
In-Reply-To: <20160926061747.4399186.40215.13125@stanleylieber.com>
i looked into mail/ml and all it does is to call upas/send with
the list of addresses as arguments and the mail to be send is
read from standard input. upas/send resolves each destination
individually... not clear why this would break all the destinations.
--
cinap
next prev parent reply other threads:[~2016-09-26 7:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 6:17 stanley lieber
2016-09-26 7:06 ` [9front] " cinap_lenrek
2016-09-26 7:31 ` cinap_lenrek [this message]
2016-09-26 7:37 ` cinap_lenrek
2016-09-26 14:40 ` stanley lieber
2016-09-26 15:20 ` cinap_lenrek
2016-09-26 14:50 ` stanley lieber
2016-09-26 16:04 ` cinap_lenrek
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=0bc335e99d3fc7580e4fba3d14aa7055@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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).