unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Michael Fischer <mfischer@zendesk.com>
To: Eric Wong <e@80x24.org>
Cc: "Jérémy Lecour" <jeremy.lecour@gmail.com>,
	"Liste Unicorn" <mongrel-unicorn@rubyforge.org>,
	unicorn-public@bogomips.org
Subject: Re: [ANN] unicorn 4.8.3 - the end of an era
Date: Wed, 7 May 2014 13:33:38 -0700	[thread overview]
Message-ID: <CABHxtY6CYM5+tTsLmiNSK=_EAbKjoqmapJWb92=4-SHN1FLg-Q@mail.gmail.com> (raw)
In-Reply-To: <20140507094632.GA26422@dcvr.yhbt.net>

On Wed, May 7, 2014 at 2:46 AM, Eric Wong <e@80x24.org> wrote:

> Jérémy Lecour <jeremy.lecour@gmail.com> wrote:
> > Would you mind explaining what a regular subscriber has to do to keep
> > receiving those emails in their inbox?
>
> You use ssoma[1] to to import mail into your inbox.  This is like how
> slrnpull works with NNTP or getmail/fetchmail works with POP.  It's
> only a one-way sync, but you can import it into an IMAP folder.
>
> Currently there's no SMTP delivery component, but I could probably set
> one up this week if there's enough demand for one.  The subscriber list
> will be public, though.

Is there some compelling reason why the mailing list simply cannot be
moved to another provider?  IMHO your users and fellow developers
shouldn't have to do anything other than change the submission
address.

I respect your desire to power the communication platform with free
software (and I'm sure this can still be done with Mailman or
whatever), but keep in mind the practical reality of our time, where
most of us these days are now comfortably using Webmail or or POP/IMAP
against a remote server that's not under the user's control and have
no desire to implement yet another communication conduit.

Thanks,

--Michael

  parent reply	other threads:[~2014-05-07 20:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  8:05 [ANN] unicorn 4.8.3 - the end of an era Eric Wong
2014-05-07  9:30 ` Jérémy Lecour
2014-05-07  9:46   ` Eric Wong
2014-05-07 10:16     ` Lin Jen-Shin (godfat)
2014-05-07 10:52       ` Alejandro Riera
2014-05-07 19:54         ` handling SMTP subscribers to public-inboxen Eric Wong
2014-05-07 20:33     ` Michael Fischer [this message]
2014-05-07 21:25       ` [ANN] unicorn 4.8.3 - the end of an era Eric Wong
2014-05-07 12:08 ` Bráulio Bhavamitra
2014-05-07 20:25   ` Xavier Noria
2014-05-07 20:34     ` Eric Wong
2014-05-07 20:37       ` Xavier Noria

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

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABHxtY6CYM5+tTsLmiNSK=_EAbKjoqmapJWb92=4-SHN1FLg-Q@mail.gmail.com' \
    --to=mfischer@zendesk.com \
    --cc=e@80x24.org \
    --cc=jeremy.lecour@gmail.com \
    --cc=mongrel-unicorn@rubyforge.org \
    --cc=unicorn-public@bogomips.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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).