Theo Van Dinter wrote: >On Tue, Feb 28, 2006 at 10:59:29AM -0800, [EMAIL PROTECTED] wrote: > > >>If you're careful about how you call SpamAssassin you can fake envelope rules >>using these headers. >> >> > >It's worth noting that there's a pseudo-header called "EnvelopeFrom" which >is available to header rules which attempts to figure the EnvelopeFrom >value from various headers that MTAs may put in the message. There's also >"envelope_sender_header" which lets you specify which header to use, >which may be necessary depending on your MTA. > >See the Mail::SpamAssassin::Conf POD for more info. :) > > >
Hmmm.... I looked at that, and tried substituting EnvelopeFrom, but it didn't work. What am I missing? Is SA not using the Return-Path: line by default? debug: all '*From' addrs: [EMAIL PROTECTED] [EMAIL PROTECTED] ... debug: SPF: checking EnvelopeFrom (helo=lists-outbound.sourceforge.net, ip=66.35.250.225, [EMAIL PROTECTED]) debug: SPF: query for [EMAIL PROTECTED]/66.35.250.225/lists-outbound.sourceforge.net: result: pass, comment: Please see http://spf.pobox.com/why.html?sender=alsa-devel-admin%40lists.sourceforge.net&ip=66.35.250.225&receiver=mail.redfish-solutions.com: lists-outbound.sourceforge.net A 66.35.250.225 debug: registering glue method for check_for_spf_pass (Mail::SpamAssassin::Plugin::SPF=HASH(0x1701c90)) ... Do I need to use: header EnvelopeFrom =~ /[EMAIL PROTECTED]/ instead? That doesn't seem to work either. -Philip
