Even hosts that correctly implement $CURRENT_YEAR's email security dance end up on spam lists erroneously. The problem is allowing these hosts to have that much influence to begin with. The creation and spreading of those lists is pernicious to the protocol, but in absence of new RFCs and matching client behavior, I see the need to add some light 'hazing' to setting up e-mail.
The problem is when Google tells everyone your site is spam and they listen. Tech can't solve that problem.
Even hosts that correctly implement $CURRENT_YEAR's email security dance end up on spam lists erroneously. The problem is allowing these hosts to have that much influence to begin with. The creation and spreading of those lists is pernicious to the protocol, but in absence of new RFCs and matching client behavior, I see the need to add some light 'hazing' to setting up e-mail.
The problem is when Google tells everyone your site is spam and they listen. Tech can't solve that problem.