Hi Ivan,

On May 3, 2023 2:39:58 AM GMT+02:00, Ivan <ivan@niktivan.org> wrote:
>Hello,
>
>I am trying to figure out how to add the `www` second-level domain to my
>sourcehut pages custom domain website.
>
>I am using the command `tar -cvz index.html > site.tar.gz` to package the
>tar and `hut pages publish -d niktivan.org site.tar.gz` to publish it.
>
>The site works fine at niktivan.org.
>
>I have further added the following CNAME record to my registrar's DNS config

>[ Another reason I'm interested is that I'm playing with sr.ht to see
>  a bit how it would work for Emacs development, and currently we send
>  such email notifications to a public mailing list and we'd like to
>  keep that functionality.  ]
>
For the Emacs case, if you host your own sr.ht instance you could add any git hooks you want to your service. It's not as convenient as getting the hosted service publicly.

>> FWIW builds.sr.ht support emailing result, but it'd cost
>> spawning up a VM every push if you have no other use for CI:
>> https://man.sr.ht/builds.sr.ht/triggers.md
>
>Hmm... that's a possibility, but it does sound both overkill and

On April 2, 2022 5:45:24 AM GMT+02:00, Beau Trepp <beautrepp@gmail.com> wrote:
>Just wondering if there is anyone who has built anything similar to the
>'automatic merge' when approved and passed CI like some other services
>have. I figure the analogue here would be something watching the mailing
>list for 'approved' email signed by a valid GPG key, then the bot would
>merge it back to main.
>
Yes. There are similar things out there. I couldn't find a blogpost describing the setup I read about, but kernel maintainers, e.g. Greg Kroah-Hartman, do similar things (and have done so for a long time).

They typically subscribe to the mailing list as usual and get a set of scripts with procmail or something like that that process the messages. They can apply patches, run tests, autorespond... It's up to the script what to do with that.

I have not checked, but sourcehut may already be doing part of this for patch CI. You could check and copy/extend it for merges as well.

Migadu here also identifies you as spam:

X-Migadu-Spam-Score: 6.00
X-Spam: Yes
Authentication-Results: aspmx1.migadu.com;	dkim=pass header.d=lists.sr.ht header.s=srht header.b=cUPC2BOb;	dkim=fail ("headers rsa verify failed") header.d=coderkalyan.com header.s=default header.b=e51XeYqY;	dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=coderkalyan.com (policy=quarantine);	spf=pass (aspmx1.migadu.com: domain of lists@sr.ht designates 173.195.146.151 as permitted sender) smtp.mailfrom=lists@sr.ht

It would seem both the SPF and DKIM checks fail. In my short experience years ago, if one of them succeeds then you are not considered spam immediately. I'd try to check on those failures. It may be some slight misconfiguration.

Regards,
Miguel