Re: [mailop] Mailop cert - was Re: Admin: Gmail users of mailop suspended due to bounces.

[Phil Pennock via mailop]

On 2019-04-29 at 19:51 +0100, Andrew C Aitchison via mailop wrote:
> I'm trying to alert the exim developers to the suggestions that people
> have made in this thread; but it would be easier to ask them to subscribe to
> mailop if the archive didn't have an expired certificate.

I'm on mailop, I just started a new job recently and fell behind on
public mailing-lists.

Every mail sent out by the mailing-list contains this added footer:
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

At this point, complaining about over-signing is just so much hot air
and underinformed smug superiority (at a level which almost just drove
me to unsubscribe from mailop because this much crap just ... isn't
worth it).

Seriously, the body has been modified, the signature will fail, no
matter what.  Game over.

Exim switched to over-signing a few releases back.  We're now tracking
if we should change the default list of signed headers as a result of
this.  But nothing in Exim's defaults would have changed a single thing
in what happened here.

Independent of DMARC/ADSP/whatever, if you're sending out email in 2019,
you need to be claiming responsibility for it.  DKIM sign.  Perhaps SPF,
perhaps not.

Google's stance on IPv6 and email might be frustrating to encounter, but
really it's the least bad approach they could have taken given that the
IPv4 constraints around reputation tracking disappear.

I've posted over in:
  
with the configuration we have on the @exim.org hub, to have Mailman and
Exim playing together to implement ARC signing and such like.  Whether
or not one specific recipient domain (or hoster) chooses to trust a
given sender for ARC is independent of whether or not it helps others,
and if you're running an MLM in 2019, it's time to try setting up ARC.

-Phil, perhaps a little on the cranky side, but seriously, this thread
   is so much bullshit.

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Mailop cert - was Re: Admin: Gmail users of mailop suspended due to bounces.

[Brielle Bruns via mailop]

On 4/29/2019 12:51 PM, Andrew C Aitchison via mailop wrote:


I'm trying to alert the exim developers to the suggestions that people
have made in this thread; but it would be easier to ask them to 
subscribe to

mailop if the archive didn't have an expired certificate.



I joined the exim-dev list and shared with them my setup, version, etc. 
Hopefully I can get them what they need to figure things out.



--
Brielle Bruns
The Summit Open Source Development Group
http://www.sosdg.org/ http://www.ahbl.org

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

[mailop] Mailop cert - was Re: Admin: Gmail users of mailop suspended due to bounces.

[Andrew C Aitchison via mailop]

On Mon, 29 Apr 2019, Jim Popovitch via mailop wrote:

On April 29, 2019 3:46:03 AM UTC, John Levine via mailop  
wrote:

Still waiting to hear when mailop.org adds its SPF record.


Didn't it take almost 2 years the last time we waited on mailop.org to fix a 
cert?


The current web cert for the mailop archive on chilli.nosignal.org expired in 
July 2018.

I'm trying to alert the exim developers to the suggestions that people
have made in this thread; but it would be easier to ask them to subscribe to
mailop if the archive didn't have an expired certificate.

Is there any chance that the certificate could be renewed ?

Thanks,

--
Andrew C. Aitchison Cambridge, UK
and...@aitchison.me.uk___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop