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

241–247 of 247 posts

Re: Poste.io – Complete Mail Server

#241

Post by kevincox »

franga2000 wrote: post #158
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 is spam related to SPF and DKIM? Those prevent forgery, but if a spammer actually owns a domain, they can send you whatever they want. That's where the majority of spam comes from, so it's far from a solved problem.

SPF and DKIM allow using domain reputation instead of IP reputation. Especially with IPv6 IPs are fairly easy to aquire and can be "stolen" either by spoofing/highjacking the network or more easily by compromising some hosts and sending from there. Hijacking a domain is generally harder as you need to compromise a mail server to get both the IP and DKIM key. And there are less mail servers than WordPress instances to hijack.

Sure, you can buy domains but that leaves some paper trail and generally you will see added spam scores for new domains.

So SPF and DKIM don't improve spam scores on their own, but the give a much more reliable path to building reputation.

Re: Poste.io – Complete Mail Server

#242

Post by account42 »

geocrasher wrote: post #93
johnklos wrote: post #80

Earlier quoted context omitted.

You can't forward email to Gmail - they'll blame your server for forwarded spam regardless of everything else being correctly set up. This is true to an extent for other providers, too. The simplest solution is to set up IMAP on your mail server and have remote mail accounts fetch from it. Most email providers can be configured to fetch via IMAP.

^^^ This ^^^ The problem is that there is no such thing as mail forwarding. It is mail re-sending. So, you get a piece of spam and re-send it to Google, and the From address isn't the spammer, it's you. They'll eventually block the email address, and then the whole domain it's on. Don't forward. SMTP. SMTP is authenticated, which solves the issue.

There is such a thing as mail forwarding - it just doesn't work with SPF. In fact, since submission and outbound connections are both SMTP pretty much all mail servers to happily forward mail from your client to another server - only with domain and authentication restrictions, but those are not required by the protocol.

Re: Poste.io – Complete Mail Server

#243

Post by 867-5309 »

account42 wrote: post #239
867-5309 wrote: post #196

Earlier quoted context omitted.

some users have javascript disabled, some have email clients disabled. it's not foolproof but works for the majority of users, i.e. >99%

Any any well designed website will work with javascript disabled unless it is absolutely needed for the task (i.e. we are talking about an actual app). There is also no guarantee that the image being loaded means that the user opened the mail and it wasn't just preemptively cached by the server/client. There is also no guarantee that the user opening the mail means they read it.

have you seen the web lately? javascript is increasingly being used on backend. not just for apps, for static one page sites too. those who disable javascript do not have a pleasant browsing experience and are forced to enable it often

I'm not here to guarantee anything, just mentioning the technology exists and is still widely employed. there are no guarantees with messaging app ticks either

Re: Poste.io – Complete Mail Server

#244

Post by 867-5309 »

account42 wrote: post #238
867-5309 wrote: post #181

Earlier quoted context omitted.

>It's so annoying if mail is accepted but you don't know if it is actually seen by the recipient. that's what those embedded 1x1px images are for

Are you sure those are GDPR-compliant? Just because you can do something doesn't mean that you should.

I have no idea, but doubt they are mentioned specifically

Re: Poste.io – Complete Mail Server

#245

Post by throwaway892238 »

AnonC wrote: post #172
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…

I'm not the OP/creator and have no affiliation with it. On the first two points, I thought the snark in this comment could be accepted had it been followed with more useful information and pointers along with the criticism. A one line criticism and attack isn't helping anyone and doesn't help us have "curious conversation" that HN asks users to promote.

Not every comment has to be a lecture from an academic, despite how much the mods want that to boost their forum's rep

Re: Poste.io – Complete Mail Server

#246

Post by pbreit »

ponytech wrote: post #164
pbreit wrote: post #130

Earlier quoted context omitted.

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?

May I ask, why are you still using Gmail then? 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.

I can't even think of another provider. And Gmail is otherwise quite amazing.
Post reply on HN