You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by Apache Wiki <wi...@apache.org> on 2008/06/20 12:22:26 UTC

[Spamassassin Wiki] Update of "DynablockIssues" by CarlosVelasco

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The following page has been changed by CarlosVelasco:
http://wiki.apache.org/spamassassin/DynablockIssues

The comment on the change is:
Postfix 2.5+ RFC 3848

------------------------------------------------------------------------------
  '''Note: The problem described was fixed in version 3.0.2.'''  However, some MTAs such Postfix don't support RFC 3848 and will therefore still exhibit the described problem since SpamAssassin won't be able to automatically trust authenticated users if the MTA doesn't leave a supported authentication token in the relay's Received header.
  
  '''Update (2006-07-14): Postfix 2.3 includes support''' for adding its own style of authentication info to its received headers by setting ''smtpd_sasl_authenticated_header = yes'', which is disabled by default, in your Postfix config.  '''SpamAssassin 3.1.4''' and later includes support for this Postfix auth info.
+ 
+ '''Update (2008-06-20): Postfix 2.5+ includes native support RFC 3848''' setting ''smtpd_sasl_authenticated_header'' is not needed but optional.
+ 
  
  ["madduck"]: This will not fix TLS-authenticated sessions. See [http://dev.riseup.net/privacy/postfix/ this patch] which munges the Received headers.  ["DarylC.W.O'Shea"]: This should work to avoid the Dynablock problem in this specific situation but isn't recommended since it destroys the audit trail provided by the Received headers.