Re: Twitter issue

From: S Moonesamy <sm+mu_at_elandsys.com>
Date: Fri, 21 Oct 2016 10:40:05 -0700


Hi Ish,
At 10:12 21-10-2016, Ish Sookun wrote:
>Then after a couple of minutes:
>
>; <<>> DiG 9.10.4 <<>> <http://twitter.com>twitter.com
>;; global options: +cmd
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4648
>;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
>
>;; OPT PSEUDOSECTION:
>; EDNS: version: 0, flags:; udp: 512
>;; QUESTION SECTION:
>;<http://twitter.com>twitter.com. IN
>
>;; ANSWER SECTION:
><http://twitter.com>twitter.com. 1592 IN 104.244.42.129
><http://twitter.com>twitter.com. 1592 IN 104.244.42.193
>
>;; Query time: 104 msec
>;; SERVER: 8.8.8.8#53(8.8.8.8)
>;; WHEN: Fri Oct 21 21:04:29 MUT 2016
>;; MSG SIZE rcvd: 72

I am getting the following:

  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58907
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;twitter.com. IN A

  ;; ANSWER SECTION:
  twitter.com. 1437 IN A 104.244.42.193
  twitter.com. 1437 IN A 104.244.42.129

  ;; AUTHORITY SECTION:
  twitter.com. 80159 IN NS ns2.p34.dynect.net.
  twitter.com. 80159 IN NS ns4.p34.dynect.net.
  twitter.com. 80159 IN NS ns1.p34.dynect.net.
  twitter.com. 80159 IN NS ns3.p34.dynect.net.

The following was from 8.8.8.8 at 21:28:

  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 35602
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;twitter.com. IN A

  ;; Query time: 41 msec
  ;; SERVER: 8.8.8.8#53(8.8.8.8)
  ;; WHEN: Fri Oct 21 10:28:35 2016
  ;; MSG SIZE rcvd: 29

>That would also explain why notifications from
>Twitter are landing in my spam folder.
>
>Received-SPF: temperror
>(<http://google.com>google.com: error in
>processing during lookup of
>b0095f27827ish=<mailto:hacklog.mu_at_bounce.twitter.com>hacklog.mu_at_bounce.twitter.com:
>DNS error) client-ip=199.16.156.177;
>Authentication-Results: <http://mx.google.com>mx.google.com;
> dkim=temperror (dns failure for
> signature) header.i=_at_<http://twitter.com>twitter.com;
> spf=temperror
> (<http://google.com>google.com: error in
> processing during lookup of
> b0095f27827ish=<mailto:hacklog.mu_at_bounce.twitter.com>hacklog.mu_at_bounce.twitter.com:
> DNS error)
> smtp.mailfrom=b0095f27827ish=<mailto:hacklog.mu_at_bounce.twitter.com>hacklog.mu_at_bounce.twitter.com

A DNS error should cause a (SPF) temporary
error. I vaguely recall that Google explained
why it treats the message as "spam".

Regards,
S. Moonesamy
Received on Fri Oct 21 2016 - 17:41:14 PST

This archive was generated by hypermail 2.3.0 : Fri Oct 21 2016 - 17:45:01 PST