public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Subject: Re: ezmlm warning
Date: Wed, 23 Apr 2014 17:04:00 -0000	[thread overview]
Message-ID: <CE435457-7B59-499E-B701-9DF58E823F48@comcast.net> (raw)
In-Reply-To: <20140423154314.GB26579@elastic.org>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

On Apr 23, 2014, at 8:43 AM, Frank Ch. Eigler <fche@elastic.org> wrote:
>> I’ve checked lots of my old email for dkim=fail, and I see all
>> bugzilla email fails dkim.  The latest failure was on March 31,
>> 2014.
> 
> It'd be handy if you could find a couple of raw message URLs in the
> archives for analysis.

Here are the raw bits for the last one I saw.  I think you can reproduce it on demand by cc: yourself on a bug report, and then just modify it.  It will then send out email to you.

The advantage of doing that is you can then get logging from the various tools and see in depth what was going on.

I’ll discount the issue I saw as a foible on comcast’s part.

Thanks.


[-- Attachment #2: 59305.eml.bin --]
[-- Type: application/macbinary, Size: 5271 bytes --]

  reply	other threads:[~2014-04-23 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1398055301.29540.ezmlm-warn@gcc.gnu.org>
2014-04-23 11:07 ` Fwd: " Mike Stump
2014-04-23 15:44   ` Frank Ch. Eigler
2014-04-23 17:04     ` Mike Stump [this message]
     [not found] <1412716173.8985.ezmlm-warn@gcc.gnu.org>
2014-10-08 17:23 ` Rafael Espíndola
2014-10-09  0:51   ` Ian Lance Taylor
2014-10-09  5:19     ` Rafael Avila de Espindola
2014-10-09  5:26       ` Chandler Carruth
2014-10-09 11:54         ` Joseph S. Myers
2013-04-01  4:45 overseers-help
     [not found] <1134362992.10249.ezmlm-warn@gcc.gnu.org>
2005-12-14  0:44 ` Fwd: " Mike Stump
2005-12-14  2:28   ` Ian Lance Taylor
2006-01-30 18:30     ` Mike Stump
  -- strict thread matches above, loose matches on Subject: below --
2003-07-29 17:05 overseers-help

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=CE435457-7B59-499E-B701-9DF58E823F48@comcast.net \
    --to=mikestump@comcast.net \
    --cc=fche@elastic.org \
    --cc=overseers@gcc.gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).