Hello,
Why am I seeing a hostname as the reply for an ADSP lookup?
~$ dig TXT _adsp._domainkey.live.com
rds.live.com.nsatc.net.
Shouldn't I be seeing something like this:
~$ dig TXT _adsp._domainkey.domainmail.org
"dkim=unknown"
-Jim P.
___
mailop
> On May 2, 2016, at 7:27 AM, Jim Popovitch wrote:
>
> Hello,
>
> Why am I seeing a hostname as the reply for an ADSP lookup?
>
> ~$ dig TXT _adsp._domainkey.live.com
> rds.live.com.nsatc.net.
Wildcard CNAME at the root of live.com, I expect.
;; ANSWER SECTION:
father.christmas.live.com. 360
On Mon, May 2, 2016 at 12:19 PM, Steve Atkins wrote:
>
>> On May 2, 2016, at 7:27 AM, Jim Popovitch wrote:
>>
>> Hello,
>>
>> Why am I seeing a hostname as the reply for an ADSP lookup?
>>
>> ~$ dig TXT _adsp._domainkey.live.com
>> rds.live.com.nsatc.net.
>
> Wildcard CNAME at the root of live.co
Hi Jim,
At 07:27 02-05-2016, Jim Popovitch wrote:
Why am I seeing a hostname as the reply for an ADSP lookup?
~$ dig TXT _adsp._domainkey.live.com
rds.live.com.nsatc.net.
;; ANSWER SECTION:
_adsp._domainkey.live.com. 3600 IN CNAME rds.live.com.nsatc.net.
;; QUESTION SECTION:
;test.live.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 2016-04-28 at 21:56 +, Michael Wise wrote:
> So is the FORMERR ... just the resolver noting that EDNS is not
> supported?
Yes.
If so, I'm uncertain of the issue.
> We don't use EDNS here, so that's what the "our" servers should be
> d
I'm just wondering if there was some bleed between the ML copies of the message
and the personal traffic copies of the message.
For it to be blocked as spam, the system must have seen many copies... I guess
enough people are sending out DCC hashes that enough of them added up and the
direct em
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> For it to be blocked as spam, the system must have seen many copies...
> I guess enough people are sending out DCC hashes that enough of them
> added up and the direct email was blocked?
Apparently so; unless some recipient is marking the list as
