jcoffey-dev
db4135e481
Brings in the stripped v0.16.25 snapshot (72f8ddd), a bug-fix release:
DKIM rotation (keys retired before their successor is published, keys
made under manual DNS never rotating, manual DNS activating an
unpublished key), IMAP answering failed logins with an untagged NO,
DNSBL scoring only the first return code and caching "not listed" for
24 hours, Pyzor digesting empty input, queue quotas with an empty match
never enforced, RocksDB's info log growing without limit, MaskedEmail
creation with several domains, and Autodiscover answering other schemas
with the Outlook settings.
Conflicts:
- crates/main/Cargo.toml: inbuxa's name and AGPL-only license, version
0.16.25.
- SECURITY.md and .github/PULL_REQUEST_TEMPLATE.md: inbuxa's own.
- Cargo.lock: upstream's, re-resolved against inbuxa's manifests.
- crates/common/src/network/autoconfig/autodiscover.rs: upstream now
parses the request into a struct, so the legacy-protocol switch
(LP-7) reads the address from request.email; ActiveSync and other
schemas get upstream's error 601 untouched.
- resources/schema: unchanged upstream apart from two labels the rename
pass now covers, which main already had.
AGENTS.md, new upstream, is left out: it is about contributing to
upstream, which doesn't apply to this repository.
48 lines
2.3 KiB
YAML
48 lines
2.3 KiB
YAML
name: Redirect new discussions to the support portal
|
|
|
|
on:
|
|
discussion:
|
|
types: [created]
|
|
|
|
permissions:
|
|
discussions: write
|
|
|
|
jobs:
|
|
redirect:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Post support portal redirect
|
|
uses: actions/github-script@v9
|
|
with:
|
|
script: |
|
|
const discussion = context.payload.discussion;
|
|
const author = (discussion.user && discussion.user.login) || '';
|
|
|
|
const body = [
|
|
`Hi @${author}, thanks for posting!`,
|
|
``,
|
|
`Stalwart support has moved to **[support.stalw.art](https://support.stalw.art)**. The support portal is now the canonical place to ask questions, request help, and report issues for triage. Other community members may still reply here, but the maintainers no longer answer support questions through GitHub Discussions, so your question may go unanswered unless you also post it on the portal.`,
|
|
``,
|
|
`You can sign in to support.stalw.art with your existing GitHub account, so no separate registration is required. Google, Discord, LinkedIn, and email/password sign-in are also available.`,
|
|
``,
|
|
`**Why we are unifying our support channels**`,
|
|
``,
|
|
`Until now, Stalwart support has been spread across GitHub Discussions, Discord, Matrix, and Reddit. As the project has grown, tracking parallel inboxes and deduplicating threads has become unsustainable; the result has been slower answers, repeated work for the people helping out, and good information buried in chat scrollback where the next person with the same question would never find it.`,
|
|
``,
|
|
`[support.stalw.art](https://support.stalw.art) is a Discourse instance that we operate ourselves, hosted at Hetzner in Germany and GDPR-compliant.`,
|
|
``,
|
|
`Thank you for helping us keep the conversation in one place.`,
|
|
].join('\n');
|
|
|
|
await github.graphql(
|
|
`mutation($discussionId: ID!, $body: String!) {
|
|
addDiscussionComment(input: { discussionId: $discussionId, body: $body }) {
|
|
comment { id }
|
|
}
|
|
}`,
|
|
{
|
|
discussionId: discussion.node_id,
|
|
body,
|
|
}
|
|
);
|