> -----Message d'origine----- > De : Mike Harrington [mailto:[EMAIL PROTECTED] > Envoy=E9 : mardi 7 juin 2005 03:56 > =C0 : [email protected] > Objet : [xmail] Re: senderid >=20 >=20 > Microsoft's Sender ID I think is pretty much dead in the=20 > water as it sits,
Agree, as Microsoft patented some (all ?) portion, and you 'could' need = a licence to use it. At this time Microsoft position is not clear about a 'royalty free = licence' of sendid id. >=20 > Both are rather pointless in my opinion because they only=20 > prove where a > message comes from. Spammers can (and have) create SPF records for > themselves. Just because you can use Sender ID / SPF to prove where = a > message comes from, doesn't mean it's not spam. >=20 > -Mike >=20 I disagree. Yes, a spammer can create spf records for its owned domains then send = spam. BUT to add spf records in a dns zone, the spammer must be able to write = to the zone files. And if the spammer can, you have more changes to find and fight the = spammer : only persons that have write access to the zone ;-) (you can simply stop the domain at smtp level, like=20 This limits drasticaly the number of possible spammers at domain zone = level !! If a isp uses spf records (on any hosted domains) and force its = customers to authenticate to send mail, then if the spammer is a isp customer, you = can point back to it at isp level ... Spf, sender-id, signed mails, domain keys, ... thatever is the final preferred 'choice' on internet, will be more powerfull and more = difficult to bypass as more and more internet users (particulary isp's first) use it = .... up to the time it will become naturaly 'mandatory' when installing a = smtp server or domain because without you can't send any mail anymore ... Francis Francis - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
