Live data from Hacker News

Mail-in-a-Box

mailinabox.email

71–80 of 91 posts

Re: Mail-in-a-Box

#71

I have a Linode VPS and am happy to fire up another VPS to handle email exclusively. In fact, I already did and installed Mail in a Box as mail.mydomain.com. I have to say (being a developer with enough Linux knowledge to handle hosting and simple stuff) that nameserver setup is completely confusing. I should stop using Linode nameservers? If so, I should set up glue records and place that into NameCheap domain speci…

Hi, metadata.

It sounds scary to set up glue records, but so is setting up all of the DNS records manually that you'd need for really good mail: MX, SPF, DKIM, and DMARC, and if you want secure DNS and/or mandatory encryption on the wire you'll want DANE records and zone signing.

Mail-in-a-Box wants to take over your DNS because it wants to take care of all of this for you. If you run your own DNS, it's still secure. An alternative is to use a new domain name.

Thanks for the feedback.

[I'm the guy behind the project.]

Re: Mail-in-a-Box

#72

I have a Linode VPS and am happy to fire up another VPS to handle email exclusively. In fact, I already did and installed Mail in a Box as mail.mydomain.com. I have to say (being a developer with enough Linux knowledge to handle hosting and simple stuff) that nameserver setup is completely confusing. I should stop using Linode nameservers? If so, I should set up glue records and place that into NameCheap domain speci…

Hi, metadata. It sounds scary to set up glue records, but so is setting up all of the DNS records manually that you'd need for really good mail: MX, SPF, DKIM, and DMARC, and if you want secure DNS and/or mandatory encryption on the wire you'll want DANE records and zone signing. Mail-in-a-Box wants to take over your DNS because it wants to take care of all of this for you. If you run your own DNS, it's still secure.…

I had the same problem. Also, I had some DKIM and SPF already configured to external SMTP server.

I understand your message, but it is not clear in Mail-in-a-Box interface. What exactly is the problem with my own DNS server? If I want to work without DANE, I can just add all these new records to my DNS and it works out of the box?

I started to setup a personal email server several times and abandoned it because it is just too difficult. This time, it was easy. Thanks!

Re: Mail-in-a-Box

#73

It's a great idea except that for one person it's going to cost a lot more than buying an account on FastMail (disclaimer: I work there) or any of the other hosting sites (even before you start start thinking redundancy and backups - we have about 10Tb of disk for every 1Tb of pure email quota, by the time you count search indexes and RAID and 3x replication redundancy - two local one offsite) For more than one perso…

If you want to give someone else the access and control for your correspondence, there are many cheaper alternatives than being personal responsible for it.

Personally however, I am willing to pay to keep my private communication private. In my professional role, I consider it a requirement.

Re: Mail-in-a-Box

#74

I have a Linode VPS and am happy to fire up another VPS to handle email exclusively. In fact, I already did and installed Mail in a Box as mail.mydomain.com. I have to say (being a developer with enough Linux knowledge to handle hosting and simple stuff) that nameserver setup is completely confusing. I should stop using Linode nameservers? If so, I should set up glue records and place that into NameCheap domain speci…

Hi, metadata. It sounds scary to set up glue records, but so is setting up all of the DNS records manually that you'd need for really good mail: MX, SPF, DKIM, and DMARC, and if you want secure DNS and/or mandatory encryption on the wire you'll want DANE records and zone signing. Mail-in-a-Box wants to take over your DNS because it wants to take care of all of this for you. If you run your own DNS, it's still secure.…

I had problems getting Hover to make glue records for the IP address. I just ended up having to manually enter in the DNS information myself.

Re: Mail-in-a-Box

#75

Earlier quoted context omitted.

I will look into creating a .deb package. No $100 necessary for me. My email address is in my profile, I'd anyone wants to connect before I can put together a pull request.

Hey. Please start an issue on github sooner rather than later so you don't do lots of work and then I end up rejecting the PR. :) Communication! [I'm the guy behind the project.]

Will do. Sorry, I am really short on time this weekend but I will reach our first thing Monday.

Re: Mail-in-a-Box

#77

Earlier quoted context omitted.

I will look into creating a .deb package. No $100 necessary for me. My email address is in my profile, I'd anyone wants to connect before I can put together a pull request.

Hey. Please start an issue on github sooner rather than later so you don't do lots of work and then I end up rejecting the PR. :) Communication! [I'm the guy behind the project.]

I have a use for this at CC if we can get it working on Debian wheezy.

Thanks for releasing this under CC0.

Re: Mail-in-a-Box

#78
post #39

what you need: A completely fresh Ubuntu 14.04 machine Bummer. I already have a server running and don't plan on paying for an extra instance just for mail. Has anyone tried this with VirtualBox or some other virtualization? Should work if the correct ports are forwarded, no?

There's a Vagrantfile in the project. I haven't used it in production this way, but it should work. [I'm the guy behind the project.]

Ah, will try.

Re: Mail-in-a-Box

#79
post #42

What about a backup SMTP server? I ran my own mail server for a year and found it incredibly stressful. Switched to runbox.com and I couldn't be much happier atm.

Unless you have very long downtimes, a backup server shouldn't be needed. SMTP is designed to handle such problems and keep trying for at least four or five days.

Re: Mail-in-a-Box

#80

The problem is not setting up an email server; the problem is in ensuring you email is delivered/visible. I set up an email server vps with my domain and domain keys etc but my test emails to my family ,who use Yahaoo and Gmail, would not get delivered. I gave up !

Setting up my own mail server a couple years ago i had this problem. The "best" solution seemed to be routing through a service like gmail, which defeated the purpose.

It doesn't completely defeat the purpose, because they would only get your outbound emails, not received ones.
Post reply on HN