10 Nov
2022
10 Nov
'22
6:35 p.m.
In a way this is a test; if the message shows up, then the bounce message
(see below) is false so excuse the noise.
I did write to users-owner(a)trinitydesktop.org but got no reply.
Hopefully resolved so pardon the noise.
fjd
--------
Your subscription has been disabled on the users(a)trinitydesktop.org mailing
list because it has received a number of bounces indicating that there
may be a problem delivering messages to moelmoel2714(a)gmail.com. You may
want to check with your mail administrator for more help.
If you have any questions or problems, you can contact the mailing
list owner at
users-owner(a)trinitydesktop.org
10 Nov
10 Nov
8:29 p.m.
On Thursday 10 November 2022 18:35:56 fjd wrote:
In a way this is a test; if the message shows up, then
the bounce message
(see below) is false so excuse the noise.
I did write to users-owner(a)trinitydesktop.org but got no reply.
Hopefully resolved so pardon the noise.
fjd
Message received here, so you would seem to be good to go.
Bill
11 Nov
11 Nov
6:56 a.m.
On Fri, 11 Nov 2022 03:35:56 +0100
fjd <moelmoel2714(a)gmail.com> wrote:
In a way this is a test; if the message shows up, then
the bounce message
(see below) is false so excuse the noise.
The TDE mailing lists have a long history of not "playing nice" with GMail
(the addition of the list footer causes messages to fail a verification step, which
makes GMail have fits). If you can resubscribe from a non-GMail address,
you'll probably get better results.
E. Liddell
8:14 a.m.
On Friday 11 of November 2022 15:56:09 E. Liddell wrote:
On Fri, 11 Nov 2022 03:35:56 +0100
fjd <moelmoel2714(a)gmail.com> wrote:
Hi all,
in connection with the fact that problems with delivery posts to Gmail have
recently increased, we set up on the mail server signing with DKIM. This
is now used if the message is created on the server (for example, for
confirm subscription to ML) or for mails, where the sender's address is
replaced (or example, due to non-useful SPF) - see emails with sender in
form: "<user> via tde-users" <users(a)trinitydesktop.org>rg>.
Now the question arises: Do we want to force the replacing the sender's
address for all cases so that all outgoing posts can be signed using our
DKIM key? What is your opinion?
Cheers
--
Slávek
In a way this is a test; if the message shows up,
then the bounce
message (see below) is false so excuse the noise.
The TDE mailing lists have a long history of not "playing nice" with
GMail (the addition of the list footer causes messages to fail a
verification step, which makes GMail have fits). If you can resubscribe
from a non-GMail address, you'll probably get better results.
E. Liddell
____________________________________________________ 
8:49 a.m.
On Fri November 11 2022 08:14:12 Slávek Banko wrote:
in connection with the fact that problems with
delivery posts to Gmail have
recently increased, we set up on the mail server signing with DKIM. This
is now used if the message is created on the server (for example, for
confirm subscription to ML) or for mails, where the sender's address is
replaced (or example, due to non-useful SPF) - see emails with sender in
form: "<user> via tde-users" <users(a)trinitydesktop.org>rg>.
Now the question arises: Do we want to force the replacing the sender's
address for all cases so that all outgoing posts can be signed using our
DKIM key? What is your opinion?
I had this problem with GMail (and Yahoo and others) on some lists I run.
I found SPF+DMARC was sufficient to get list posts to GMail. SPF+DMARC
fixed all problems except one - Yahoo users couldn't see posts from other
Yahoo users. However IIRC there were only two Yahoo users and they both
switched to GMail.
I believe it is sufficient that SPF matches on the SENDER domain and
doesn't need to match the FROM domain. For example this post will
probably end up with something like the following headers:
Return-Path: <users-bounces(a)trinitydesktop.org>
From: Mike Bird <mgb-trinity(a)yosemite.net>
We were testing DKIM but it was complicated with mailing lists so when
SPF+DMARC 99% solved the problem we decided not to deploy DKIM (yet).
I would suggest that you announce SPF and DMARC for trinitydesktop.org.
You can copy/adapt our TXT records as a starting point if you wish.
You might also want to do a Google Site Verification. I no longer
remember the details but I believe it was useful when we were working
on our own mailing list problems:
https://support.google.com/webmasters/answer/9008080?hl=en
One other thing we tried was setting up a new mail server with no bad
history. That did not work. It is much harder to get the big players
to accept mail from a new server than it used to be.
--Mike
551
days inactive
551
days old
4 comments
5 participants
participants (5)
-
E. Liddell -
fjd -
Mike Bird -
Slávek Banko -
William Morder