9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] listserv
Date: Sun, 13 Mar 2022 19:47:00 +0100	[thread overview]
Message-ID: <CAFSF3XNU93+8Py6SSL1i+968R9da-b+tiVLGN8N2Cts4-AzCJg@mail.gmail.com> (raw)
In-Reply-To: <3FF3FBE743FA96EBA6FEE8A0377D986C@thinktankworkspaces.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 20:01 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 [this message]
2022-03-13 20:49       ` thinktankworkspaces
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=CAFSF3XNU93+8Py6SSL1i+968R9da-b+tiVLGN8N2Cts4-AzCJg@mail.gmail.com \
    --to=23hiro@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).