From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 20328 invoked from network); 4 May 2023 03:38:51 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 4 May 2023 03:38:51 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 1A9FE424BE; Thu, 4 May 2023 13:38:45 +1000 (AEST) Received: from anduin.eldar.org (anduin.eldar.org [IPv6:2001:470:c620:0:280:c8ff:fef8:70bc]) by minnie.tuhs.org (Postfix) with ESMTPS id 70FC7424BD; Thu, 4 May 2023 13:38:33 +1000 (AEST) Received: from anduin.eldar.org (IDENT:brad@localhost [127.0.0.1]) by anduin.eldar.org (8.16.1/8.13.8) with ESMTPS id 3443cV0b017314 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 3 May 2023 23:38:31 -0400 (EDT) Received: (from brad@localhost) by anduin.eldar.org (8.16.1/8.13.8/Submit) id 3443cV5Z008552; Wed, 3 May 2023 23:38:31 -0400 (EDT) From: Brad Spencer To: Warren Toomey In-Reply-To: (message from Warren Toomey via TUHS on Thu, 4 May 2023 09:46:51 +1000) Date: Wed, 03 May 2023 23:38:30 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (anduin.eldar.org [0.0.0.0]); Wed, 03 May 2023 23:38:31 -0400 (EDT) Message-ID-Hash: R2ZU35NXLR7FAG5BSOLLQI5S2QUAUXHF X-Message-ID-Hash: R2ZU35NXLR7FAG5BSOLLQI5S2QUAUXHF X-MailFrom: brad@anduin.eldar.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: tuhs@tuhs.org X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: OT: TUHS mails not going to Outlook & Hotmail. Help! List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Warren Toomey via TUHS 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