From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] smtpd in modern times.
Date: Mon, 8 Feb 2016 08:21:06 -0500 [thread overview]
Message-ID: <0B7920A6-3331-49BA-BFF1-765BD1D5A154@9srv.net> (raw)
In-Reply-To: <ee7251f87debb839113e93bd07d161bd@quintile.net>
What leads you to believe this is so? I run smtpd from Erik's upas, and haven't noticed any problems related to this.
> On Feb 7, 2016, at 18:26, Steve Simon <steve@quintile.net> wrote:
>
> I have been running my a smtp server on plan9 for about
> 10 years but I beleive I am having more and more incomming
> mail bounce because of plan9's lack of support for tls 1.2.
>
> What is anyone else doing about this?
>
> stop ovvering ESMTP in smptd?
>
> Using a 3rd party smtpd supplier (google?)
>
> Does 9front support tls1.2 now?
>
> use facebook instead of email (joke).
>
> Other...
>
> -Steve (hoping replies don't bounce)
prev parent reply other threads:[~2016-02-08 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 23:26 Steve Simon
2016-02-07 23:34 ` Jack Johnson
2016-02-07 23:44 ` cinap_lenrek
2016-02-08 0:35 ` erik quanstrom
2016-02-08 13:21 ` Anthony Sorace [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=0B7920A6-3331-49BA-BFF1-765BD1D5A154@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
/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).