-----Original Message-----
From: owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
[mailto:owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com] On Behalf Of
Richard Bang
Sent: woensdag 1 december 2004 11:05
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: [spf-discuss] Multiple header entries
Hi,
What should be the policy if an MTA received a message with
an spf header already in it. Should it remove the header and add
its own, or just add a new one and leave the original intact.
(I would assume the latter as it makes the processing history
more intact).
The 'official' status of the SPF-Received: header is a bit in limbo, I
believe. But like regular Received: headers, you could follow the practice
of adding one 'on top', and leave the older ones be; like so:
Received-SPF: pass (asarian-host.net: domain of
listbox+trampoline+735+865569+5f71ec8d(_at_)v2(_dot_)listbox(_dot_)com
designates
207.8.214.5 as permitted sender)
Received-SPF: pass (backbone.midwestcs.com: domain of midwestcs.com
designates 206.222.212.237 as permitted sender) client-ip=206.222.212.237;
envelope-from=wayne(_at_)midwestcs(_dot_)com; helo=midwestcs.com;
Adding the hostname of the receiving machine ($j in sendmail) right after
the first bracket makes for an easy history trail.
- Mark
System Administrator Asarian-host.org
---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx