Add support for sourcehut emails #4
Description
Hi,
here is an example email I received from sourcehut for page https://todo.sr.ht/~madearl/jiralib3/1#event-429643:
Return-Path: <[email protected]>
[…]
Content-Type: multipart/signed;
boundary=171f0dae01100c3f16bf2d2e4a8b2bec5842dea0a0c1c76cc0b144647322;
micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 17 Sep 2025 18:15:05 +0000
Message-Id: <[email protected]>
Mime-Version: 1.0
Subject: Re: ~madearl/jiralib3#1: Can't get started
References: <~madearl/jiralib3/[email protected]>
In-Reply-To: <~madearl/jiralib3/[email protected]>
Sender: <[email protected]>
Reply-To: "~madearl/jiralib3#1" <~madearl/jiralib3/[email protected]>
From: "~madearl" <[email protected]>
--171f0dae01100c3f16bf2d2e4a8b2bec5842dea0a0c1c76cc0b144647322
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8; format=flowed
I don't think basic works anymore on Jira Cloud. I've update the README to =
suggest 'token as preferred method.
You then need:
jiralib3-url: "https://jira.wolterskluwer.io"=20
jiralib3-auth: 'token
jiralib3-user-login-name "[email protected]" <-- note email addre=
ss, not user name for Jira Cloud
jiralib3-token "the-token-you-created"
One more thing to note: If this is not Jira Cloud (which usually is named y=
ourcorp.atlassian.net) you might need to ask the Jira admin to give you per=
missions to access the API.
--=20
View on the web: https://todo.sr.ht/~madearl/jiralib3/1#event-429643
--171f0dae01100c3f16bf2d2e4a8b2bec5842dea0a0c1c76cc0b144647322
Content-Type: application/pgp-signature
-----BEGIN PGP MESSAGE-----
wsCpBAEBCABdBYJoyvqpCRBllwTRo4qTrjUUAAAAAAAcABBzYWx0QG5vdGF0aW9u
cy5vcGVucGdwanMub3JnoqdAMyC673j4eL5QgCnn8xYhBER7aeSzS+kLyCmg6WWX
BNGjipOuAABpmwf/UUPbFnseFLBmwOi6JJfvbXpDTbL/A9kPNAnVICBqmHuV1eug
ZU7wMyqfzar7BEFuUDlLEGoCtXUcQY9MyvVOjp5lLLp8zSCBprFw9FswxabOIkDj
tJyzxKoErqEkmTtf0f8cZnsICOMyE0xnT4lfrFhHYo4v8BKxy1NeXU1/aKmY8XvN
x3GRweRnvO2VbmYbgdNj99A6jE5tXmRPSfIEYxqPmUybeYkDUcvbgP/HUQltHOHD
/BmOLXiFU2l7y7ZZaIYEnc4aJYadJdQ0cdFbr6hNS9507EdYCA5Ty2I5Hcp0LByT
UwI8pjx7Md0opo+l6ubxmF+4DE45NP3LZYcFbA==
=E4Xh
-----END PGP MESSAGE-----
--171f0dae01100c3f16bf2d2e4a8b2bec5842dea0a0c1c76cc0b144647322--
The URL I would like to get in the "Actions" is right after "View on the web:". Please note there is no "text/html" part in this email, this is just plain text.
I think the current design of microdata is a bit hard to extend for new kinds of emails. I would suggest creating a variable containing a list functions to execute in order (one for github, one for discord, one for sourcehut, ...): the first function which returns non nil wins. This way, adding support for sourcehut is just a matter of adding a function.