clo-devel June 2023

clo-devel@common-lisp.net

2 participants
2 discussions

Re: Discourse Requirements
by Mark Evenson 19 Nov '24

19 Nov '24

> On Jun 18, 2022, at 18:11, Chris Moore <moore.christopher515(a)gmail.com> wrote: > > Hey Mark! > > If it makes it easier for the foundation, I can get the host together myself (paying for w/e architecture) and get a proof of concept out for the board to review prior to attaching any kind of DNS record. Not necessary for you to get the host yourself. Sorry to have been a little recalcitrant over the last week, but I have just started a new job with <https://status.im> which has been occupying my time. Erik Hülsmann, a CLF board member, rents <https://hetzner.de/> instances for his CRM company which he essentially donates to the CLF at less than costs, so spinning up a host is no problem. We have standardized on Debian over Ubuntu as it makes the licensing situation clearer when we need a “special case”. Is there any reason you couldn’t install Discourse in the manner you wish under Debian? > > This includes me setting up whatever mail server, getting our daily backups together, and adding necessary plugins (GitHub/Gmail OAuth). If necessary, we would federate the `USER(a)common-lisp.net` domain. Currently we are running exim as the main MTA due to legacy concerns with mailman2 databases, but we wish to transition to a toplevel `postfix` that will work with the legacy `exim` for the `mailman2` app. > > I apologize for trying to rush this - I've got a lot of free time currently due to a lull in work going on at my current company. So I and the dev team are currently not doing much. I want to take advantage of the time while I can. Cool. Let’s take advantage of it. > > Let me know and I'll get this out the door ASAP. Can you please provide me with the public half of a contemporary-strength SSH keypair. We’ll set up a host, and communicate root@HOST via ip4/6 under separate cover. yours, Mark P.S. if you wanna find me online, let’s figure out a Discord rendezvous. I’m <discord:347061732705042435> aka <discord:easye#8466>. -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

2 1

Deliverability via admin@common-lisp.net and request for a new GitLab group
by Vladimir Sedach 21 Jun '23

21 Jun '23

Hello, I tried sending a request for a new GitLab group for CLiki2 to admin(a)common-lisp.net on May 31, and again on June 4. I have not received a reply to either message. I did get DMARC reports from several mail hosts, except philipp(a)marek.priv.at, for whom the following delivery failure message was returned: Mail Delivery System <Mailer-Daemon(a)common-lisp.net> writes: > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > philipp(a)marek.priv.at > (generated from pmarek(a)common-lisp.net) > host nc.hitco.at [2a03:4000:6:71ec::cafe] > SMTP error from remote mail server after RCPT TO:<philipp(a)marek.priv.at>: > 550 5.7.23 <philipp(a)marek.priv.at>: Recipient address rejected: > Message rejected due to: SPF fail - not authorized. Please see http://www.openspf.net/Why?s=mfrom;id=vas@oneofus.la;ip=2a01:4f8:160:83c4::…<UNKNOWN> I believe this is due to a configuration error on Philipp's SMTP server, and have corresponded with him about this separately. The DMARC policy for my mail domain has a "none" policy, so SPF failures should not be rejected. I set up DKIM, SPF, and DMARC on this domain in 2015, have a 10/10 deliverability score from https://www.mail-tester.com/ and have not had any problems with mailing lists. So, 2 things: 1. Can everyone who is being forwarded mail from admin(a)common-lisp.net please check their spam folders for any messages sent via admin(a)common-lisp.net to them since May 30th? 2. Can someone please make a new GitLab group for CLiki2 with my account (vsedach) as an owner? If no one finds emails from me sent to admin(a)common-lisp.net in their Spam folders, there might be a configuration issue with how those mails are forwarded. I receive mail forwarded via vsedach(a)common-lisp.net, so it might be something involving forwarding to multiple people. Thank you. -- Vladimir Sedach

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel June 2023