Vili wrote: >> adding addresses of another SPF-aware email service to gmail won't >> help you with sending those messages via gmail: it just cannot >> magically add its SMTP srv addrs to the SPF-related DNS records of >> somebody else's domain, no matter how powerful their web iface is. >> > I am sure, you are right. But from a practical point of view: it > works. I sent emails from TB, they arrived. > you must have already noticed that i'm veeery bad at remembering small details by heart. remember what's important, and you'll 'decompress' the whole story upon need. :)
there was a web robot that checks for the SPF records of a specified domain (somewhere around openspf.org, or following the links from there). hence, you have to check those domains before aliasing them to any relay. even worse, you have to do that PERIODICALLY - in the event that the holders will add SPF support at some point. and a symmetrical amount of shit on the recepients' side. they MAY check the SPF records upon accepting messages, but they also may not. given that SPF is a very good measure against spam, i think it will get even more popular further on. is your approach practical? depends. i personally don't think so, considering those periodical checks involved; i'd rather prepare my infrastructure for standing even a worst-case scenario, and i'm glad i did that already in what concerns SPF. another moral could be this: never add any domain as an alias to any freemail service, unless it's you that owns that domain (and control the appearance of SPF records). how does this map to that whore-wife analogy is left to your imagination. ;) -- Signed, Vitalie. http://vv.labordei.com ________________________________________________________ Current beta is 3.99.07 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
