Re: Cool things to do with server
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 15/03/15 09:11, Joris Bolsens wrote:
>> Mail server,
> I thought about this, but from what i understand, mail servers are
> notoriously difficult to secure properly.
The crucial bit is ensuring you don't openly relay all mail. Only
traffic from your authorised users.
That's the major tricky bit. Nothing worse than coming home to a
modem running red hot and a mail queue crammed with Viagra spam.
(Been there, done that. On dial-up too no less.)
The only issue you might hit is port 25/tcp being blocked by your ISP.
You may have to relay outbound email via their SMTP server. Even if
it's blocked inbound too, you can still use something like `fetchmail`
to grab mail from POP3 and IMAP mailboxes anywhere and present all
your email as one homogeneous mailbox with as much space as you like.
This was one of the reasons I don't use Gmail: I had a >1GB mailbox
back in 2002, a time when the average webmail account offered about
10MB. Having gotten it working, I see no reason to move.
I've been hosting a number of websites on mine (which runs Gentoo, but
the same can be achieved in Debian). At the moment it's a "shared
hosting" arrangement but I'm starting to look into moving to LXC.
(The machine is an Intel Atom with no VT extensions, so no KVM for me.)
Using LXC then, your host can basically just act as a router/firewall
and reverse proxy (using Apache/nginx for http; sniproxy for https)
and your actual hosted services are on internal containers in a
virtual DMZ.
Spinning up minimal LXC instances using deboostrap is a synch and they
take very little disk space.
- --
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJVDyztAAoJEE36GRQQveO3nHcP/2Y2DsWyTZuYmbM8ErqQnvZX
ri2v41cnLjvElBOaD7KIcLTCIzmSGJRnkOjFqO76nERAShSsVRW6oU3hNA64tHkQ
LCR2Du96b5xOCiNPJTP2czznWc9bCBOpzzBwKtKIIqwsoBIIteWcs99cOz4iEzSg
F1Vc62R/PhBDe8goR/oV0KibQq83PvnUbOfEbujT+jB89cj+WfHByEaBw4aHEo+Q
08iL6ifWXYUe7LqPNNAL3knqCLTh9kNLJf0Le8GI5cYpY0TBXxLmd+66T96u2L57
+PIe0qu2H6Ufj1IIPi1/H8L0OLPrPL82zuNTY2JGN+6ywZR2+24xtvL7bio6d6ex
pu4VDi0QoABIeoMaOt17IRXH3b3v61GtLwfp5Y6vH+RoC8gjfLViW4FNzwO/JF2g
q6ZlMyPoyHth80ajfxywDXBOAuzDmcCrPq90Icde5ipGxo9rQes0XR9QQh9LnxpL
Q5ZdfQVDIafDDfGSQ5D/cBvy1UzP4fIa+mkoZvdW4rKlTD1fLrtpAp59rAu27X99
d6u1myOk8MJ0yTKT6EXXmlL9d8GJ86d7mRNj7WBhgjc5MUIohMHkWe5EGDWJ7agj
n8hzDwvOlW4YbMSy4VBBjvA0Js2Pkey6W3CVjaMaQLxlpMAHSQ+WyeomusUNAsiR
IdK7DqzJaaL1JtuONJlK
=ji8H
-----END PGP SIGNATURE-----
Reply to: