The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] TUHS list: back to one list
Date: Fri, 20 Oct 2017 08:40:06 +1000	[thread overview]
Message-ID: <20171019224006.GA11678@minnie.tuhs.org> (raw)

All, behind the scenes we have had Grant Taylor and Tom Ivar Helbekkmo
helping us find a solution to the TUHS list DKIM issues. We have been
running two separate lists (unmangled and mangled TUHS headers) for a
few weeks. It looks like we can now merge them all back together and
use the settings on one to avoid (most of) the DKIM problems.

So that's what I've done: merged back to a single TUHS mailing list.
I've restored the [TUHS] on the Subject line as well.

I'll monitor the logs for further bounces. Fingers crossed there won't
be any further unsubscriptions from the list due to bounce processing.
If there are, I'll manually put you back in.

Cheers all & thanks to Grant and Tom.
	Warren


             reply	other threads:[~2017-10-19 22:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 22:40 Warren Toomey [this message]
2017-10-19 23:45 ` Arthur Krewat
2017-10-20  6:41 ` Dave Horsfall

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=20171019224006.GA11678@minnie.tuhs.org \
    --to=wkt@tuhs.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 NNTP newsgroup(s).