From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 184] new mailing lists proposal for libre-soc.org
Date: Thu, 09 Apr 2020 20:28:12 +0000
Message-ID: <bug-184-13-fT3cz3XXQu@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=184
--- Comment #14 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #13)
> (In reply to Luke Kenneth Casson Leighton from comment #12)
> > (In reply to Jacob Lifshay from comment #11)
> >
> > > I'm guessing the source address will be
> > > git-mirroring@jacob-build-server.programmerjake.tk
> >
> > ah if you install ssmtp and set it up similar to how it is done on the
> > ppc64 server, we can make it look like the messages are coming from
> > libre-soc.org.
>
> If we use the lettre.at library for sending build emails, we could set it to
> just connect directly to libre-soc.org over the vpn without needing a local
> email server.
ssmtp is not a local email server it's a redirector.
the less that gets done here the better.
can you arrange for the command to call an external command - the faster
this gets done in the least amount of time the better.
(there's no need to use a complicated advanced rust mail library:
get the information out as fast as possible and let *another*
external command do that job, this provides flexibility)
> We could also make the source address be builds@libre-soc.org
> instead of git-mirroring@jacob-build-server.programmerjake.tk that way it
> won't change if we move to a different server.
yes.
> > take a look in the /etc/ssmtp directory on the pp64 server
> >
> > > If you can, the Reply-To: header for both special-use mailing lists should
> > > be set to libre-soc-dev@libre-soc.org
> >
> > hmmm a case could be made for teaching people "um no you go to the
> > bugtracker" by rejecting replies. otherwise they will think that they
> > _should_ reply and we are back to square one.
>
> We could add a link to the new bug page to the emails sent out to the builds
> mailing list. If we are going to reject replies we should set Reply-To: to
> no-reply@libre-soc.org instead of leaving it as the default.
yep good idea.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-184-13@https.bugs.libre-soc.org/>
2020-04-08 19:21 ` bugzilla-daemon
2020-04-09 11:20 ` bugzilla-daemon
2020-04-09 18:56 ` bugzilla-daemon
2020-04-09 19:36 ` bugzilla-daemon
2020-04-09 20:14 ` bugzilla-daemon
2020-04-09 20:28 ` bugzilla-daemon [this message]
2020-04-10 18:27 ` bugzilla-daemon
2020-05-20 5:58 ` bugzilla-daemon
2020-06-07 0:29 ` bugzilla-daemon
2020-06-07 0:31 ` bugzilla-daemon
2020-06-07 0:57 ` bugzilla-daemon
2020-06-10 13:53 ` bugzilla-daemon
2020-06-10 21:25 ` bugzilla-daemon
2020-06-14 18:57 ` bugzilla-daemon
2020-06-14 23:16 ` bugzilla-daemon
[not found] <bug-184-13@http.bugs.libre-riscv.org/>
2020-03-20 18:54 ` bugzilla-daemon
2020-03-21 15:47 ` bugzilla-daemon
2020-03-21 23:24 ` bugzilla-daemon
2020-03-23 0:01 ` Cole Poirier
2020-04-07 15:07 ` bugzilla-daemon
2020-04-07 15:09 ` bugzilla-daemon
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=bug-184-13-fT3cz3XXQu@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git