On 12/19/2010 11:31 PM, jida...@jidanni.org wrote: > Gentlemen, I wish there was a > whitelist_from *...@facebookmail.com > rule that would use the Return-Path field, > > $ egrep '^(From|Return-Path):' a b > a:Return-Path: <notification+zj4oo-6-6...@facebookmail.com> > a:From: Facebook <notification+zj4ooo699...@facebookmail.com> > b:Return-Path: <chanetho...@hotmail.com> > b:From: Facebook <update+3ttttttxy...@facebookmail.com> > > as that is much more reliable. > > I see there are other whitelist_ rules, but none that can use what is > already staring one in the face in the headers, and does not need to go > on the network to work. > Hmm, from what I though whitelist_from *SHOULD* match Return-Path: headers, provided they are present in the message at the time it is scanned.
However, looking at all_from_addrs.. that doesn't appear to be the case. This seems to be inconsistent with metadata/Received.pm, which looks to be translating Received: header embedded Return-Path's in to a From: meta-data. Anyone recall while we're taking one kind of Return-Path, but not the other (or am I just missing where the transform happens?)
