A sender was a circuit in a 20th century electromechanical telephone exchange which sent telephone numbers and other information to another exchange. In some American exchange designs, for example 1XB switch the same term was also used to refer to the circuit that received this information. A telephone operator manually connecting calls with patch cables at a telephone switchboard. ... The Number One Crossbar Switching System was the primary urban local telephone exchange design used by the Bell System in the middle 20th century. ...
If these people use SPF to specify their legitimate senders, the number of error messages may be reduced because receivers implementing SPF will know that the message is forged.
In particular, if a sender provides SPF information, and the receiver uses it, the receiver has some justification in believing that the email at least came from the domain that it asserts it came from.
One solution is for the SPF record to specify the forwarder as an allowed sender, but this is problematic because the sender has no idea in general what aliases the receiver might have configured.
Sender ID was an anti-spam proposal from the MARID IETF working group that joined Sender Policy Framework and Caller ID.
The MARID IETF working group stopped their work on the proposed standard on September 23, 2004 because of various problems and major differences between the members of the group.
SPF Claws Sender-ID. In late August, 2005, changes to the Sender-ID Framework experiment triggered a response from the Sender Policy Framework council that threatened doom for both projects.