The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Brad Spencer <brad@anduin.eldar.org>
To: Warren Toomey <wkt@tuhs.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: OT: TUHS mails not going to Outlook & Hotmail. Help!
Date: Wed, 03 May 2023 23:38:30 -0400	[thread overview]
Message-ID: <xonfs8cyde1.fsf@anduin.eldar.org> (raw)
In-Reply-To: <ZFLya8Nn6xr3efhI@minnie.tuhs.org> (message from Warren Toomey via TUHS on Thu, 4 May 2023 09:46:51 +1000)

Warren Toomey via TUHS <tuhs@tuhs.org> writes:

> All, e-mails from the TUHS server are not making it to Hotmail or Outlook.
> I've not changed anything. Is there anybody with some MTA/ISP experience
> who might be able to help diagnose the problem?
>
> Thanks, Warren

There is a lot that could be and without more information it will be
next to impossible to determine what the problem or problems may be.

The first question is are you getting bounces, or is the message just
getting black holed??  From the TUHS sending server, can you send an
email from the command line (for example) outside of the list management
software to a known address that could not receive email from the list
itself??  If this direct message (just to give it a name) does not make
it, then it could indicate that the receiver has blocked the TUHS server
(for a ton of possible reasons).  If this direct message does make it,
but email from the list management software does not, then it is likely
that something about how the message is processed (i.e. altered) is
triggering the block.

A few others have mentioned DMARC, but DKIM may be involved.  More or
less, if the original sender uses any of the signed email techniques
that exist and the TUHS server alters any part of the message it will
likely cause the message to fail the signature check.  This may include
altering the Subject and the From if these bits of the header were
covered by the signature.  I am by no means an expert here, but am on a
number of email lists and this problem comes up from time to time and
there has been debate on how or if the list management software should
mess with the message.

Of course, I would also check to make sure that the message actually
made it off of the TUHS server itself.  That is, the message isn't
sitting in the local queue having failed to contact the destination
email server??

Other stranger stuff..  from my logs of incoming TUHS email it looks
like you can send via IPv4 and IPv6...  is it only one of those sending
addresses that fail?? (This may be hard to determine, I realize, but it
may be the case that the receiver can't receive one of the addresses
families correctly, probably IPv6 if there is a problem).  It doesn't
look like you are using TLS as a email client sending back out.  Is it
possible for you to do that??  It might help.  I know that some of the
stuff I use to keep SPAM out gives a greater credibility to clients that
come in via TLS and have a valid certificate where the cert chain
validates completely.  (I won't debate whether or not this is a good
idea or even useful given how simple it is to get Let's Encrypt certs
for free, just mostly mentioning that it happens).



I am not at all an expert on this topic, but have had my own email
domain since 1993 and have seen a whole lot of really strange stuff.





-- 
Brad Spencer - brad@anduin.eldar.org - KC8VKS - http://anduin.eldar.org

  parent reply	other threads:[~2023-05-04  3:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 23:46 [TUHS] " Warren Toomey via TUHS
2023-05-04  0:33 ` [TUHS] " Jim Capp
2023-05-04  1:35   ` Greg 'groggy' Lehey
2023-05-04  8:58     ` [TUHS] OT: Nostr Protocol. (Was: OT: TUHS mails not going to Outlook & Hotmail. Help!) Ralph Corderoy
2023-05-04 10:10       ` [TUHS] Re: OT: Nostr Protocol Angel M Alganza
2023-05-04  0:54 ` [TUHS] Re: OT: TUHS mails not going to Outlook & Hotmail. Help! Gregg Levine
2023-05-04  3:38 ` Brad Spencer [this message]
2023-05-04  4:49   ` Mehdi Sadeghi via TUHS
2023-05-04 18:49   ` Jeremy C. Reed
2023-05-04 20:31     ` Tom Ivar Helbekkmo via TUHS
2023-05-04 20:44       ` Steffen Nurpmeso
2023-05-04 19:39 ` Warren Toomey via TUHS
2023-05-10  0:13 ` Warren Toomey via TUHS

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=xonfs8cyde1.fsf@anduin.eldar.org \
    --to=brad@anduin.eldar.org \
    --cc=tuhs@tuhs.org \
    --cc=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).