The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] ping
Date: Wed, 20 Sep 2017 10:36:47 -0600	[thread overview]
Message-ID: <bbcdd4aa-73f1-1bdc-03ea-18fd4b7b2be4@tnetconsulting.net> (raw)
In-Reply-To: <20170914235542.GA7894@minnie.tuhs.org>

On 09/14/2017 05:55 PM, Warren Toomey wrote:
> I've had a few e-mails about this. It seems to be Gmail related. I
> haven't tracked the issue down yet. I'll keep looking.

Friendly ping.  I received 16 DMARC feedback reports yesterday that were 
directly related to the TUHS mailing list.

Warren, I've sent you an email with more details off list.



-- 
Grant. . . .
unix || die

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3717 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170920/960a3791/attachment.bin>


      reply	other threads:[~2017-09-20 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 23:00 ron minnich
2017-09-14 23:09 ` Grant Taylor
2017-09-14 23:55 ` Warren Toomey
2017-09-20 16:36   ` Grant Taylor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bbcdd4aa-73f1-1bdc-03ea-18fd4b7b2be4@tnetconsulting.net \
    --to=gtaylor@tnetconsulting.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).