In some cases no RFC822 header will contain the correct alias address.
One such example is a mailing list where the recipient address is only
an alias to the configured "from" address.
For instance Postfix offers the "X-Original-To" header [1].

[1]: https://www.postfix.org/postconf.5.html

Signed-off-by: Thorben Günther <admin@xenrox.net>
---
Supersedes: https://lists.sr.ht/~rjarry/aerc-devel/patches/58533

 commands/msg/invite.go  |  5 ++++-
 commands/msg/reply.go   | 25 ++++++++++++++++++++-----
 config/accounts.go      |  1 +
[message trimmed]

Wouldn't it be nicer - and more graph-like - to add a query for a single site
instead of this very specialized query?
Something like either
	site(id: Int!)
or
	site(domain: String!, protocol: Protocol)

This would make handling ACLs listing as straightforward as your implementation
and have the further benefit that it would be easier for users to retrieve other
fields for a single site.

On Thu Apr 3, 2025 at 3:00 PM CEST, Robin Jarry wrote:

> Out of curiosity, is this described in a standard or RFC anywhere?

I don't think it is part of a standard. It seems to originate from postfix,
for example see the documentation [1].

> X-* headers are often application specific and should not be relied upon
> by MUAs nor MTAs.
>
> I don't mind adding this special case. But it may be worth making this
> user-configurable, e.g.:
>
> 	[account]

In some cases no header besides "X-Original-To" will contain the correct
alias address. One such example is a mailing list where the recipient
address is only an alias to the configured "from" address.

Signed-off-by: Thorben Günther <admin@xenrox.net>
---
 commands/msg/envelope.go |  1 +
 commands/msg/reply.go    |  1 +
 lib/rfc822/message.go    | 21 +++++++++++----------
 models/models.go         | 21 +++++++++++----------
 4 files changed, 24 insertions(+), 20 deletions(-)

diff --git a/commands/msg/envelope.go b/commands/msg/envelope.go
index d064e43c..bfda5c59 100644
[message trimmed]

On Mon Nov 25, 2024 at 3:49 PM CET, Drew DeVault wrote:
> You cannot add new values to an enum type in Postgres, instead you have
> to create a new type and update the type of the column in a four step
> process:

Adding to an enum is supported by Postgres with "ALTER TYPE", only removing values
requires the four step migration. This is already used in some sourcehut migrations
(e.g. the one I did for lists [1]).

[1]: https://git.sr.ht/~sircmpwn/lists.sr.ht/commit/a438d6b68f5eb4b232e748b0d666ae5e7afc2c4c

And route the UI's visibility change through GraphQL
---
v3: Add schema migration

 api/graph/schema.graphqls                     |  4 +++
 api/graph/schema.resolvers.go                 | 31 +++++++++++++++--
 ...bfcbb3_add_job_updated_to_webhook_event.py | 34 +++++++++++++++++++
 buildsrht/blueprints/settings.py              | 12 ++++---
 schema.sql                                    |  3 +-
 5 files changed, 77 insertions(+), 7 deletions(-)
 create mode 100644 buildsrht/alembic/versions/707deabfcbb3_add_job_updated_to_webhook_event.py

diff --git a/api/graph/schema.graphqls b/api/graph/schema.graphqls
index 0e941f7..8cc56b7 100644
[message trimmed]

And route the UI's visibility change through GraphQL
---
 api/graph/schema.graphqls        |  4 ++++
 api/graph/schema.resolvers.go    | 31 +++++++++++++++++++++++++++++--
 buildsrht/blueprints/settings.py | 12 ++++++++----
 3 files changed, 41 insertions(+), 6 deletions(-)

diff --git a/api/graph/schema.graphqls b/api/graph/schema.graphqls
index 0e941f7..8cc56b7 100644
--- a/api/graph/schema.graphqls
+++ b/api/graph/schema.graphqls
@@ -283,6 +283,7 @@ type OAuthClient {
 
 enum WebhookEvent {
[message trimmed]

---
 buildsrht/blueprints/settings.py | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/buildsrht/blueprints/settings.py b/buildsrht/blueprints/settings.py
index 0368a5c..779616f 100644
--- a/buildsrht/blueprints/settings.py
@@ -1,6 +1,6 @@
 from flask import Blueprint, current_app, render_template, request, url_for, abort, redirect
 from flask import current_app
-from srht.database import db
+from srht.graphql import exec_gql
 from srht.oauth import current_user, loginrequired
[message trimmed]

On Thu Nov 21, 2024 at 3:13 PM CET, Drew DeVault wrote:
> LGTM, but if we're adding a JOB_UPDATED GQL webhook, then we have to
> update the web UI's visibility change to be routed through GQL so that
> the webhook is delivered appropriately when updating visibility from the
> web.

Will send a follow-up patch.

---
This feature was requested by hut users.
If you prefer, I can modify this patch to use an input struct instead of just the
visibility.

 api/graph/schema.graphqls     |  4 ++++
 api/graph/schema.resolvers.go | 31 +++++++++++++++++++++++++++++--
 2 files changed, 33 insertions(+), 2 deletions(-)

diff --git a/api/graph/schema.graphqls b/api/graph/schema.graphqls
index 0e941f7..8cc56b7 100644
--- a/api/graph/schema.graphqls
+++ b/api/graph/schema.graphqls
@@ -283,6 +283,7 @@ type OAuthClient {
[message trimmed]