> All passwords are by default stored as salted SHA512 hash (5000 rounds). Attackers will have hard time to crack your passwords. SHA512 isn't a good choice for this, because it's optimized for fast low-memory computation. Why not use bcrypt or argon2, which are industry-accepted best practices for password hashing?
Their rationale is probably because those two don't scale very well when you want to make their efforts count, whether bcrypt's hunger for CPU or Argon2's hunger for CPU and/or RAM. Bcrypt is very capable at bogging things down when you have lots of users authenticating very frequently, which is often the case with a POP3 server. A mere 100 e-mail clients authenticating every 2 minutes on average to check for new mai…
Poste.io – Complete Mail Server
161–170 of 247 posts
Re: Poste.io – Complete Mail Server
#162Dovecot, Roundcube, ClamAV, Rspamd are all battle-tested and reasonable choices, but the choice of Haraka, a Node.js-based SMTP server, feels dubious. Why not exim or something similarly solid and well-understood?
I generally recommend replacing Roundcube with SnappyMail ( https://snappymail.eu ) -- not having to deal with a database by not maintaining much state is a win. I was expecting to see Postfix instead of Haraka. I wouldn't have been very surprised at exim.
Re: Poste.io – Complete Mail Server
#163Have written a bit about self hosting email[0]. I personally run: - Proton Mail (not self Hosted but for some addresses) - Haraka - Maddy For people new to self hosting email I recommend maddy over the usual postfix + dovecot [0]: https://vadosware.io/post/its-never-been-easier-or-harder-to...
A rather large caevat on Maddy: Note: IMAP storage is "beta". If you are looking for stable and feature-packed implementation you may want to use Dovecot instead. So at this point it replaces postfix.
That warning has been there for a while -- I don't think it's accurate at this point -- You can use SQLite or other DBs to hold your IMAP data:
https://maddy.email/reference/storage/imapsql/
https://maddy.email/reference/blob/fs/
https://maddy.email/reference/blob/s3/
I've used all three of these actually (over the years -- more recently I've moved a bunch of my imapsql workload to S3-compatible storage on Backblaze) and they work great.
If you're sending and receiving gobs and gobs of email maybe think twice, but for someone who is dipping their toes into self-hosting email maddy is one of the best choices out there.
As usual YMMV, and back things up, if they are important to you.
Re: Poste.io – Complete Mail Server
#164I feel like this solution is optimizing the wrong problem. The bulk of work with managing a mail server (these days) isn't software setup and admin. On the receiving side, it's all the work dealing with abuse and attacks. On the sending side -- and this is the tough one -- it's getting sites to accept your email. When I finally gave up managing my own mail server (about two years ago), I found that about every six mo…
Why are the email providers so bad about this? When I check my "spam" filder in Gmail, around half the email is not spam. Is it because humans are so bad at classifying spam?
This is an honest question, in my opinion the only way to make Google more friendly with self-hosted mail servers is their users complaining about or leaving Gmail.
Re: Poste.io – Complete Mail Server
#165I feel like this solution is optimizing the wrong problem. The bulk of work with managing a mail server (these days) isn't software setup and admin. On the receiving side, it's all the work dealing with abuse and attacks. On the sending side -- and this is the tough one -- it's getting sites to accept your email. When I finally gave up managing my own mail server (about two years ago), I found that about every six mo…
I refer to this as ‘the mail cartel problem’.
Re: Poste.io – Complete Mail Server
#166Earlier quoted context omitted.
Isn't 465 safer since 587 uses STARTTLS and STARTTLS can be downgraded?
> since 587 uses STARTTLS and STARTTLS Technically yes, but for the last decade I've seen only one instance where 587 was explicitly STARTTLS (Fastmail), everyone else just running TLS on it.
Re: Poste.io – Complete Mail Server
#167Earlier quoted context omitted.
I’ve been in the Ethereum ecosystem for over six years. I’ve heard “there’s a lot of work being done on…” literally thousands of times. Yet outside of the crypto-sphere I’ve only met a handful of people who’s life would be impacted in the slightest if the entire thing disappeared. Ethereum is eight years old and debates about use cases, etc aside I think even someone towards the middle of the debate can readily ackno…
You must only be following at a pretty surface level if you think "things are being worked on" is just a meme
Re: Poste.io – Complete Mail Server
#168I feel like this solution is optimizing the wrong problem. The bulk of work with managing a mail server (these days) isn't software setup and admin. On the receiving side, it's all the work dealing with abuse and attacks. On the sending side -- and this is the tough one -- it's getting sites to accept your email. When I finally gave up managing my own mail server (about two years ago), I found that about every six mo…
Re: Poste.io – Complete Mail Server
#169Earlier quoted context omitted.
> since 587 uses STARTTLS and STARTTLS Technically yes, but for the last decade I've seen only one instance where 587 was explicitly STARTTLS (Fastmail), everyone else just running TLS on it.
How can I check if a connection is TLS or STARTTLS?
Re: Poste.io – Complete Mail Server
#170I feel like this solution is optimizing the wrong problem. The bulk of work with managing a mail server (these days) isn't software setup and admin. On the receiving side, it's all the work dealing with abuse and attacks. On the sending side -- and this is the tough one -- it's getting sites to accept your email. When I finally gave up managing my own mail server (about two years ago), I found that about every six mo…
THIS. Spam is a solved problem, thanks to SPF and DKIM. But despite doing all the right things, Microsoft and Google continuously block and rate-limit delivery. Case in point: we deliver 20,000 booking confirmation emails every day, all requested by users and not spam. We have perfect Postmaster Tools metrics: absolutely zero reported spam, 100% IP reputation, high domain reputation, zero feedback loop spam, 100% enc…
After the great Gmail exodus two years ago (when they killed then unkilled legacy domain accounts), I moved to MXRoute — and the amount of unfiltered spam I get is insane. It's a daily nuisance. I have added about 200 filter words now, blocked hundreds of e-mail addresses, but it's next to impossible to filter out sometimes.
From conversations and threads online by the MX Route admin, it seems like this is a nearly unsolvable problem, still. Spam evolves so fast and uses throwaway one-time approaches only, so once you've filtered for a pattern, the next campaign looks completely different.
So, yeah, sorry about the long response, but I don't think Spam has been solved, at all, at least not if you're using an e-mail that's been around for longer than a few years (and appeared at least in one leak).