<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>fuzzy2</author><text>Most spam I receive (and that continues to somehow bypass my spam filters) originates from Gmail. So no, spam is not solved, not at all.&lt;p&gt;Spam is only “solved” on big providers because they mostly accept mails only from other big providers.&lt;p&gt;---&lt;p&gt;I would argue that “running an independent mail server” and mass-mailing are two entirely separate concerns.</text><parent_chain><item><author>foxylad</author><text>THIS.&lt;p&gt;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.&lt;p&gt;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% encryption. But Gmail still rate-limits us daily, so their customers get their booking confirmations several hours late.&lt;p&gt;It&amp;#x27;s getting to the point where running an independent mail server is impossible. Yet another part of the open internet bites the dust.</text></item><item><author>that_courtney</author><text>I feel like this solution is optimizing the wrong problem.&lt;p&gt;The bulk of work with managing a mail server (these days) isn&amp;#x27;t software setup and admin. On the receiving side, it&amp;#x27;s all the work dealing with abuse and attacks. On the sending side -- and this is the tough one -- it&amp;#x27;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 months I was involved in some panic where some large mail provider (Microsoft and Google most frequently) decided they didn&amp;#x27;t want to accept email from my server. Solving these issues is neither easy nor quick.&lt;p&gt;These days I&amp;#x27;m very happy to pay somebody else to run email services using my provided domains.</text></item></parent_chain></comment><story><title>Poste.io – Complete Mail Server</title><url>https://poste.io/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>franga2000</author><text>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&amp;#x27;s where the majority of spam comes from, so it&amp;#x27;s far from a solved problem.</text><parent_chain><item><author>foxylad</author><text>THIS.&lt;p&gt;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.&lt;p&gt;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% encryption. But Gmail still rate-limits us daily, so their customers get their booking confirmations several hours late.&lt;p&gt;It&amp;#x27;s getting to the point where running an independent mail server is impossible. Yet another part of the open internet bites the dust.</text></item><item><author>that_courtney</author><text>I feel like this solution is optimizing the wrong problem.&lt;p&gt;The bulk of work with managing a mail server (these days) isn&amp;#x27;t software setup and admin. On the receiving side, it&amp;#x27;s all the work dealing with abuse and attacks. On the sending side -- and this is the tough one -- it&amp;#x27;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 months I was involved in some panic where some large mail provider (Microsoft and Google most frequently) decided they didn&amp;#x27;t want to accept email from my server. Solving these issues is neither easy nor quick.&lt;p&gt;These days I&amp;#x27;m very happy to pay somebody else to run email services using my provided domains.</text></item></parent_chain></comment><story><title>Poste.io – Complete Mail Server</title><url>https://poste.io/</url></story>