3 ms·

> interoperable and we can easily send e-mails to users of any server without breaking our heads and wondering whether their servers and clients will understan

> interoperable and we can easily send e-mails to users of any server without breaking our heads and wondering whether their servers and clients will understand that Not sure this holds true anymore in practice. Try to set up your own email server, your emails will probably get sent to spam by gmail, yahoo etc. Sure, it is technically possible, but it is time consuming and still risky to use it for business. At least you can still use your own domain and switch providers (google apps, outlook etc).

xorcist 11y ago
> Try to set up your own email server, your emails will probably get sent to spam by gmail, yahoo etc. That problem is so overstated it's not even funny. Your email will get sent to spam if your IP adress is blacklisted, or if you send spam. It's actually gotten harder to get blacklisted over time, as people has gotten more tolerant towards semi-spam ("newsletters" and stuff) and people are generally more conservative in blacklisting whole networks these days. Don't misbehave. Don't be a bad net citizen. Get your net and DNS in order, and the default Debian set up of postfix will do you just fine. I do it and most of my customers over the years have done it too. Some outsource their spam filtering, a few outsource their whole email, but most outside the small startup world still tend to keep their own mail server.
- patrickaljord 11y ago
  > Don't misbehave. Don't be a bad net citizen. Get your net and DNS in order That's not the kind of things I want to worry about. Most companies have business to run with problems of their own, thinking about DNS config and all the rules to be a good citizen (besides obvious spamming) sounds like headache and unneeded complexity to most companies. Not to mention backups, having to pay dedicated admins etc. > most outside the small startup world still tend to keep their own mail server Not sure about that: https://www.google.com/work/search/customers/ https://www.google.com/work/search/customers/ https://products.office.com/en-us/business/office-365-customer-stories-office-testimonials https://products.office.com/en-us/business/office-365-custom...
- bluegate010 11y ago
  I just recently had weeks of headaches over getting my server's email sent to spam. After setting up a brand new domain, with SPF, DKIM, etc., I woke up one morning to find my domain wasn't resolving. Eventually I learned it was because Radix, my TLD registry, had noticed my domain on the Spamhaus Domain Blocklist. Who knows why it was added; I definitely hadn't been sending spam. Radix, being proactive, placed a 'serverHold' DNS status on my domain name, preventing it from resolving. Luckily Spamhaus has an automated form for dealing with false positives. Eventually Radix removed the status. (Though, a week later it was back up, for no reason. Had to badger them for over a week to get the status removed again. Would not recommend them.) It's very lucky I wasn't trying to do anything with that domain like run a business, or rely on @<domainname> addresses to work. TL;DR the problem is definitely not overstated.
  - xorcist 11y ago
    I think that's a good example of overstating the problem right there. Who knows why it was added? Well, it certainly wasn't because you hadn't outsourced your email. Your registry could (and probably would) have put your domain on hold independently of where your MX points. Nothing short of choosing another TLD will protect you from your registry playing games with you.
chei0aiV 11y ago
The problem is well documented, here is one post from last year: https://sfconservancy.org/blog/2015/sep/15/email/ https://sfconservancy.org/blog/2015/sep/15/email/

xorcist 11y ago

> Try to set up your own email server, your emails will probably get sent to spam by gmail, yahoo etc. That problem is so overstated it's not even funny. Your email will get sent to spam if your IP adress is blacklisted, or if you send spam. It's actually gotten harder to get blacklisted over time, as people has gotten more tolerant towards semi-spam ("newsletters" and stuff) and people are generally more conservative in blacklisting whole networks these days. Don't misbehave. Don't be a bad net citizen. Get your net and DNS in order, and the default Debian set up of postfix will do you just fine. I do it and most of my customers over the years have done it too. Some outsource their spam filtering, a few outsource their whole email, but most outside the small startup world still tend to keep their own mail server.

patrickaljord 11y ago
> Don't misbehave. Don't be a bad net citizen. Get your net and DNS in order That's not the kind of things I want to worry about. Most companies have business to run with problems of their own, thinking about DNS config and all the rules to be a good citizen (besides obvious spamming) sounds like headache and unneeded complexity to most companies. Not to mention backups, having to pay dedicated admins etc. > most outside the small startup world still tend to keep their own mail server Not sure about that: https://www.google.com/work/search/customers/ https://www.google.com/work/search/customers/ https://products.office.com/en-us/business/office-365-customer-stories-office-testimonials https://products.office.com/en-us/business/office-365-custom...
bluegate010 11y ago
I just recently had weeks of headaches over getting my server's email sent to spam. After setting up a brand new domain, with SPF, DKIM, etc., I woke up one morning to find my domain wasn't resolving. Eventually I learned it was because Radix, my TLD registry, had noticed my domain on the Spamhaus Domain Blocklist. Who knows why it was added; I definitely hadn't been sending spam. Radix, being proactive, placed a 'serverHold' DNS status on my domain name, preventing it from resolving. Luckily Spamhaus has an automated form for dealing with false positives. Eventually Radix removed the status. (Though, a week later it was back up, for no reason. Had to badger them for over a week to get the status removed again. Would not recommend them.) It's very lucky I wasn't trying to do anything with that domain like run a business, or rely on @<domainname> addresses to work. TL;DR the problem is definitely not overstated.
- xorcist 11y ago
  I think that's a good example of overstating the problem right there. Who knows why it was added? Well, it certainly wasn't because you hadn't outsourced your email. Your registry could (and probably would) have put your domain on hold independently of where your MX points. Nothing short of choosing another TLD will protect you from your registry playing games with you.

chei0aiV 11y ago

The problem is well documented, here is one post from last year: https://sfconservancy.org/blog/2015/sep/15/email/ https://sfconservancy.org/blog/2015/sep/15/email/