From: pechter@gmail.com (William Pechter)
Subject: [TUHS] Who is running their own mail server and what do you run?
Date: Wed, 20 Sep 2017 15:54:04 -0400 [thread overview]
Message-ID: <6a3a0d10-61e0-4b5c-b770-0a74946432f3.maildroid@localhost> (raw)
In-Reply-To: <20170920192553.6t5vobzybqzeyjh4@matica.foolinux.mooo.com>
Never used their support. I keep nothing
important on the server.
I back up my stuff to my house over SSH with rsync.
They have zfs snapshots and a remote console over web browser, so if I break it I fix it or reinstall.
If I get into too much trouble they do have support. I am running from the bootable install they supplied and I used freebsd-update to go from 10.3 to 11.1 IIRC.
Bill
-----Original Message-----
From: Ian Zimmerman <itz@very.loosely.org>
To: tuhs at minnie.tuhs.org
Sent: Wed, 20 Sep 2017 15:26
Subject: Re: [TUHS] Who is running their own mail server and what do you run?
On 2017-09-20 14:22, William Pechter wrote:
>> exim on a VPS. Currently it is a linode running debian but I will
>> have to find an outlet that supports BSD before systemd becomes
>> unavoidable on debian, which I'm afraid is only a matter of time.
> Digital Ocean does FreeBSD for me. My mail hosting costs me $5 per
> month. Using postfix and zfs...
I try to choose my words carefully, and here I wrote "supports" on
purpose even though it is a much overused word.
Linode will let me run FreeBSD, no problem, but they will not support
it. That means, for example, no backups.
So when you write that DO "does" FreeBSD, how far do they go on the
support scale?
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
Do obvious transformation on domain to reply privately _only_ on Usenet.
next prev parent reply other threads:[~2017-09-20 19:54 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 16:25 Larry McVoy
2017-09-20 16:39 ` Jon Steinhart
2017-09-20 19:59 ` Bakul Shah
2017-09-20 21:26 ` Jon Steinhart
2017-09-20 23:17 ` Robert Brockway
2017-09-21 0:00 ` Dave Horsfall
2017-09-21 0:08 ` Grant Taylor
2017-09-21 0:55 ` Dave Horsfall
2017-09-21 1:52 ` Grant Taylor
2017-09-21 4:14 ` Dave Horsfall
2017-09-21 5:30 ` Grant Taylor
2017-09-21 15:43 ` Ian Zimmerman
2017-09-21 0:38 ` Robert Brockway
2017-09-21 1:30 ` Lawrence Stewart
2017-09-21 1:57 ` Grant Taylor
2017-09-21 3:04 ` Robert Brockway
2017-09-21 5:20 ` Grant Taylor
[not found] ` <20170921042528.E12C5156E523@mail.bitblocks.com>
2017-09-21 4:45 ` Robert Brockway
2017-09-21 4:58 ` Dave Horsfall
2017-09-21 5:34 ` Grant Taylor
2017-09-21 15:49 ` Ian Zimmerman
2017-09-20 16:46 ` Warner Losh
2017-09-20 17:01 ` Steve Nickolas
2017-09-20 17:39 ` Henry Bent
2017-09-20 22:54 ` Greg 'groggy' Lehey
2017-09-20 16:59 ` Kurt H Maier
2017-09-20 17:10 ` Arthur Krewat
2017-09-20 17:14 ` Jon Steinhart
2017-09-20 18:15 ` Arthur Krewat
2017-09-20 23:45 ` Dave Horsfall
2017-09-20 22:54 ` Steve Simon
2017-09-20 23:31 ` Grant Taylor
2017-09-20 23:57 ` Bakul Shah
2017-09-21 0:02 ` Larry McVoy
2017-09-21 1:08 ` Ian Zimmerman
2017-09-21 12:36 ` Steve Simon
2017-09-20 17:47 ` Clem Cole
2017-09-20 17:54 ` Rico Pajarola
2017-09-20 17:57 ` Ian Zimmerman
2017-09-20 18:22 ` William Pechter
2017-09-20 19:11 ` Grant Taylor
2017-09-20 19:25 ` Ian Zimmerman
2017-09-20 19:54 ` William Pechter [this message]
2017-09-20 19:09 ` Grant Taylor
2017-09-20 23:26 ` Michael Parson
2017-09-20 18:21 ` Grant Taylor
2017-09-20 18:51 ` Corey Lindsly
2017-09-20 20:13 ` jason-tuhs
2017-09-20 22:25 ` Theodore Ts'o
2017-09-20 23:06 ` Dave Horsfall
2017-09-21 12:40 ` Ben Greenfield
2017-09-23 9:12 ` Dario Niedermann
2017-09-21 20:05 Norman Wilson
2017-09-21 21:02 ` Grant Taylor
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=6a3a0d10-61e0-4b5c-b770-0a74946432f3.maildroid@localhost \
--to=pechter@gmail.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).