Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Poste.io – Complete Mail Server

poste.io

Post reply on HN
Print view View original

121–130 of 247 posts

Re: Poste.io – Complete Mail Server

#121

Post by throwaway892238 »

> All passwords are by default stored as salted SHA512 hash (5000 rounds). Attackers will have hard time to crack your passwords.

Tell me you don't know about password security without telling me you don't know about password security

> SMTP - port 25, 465 (TLS), 587

Tell me you don't follow RFCs without telling me you don't follow RFCs

> https://poste.io/doc/license

    you are allowed to run unlimited count of instances for your own use only
    you can't sell or distribute container images to third parties, every mailserver operator needs to have its own license
Rather take the 3 hours to just set up all that FOSS software myself and give it away to everyone for free but thanks anyway

Re: Poste.io – Complete Mail Server

#123

Post by brightball »

foxylad wrote: post #116
that_courtney wrote: post #13

I 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…

How many servers do you have? Just curious if the rate limit is per IP address?

Re: Poste.io – Complete Mail Server

#124

Post by anaganisk »

throwaway892238 wrote: post #121

> All passwords are by default stored as salted SHA512 hash (5000 rounds). Attackers will have hard time to crack your passwords. Tell me you don't know about password security without telling me you don't know about password security > SMTP - port 25, 465 (TLS), 587 Tell me you don't follow RFCs without telling me you don't follow RFCs > https://poste.io/doc/license you are allowed to run unlimited count of instance…

At least they are hashing and not storing encrypted passwords. But even a baby framework with may be 10s of deployments have switched to bcrypt, etc. Im not sure why they're boasting about SHA512. But I am a little lost on the RFC thing. Could you enlighten me. I thought they were standard ports for legacy,TLS, and SSL ports.

Re: Poste.io – Complete Mail Server

#125

Post by TedDoesntTalk »

brightball wrote: post #123
foxylad wrote: post #116

Earlier quoted context omitted.

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…

How many servers do you have? Just curious if the rate limit is per IP address?

We have a Microsoft email subscription (all our mail is hosted with them), and their smtp server rate limits how much mail we send to our customers. We can’t even send 30 emails at once. We had to implement retry logic with back off.

Re: Poste.io – Complete Mail Server

#126

Post by CommitSyn »

daydream wrote: post #114
orangepurple wrote: post #113

Earlier quoted context omitted.

Life is so easy if you just hand over your personal agency to monopolies and billionaires who don't actually care about you /s

If the alternative is that your construction firm fails and you and everyone else are out of a job - well your email hosting choice is a weird hill to die on.

(the '/s' means 'sarcasm' and that wasn't the user you replied to)

Re: Poste.io – Complete Mail Server

#128

Post by hanniabu »

foxylad wrote: post #116
that_courtney wrote: post #13

I 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…

Really hoping ENS can step in here and fill this gap. There's a lot of work being done on social and messaging infrastructure. Using that as an email and chat handle and social handle would be huge for maintaining open messaging. Unfortunately this relies on adoption and people living past their bias and admitting there's use cases.

Re: Poste.io – Complete Mail Server

#129

Post by rapind »

gerdesj wrote: post #106
c0l0 wrote: post #23

Earlier quoted context omitted.

Having been a part-time postmaster for more than a decade by now, I fully agree, and would even go further: Ingress spam is pretty much a solved problem if you play your cards right. ChatGPT et al. might change that again - but the mechanisms you can deploy today are very effective against the current UBE landscape. The _real_ problem is reliably getting your 100% legit mail into your consenting recipients' inboxes.

I've been doing it for well over 20 years now. Ingress - out of the box rspamd is pretty decent and it is rather configurable. Egress - DNS (A,AAAA, PTR), (E)HELO, SPF, DKIM, DMARC. "IP Reputation". There are absolutely no shortcuts and yet most of the problems I diagnose regarding email delivery will find a missing PTR record or a miss-configured (or non configured) HELO. You cannot be lazy when it comes to email. S…

> Egress - DNS (A,AAAA, PTR), (E)HELO, SPF, DKIM, DMARC. "IP Reputation".

Any insight into why this is a giant ball of complexity? I’ve had to setup spf, dkim, dmarc a couple times now and man… design by committee?

Re: Poste.io – Complete Mail Server

#130

Post by pbreit »

that_courtney wrote: post #13

I 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?
Post reply on HN