| |||||||||||||
|
| |||||||||||||
Debian rejects Sender IDDebian rejects Sender IDPosted Sep 5, 2004 23:48 UTC (Sun) by copsewood (subscriber, #199)Parent article: Debian rejects Sender ID
Fine. Stick with classic SPF which has no such patent problem. M$ SenderID adds no value to this - it takes value away by bloating the SPF format with unneccessary XML, increasing the risk of exceeding the 500 byte DNS record threshold where you have to transition from UDP to TCP DNS lookup - making the whole thing unworkable. The reason some SPF developers have agreed to include SenderID in the proposed RFC is political, not technical, as this multiplies the clients likely to implement SPF/SenderID soon by a factor of 10. If my reading of the SPF list is correct, in practice, I think this standard proposal is likely to include classic SPF as the base implementation, and this is what will be used in practice as opposed to theory.
(Log in to post comments)
|
|
||||||||||||