Really I can't see as it would hurt in either SPF/SPF or SPF/TXT To me it looks to just be a referring URL for those that get a reject based on the SPF rule. Kinda like a comment judging by < & >.
I've not seen it in the wild this far besides this case. Not even in the google for business app references. Personally I would just drop the http URL and angles. Thus far I've only really had to use ip4 and 'a' and 'redirect' with no complaints. -- Jason Hellenthal Inbox: jhellent...@dataix.net Voice: +1 (616) 953-0176 JJH48-ARIN On Jun 18, 2013, at 1:56, Julie Xu <j...@uws.edu.au> wrote: > Hi > > I be asked to add: > include:otheremailsrv.otherdomain<http://otheremailsrv.otherdomain> > so the TXT records will be looked like: > TXT "v=spf1 mx > include:otheremailsrv.otherdomain<http://otheremailsrv.otherdomain> ~all" > > Question, from my limited research, I have not found any example to put http > part into TXT records, and a little bit worried. > > Could any one advice me if I can put http in spf record like above? > > If so, is my statement right? > > Any comments will be appreciated > > Thanks in advance > > julie > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
