On 04/16, Rob Arista wrote: > I can't see how to get SA to add a 'Received-Spf' like described here, > to use it further downstream:
I believe the only way SA can add headers is with the "add_header" config option: http://spamassassin.apache.org/full/3.3.x/doc/Mail_SpamAssassin_Conf.html#item_add_header__7b_spam__7c_ham__7c_all__7d_header_nam Or man Mail::SpamAssassin::Conf But it can only add headers beginning with X-Spam-. So you might be able to add a header with that, and then use procmail or something to add your Received-SPF header based on a X-Spam-Received-SPF header. But you would probably still need to write a SA plugin to do it. The better option is probably to add the Received-SPF header at your MTA. With postfix, I use https://launchpad.net/postfix-policyd-spf-perl/ It would be nice if SA could then use this header instead of checking SPF again itself, but since it's silly to run SA without a local caching DNS server anyway, it shouldn't be significant additional overhead to do it twice. -- "Safe is anywhere a hungry person can't walk in three days." - John Titor http://www.ChaosReigns.com
