9front - general discussion about 9front
 help / color / mirror / Atom feed
From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: Re: [9front] listserv
Date: Sun, 13 Mar 2022 13:49:53 -0700	[thread overview]
Message-ID: <B5363A86CD0B0856538E8C8C4D828A8E@gmail.com> (raw)
In-Reply-To: <CAFSF3XNU93+8Py6SSL1i+968R9da-b+tiVLGN8N2Cts4-AzCJg@mail.gmail.com>

Great question. My mail kept getting bounced by gmail. Yahoo mail was fine but gmail was a pain 

For gmail to accept mail I needed a "_dmarc" for the root of the domain and the host "_dmarc.maat.thinktankworkspaces.com".

Here is the configuration:

@ 10800 IN SOA ns1.gandi.net. hostmaster.gandi.net. 1646461443 10800 3600 604800 10800
@ 10800 IN A 45.79.94.76
@ 10800 IN MX 10 maat.thinktankworkspaces.com.
@ 10800 IN MX 10 mail.thinktankworkspaces.com.
@ 10800 IN MX 10 thinktankworkspaces.com.
@ 10800 IN TXT "v=spf1 a mx ip4:45.79.94.76 -all"
_20948fec0056d2c1f86019ec5d2b200d 10800 IN CNAME 8e44ca796bf0f517dce6d208a55cc87f.d01479e663f61af9158941fd03926cee.d7f2ad3f771764a19618.sectigo.com.
_dmarc 10800 IN TXT "v=DMARC1; p=none; fo=1; rua=mailto:glenda@thinktankworkspaces.com; ruf=mailto:glenda@thinktankworkspaces.com"
_dmarc.maat 10800 IN TXT "v=DMARC1; p=none; fo=1; rua=mailto:glenda@thinktankworkspaces.com; ruf=mailto:glenda@thinktankworkspaces.com"
blog 10800 IN CNAME blogs.vip.gandi.net.
maat 10800 IN A 45.79.94.76
maat 10800 IN TXT "v=spf1 a mx ip4:45.79.94.76 -all"
mail 10800 IN A 45.79.94.76
mail 10800 IN TXT "v=spf1 a mx ip4:45.79.94.76 -all"
www 10800 IN A 45.79.94.76

All of this was such a pain that decided to write about my experience: 

http://thinktankworkspaces.com/plan9/email-upas

Again this seems to be working with a lot of other places I send mail to.

I very much welcome comments. 

Plan9 doesn't currently support DKIM. But its helpful to have spf configured and _dmarc even if its not using dkim the _dmarc reveals a lot.

'v=DMARC 1 '
indicates the protocol version.

The suggested DMARC record above includes a monitor policy (p=none). This means that you are not instructing mailbox providers to take any action with your email that fails authentication. 

'fo' lets mailbox providers know you want message samples of emails that failed either SPF and/or DKIM. For the value:
'Use 0' to receive a report if both SPF and DKIM fail. (default)
'Use 1' to receive a report if either SPF or DKIM fail. (recommended)

So its interesting it does pass on mail-tester.com and Gmail somehow resolves it and does a pass on the _dmarc for both hosts. 


Quoth hiro <23hiro@gmail.com>:
> why would you use dmarc? i was not aware it was necessary for
> anything. and in this email i see spf is valid, but dmarc isn't.
> 
> On 3/13/22, william@thinktankworkspaces.com
> <william@thinktankworkspaces.com> wrote:
> > Yes. Every time I send to 9front@9front.org. Please keep in mind i'm using
> > upas as a
> > server. I suspected it was my problem I worked hard to get 9/10 on
> > mail-tester.com and have
> > _dmarc's for host and domain so that google doesn't flag it but as difficult
> > as it was to get working. I still don't fully understand upas.
> >
> >
> > Quoth Stanley Lieber <sl@stanleylieber.com>:
> >> this address is subscribed to the mailing list. are they complaining to
> >> you directly?
> >>
> >> sl
> >>
> >> > On Mar 13, 2022, at 3:37 AM, william@thinktankworkspaces.com wrote:
> >> >
> >> > Why is my mail going to MARIO.BALDINI@LISTSERV.IEEE.ORG and why is it
> >> > getting bounced? Seems to be a forwarding from
> >> > 9front-bounces@4ess.inri.net
> >> >
> >> >
> >> >
> >>
> >>
> >
> >


  reply	other threads:[~2022-03-13 21:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  8:15 william
2022-03-13 15:56 ` Stanley Lieber
2022-03-13 16:25   ` Stanley Lieber
2022-03-13 18:31     ` william
2022-03-13 18:49     ` william
2022-03-13 18:23   ` william
2022-03-13 18:47     ` hiro
2022-03-13 20:49       ` thinktankworkspaces [this message]
2022-03-13 21:09         ` hiro
2022-03-13 21:30         ` Stanley Lieber
2022-03-15  5:01         ` Lyndon Nerenberg (VE7TFX/VE6BBM)

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=B5363A86CD0B0856538E8C8C4D828A8E@gmail.com \
    --to=thinktankworkspaces@gmail.com \
    --cc=9front@9front.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).