Skip to content

History

Revisions

  • The pages on how the project runs stop describing GitHub as its process. Governance copies GOVERNANCE.md, whose status note says its passages on the GitHub ruleset, repository admin and private vulnerability reporting describe how the project ran there but whose body still says them in the present tense; the copy now puts them in the past tense and says what happens now, from that note and from CONTRIBUTING.md and SECURITY.md at master 540347500: merge requests, no approval rule on GitLab, a gated tree landing on master by fast-forward, reports arriving as confidential GitLab issues that one maintainer receives, and the ownership of the GitLab project as the critical asset where GitHub repository admin stood. It also says plainly that GOVERNANCE.md does not yet record the second maintainer's access on GitLab. Release Process keeps RELEASE.md as it is and adds short notes at steps 9, 11, 12 and 13, where a reader of one step would otherwise miss the status note: the alert pages are GitHub's, build-inputs-1 is unreachable, the draft, packaging, SBOM, signing, smoke test and package managers cannot run until the chain moves, which is planned roadmap work, and a gated tree lands by fast-forward with no pull request. Its own publishing section now says the releases are on GitLab with the same files, that no later release can carry the GitHub signing identity, and that the installer has been Authenticode-signed since 6.3.1, where it said it was not. The Project Handbook, a record of 4 September, says in sections 7 to 12 what has changed - the merge-request route, checks by hand, no CI, the release chain stopped, CVE IDs through GitLab and the Security template - and puts the GitHub checks it records in the past tense. The home page's pointer to Contributing speaks of a merge request.

    Christopher Holloway committed Sep 24, 2026
    fc0cb9b
  • What hMailServer Is and Is Not's table of what is off by default gains the row it lacked: what the tree after 6.3.3 changes without a switch - the two-minute outbound back-off and uncounted self-chosen deferrals, settings that apply when saved, and compromised-account detection's watch mode, which only reports.

    Christopher Holloway committed Sep 24, 2026
    eabf7f1
  • Connecting a Mail Client said an account single sign-on or SCIM made could get a password through its recovery address; setting a recovery address asks for the account's own password as well, which such an account has never been told, so an administrator setting one is the only way, and the page says so.

    Christopher Holloway committed Sep 24, 2026
    3d8975c
  • Your First Domain and Mailbox's signature note put the webmail's 64 KB limit on the domain's signature, which it does not govern; the limit is named as the person's own signature's, and the inline-image rewrite as applying to both.

    Christopher Holloway committed Sep 24, 2026
    4369e0e
  • Two notes the first pass left out. Installing hMailServer says that the server's own update verification pins the same GitHub workflow identity the cosign line checks, so a release signed anywhere else is refused unless UpdateSigningIdentity, UpdateSigningIssuer and UpdateSourceRepository are changed, and that the default feed answers 404 since 18 September. Your First Domain and Mailbox says a formatted signature can carry a logo in the tree after 6.3.3.

    Christopher Holloway committed Sep 24, 2026
    5e3e2fc
  • Upgrading hMailServer's schema table linked Changes Since 6.2.10 with an escaped pipe inside a table cell, which GitLab may split at; it links [[Changes-Since-6210]] plainly, as the landing page's tables now do.

    Christopher Holloway committed Sep 24, 2026
    4f6b00b
  • The sidebar lists the eight new pages where a reader looks for them: Profiles and Environment and The Control Deck beside the container page and the Control Panel, The Webmail beside Connecting a Mail Client and Migration after DNS in Install and run; Encryption for People after Encryption and Certificates and Sign-in and Identity after Security Hardening in Secure it; Mailing Lists and Outbound Shaping beside Aliases, Lists and Public Folders and Routes and Relays in Extend it. Nothing else in the sidebar is changed.

    Christopher Holloway committed Sep 24, 2026
    b2e4243
  • Eight new pages for the ground the wiki had no page for, each written for the wiki's reader from its repository documents at master 540347500 - what it is, how to turn it on, what it does not do - with a link to the full document, and each saying which parts are in 6.3.3 and which are in the tree after it and not yet released. The Webmail: turning it on, what 6.3.3 has, and what the tree adds - Important and inbox sections, subscriptions, brand logos, recover deleted, offline days, a second account, emoji and tables, send-as and masked addresses, other accounts, expiring messages, recall, calendars, sharing and invitations, shared address books, the directory, the Security page - and the administrator's bounds. The Control Deck: signing in, the fifteen views of 6.3.3 and the thirty-eight of the tree, the parity census (456 of 464), the first-hour checklist and who may use it. Sign-in and Identity: what 6.3.3 has, passkeys, OpenID Connect and SAML side by side, SCIM, account recovery, devices and the session policies, administrator roles. Encryption for People: S/MIME in the page, a domain's S/MIME authority, OpenPGP and the Web Key Directory, password-protected messages, zero-access mailboxes, gateway encryption and sealed mail, and that a message that expires is not encryption. Mailing Lists: the membership query and the list manager - joining and leaving, the copies, one-click unsubscribe, digest, archive, bounces, and no From rewriting. Outbound Shaping: the back-off that is on by default, the connection and tenant ceilings, uncounted deferrals, IP warm-up, and bounces, complaints and the reputation watch. Profiles and Environment: apply-on-save, the three setting levels, every setting from the environment, and the four profiles. Migration: which route for which move, the webmail's Other accounts with Gmail and Outlook.com sign-in, and the migration jobs.

    Christopher Holloway committed Sep 24, 2026
    e719793
  • The three pages on extending the server's mail handling are brought up to master 540347500, every addition labelled as in the tree after 6.3.3 and not yet released. Rules and Sieve gains the mail flow rules: a domain's own rules beside the server's and an account's, the attachment-name condition and the outbound content policy's four (sensitive content, attachment type by its bytes, external recipients, readable text), and the five transport actions - add a disclaimer, reject with a text at the end of DATA, require TLS, quarantine, warn the sender. Aliases, Lists and Public Folders gains the alias a mailbox move leaves, masked addresses and verified send-as, lists that define themselves by a membership query, the list manager (one copy per member with RFC 8058 one-click over https, its own bounce handling, no From rewriting), and the sharing beside public folders. Routes and Relays gains gateway encryption on a remote domain policy, the outbound back-off - on by default at two minutes, with a relay counted as one destination - the connection and tenant ceilings and IP warm-up, restricted delivery, journaling and dual delivery, the send API and the two-family bind address.

    Christopher Holloway committed Sep 24, 2026
    767a600
  • The four pages on operating the server are brought up to master 540347500. Monitoring and Health counts 38 metric families and lists the six added since 6.3.3 (country blocking, complaints, spam traps), has eleven alert conditions where it had six - the create scripts seed eleven, one more than the audit counted - gives the audit trail its put-back route and the auditor role's access, says which of the trail's recorded gaps are closed and which remain, corrects the reports (spam, virus and storage are per domain since schema 6062), and adds following one connection live and the new places mail can wait: held for review, held for the sandbox, a shaping back-off, a warm-up ceiling, a drain. Backup and Restore says the account stores are 57 tables, 21 carried and 36 declared exceptions with passkeys and shares among the ones left out, adds the encrypted archive and restoring one mailbox or one message, and says how a zero-access mailbox and a domain's S/MIME authority travel. Troubleshooting explains the update check's 'The update feed answered HTTP 404.' on every release since 6.2.28, the applies marks and a setting the environment manages, and where a message waits in the tree. Upgrading hMailServer has the schema at 6096 and fifty-six steps after 6.3.3 (none touches hm_messages; 6072 scales with the greylisting table), the drain, [Database] UpgradeOnStart and the reported roll-back, and says the update settings apply when saved.

    Christopher Holloway committed Sep 24, 2026
    688511e
  • The five pages on securing the server are brought up to master 540347500, every addition labelled as in the tree after 6.3.3 and not yet released. DNS for Your Domain adds the DKIM rotation policy (it never edits DNS, it says what to publish and waits), the report mailbox through which the server reads the DMARC and TLS-RPT reports a domain receives, the openpgpkey host the Web Key Directory needs, and that BIMI is read for display and not published. Encryption and Certificates says it is about transport, points to the new Encryption for People page, notes which of its keys wait for a reinitialise now that a save applies, and gains section 9.6b on gateway encryption to a partner's OpenPGP key or certificate (the Subject is not hidden; refuse is the default fallback). Stopping Spam gains the hardened greylisting and its bypass list, the SMTP policy switches and the domain white and black list, the three-level allow and block lists with URL entries and the quarantine digest, the refusals each adds, and a section on impersonation protection, spam traps, country blocking and complaints. Stopping Viruses gains the sandbox, what the scanner and the attachment list do with a message sealed end to end, and the attachment conditions of the mail flow rules. Security Hardening gains passkeys, single sign-on, SCIM, account recovery, the breach check, devices and sessions, administrator roles, compromised-account detection, country blocking, verified send-as, masked addresses and restricted delivery, with checklist rows for them.

    Christopher Holloway committed Sep 24, 2026
    5303aec
  • The three Control Panel pages counted 55 pages and 56 in the tree, 393 and 406 settings in the palette and 3,489 texts, and said a saved [Settings] value waits for a restart. At master 540347500 the navigation map registers 64 pages in the same eight groups - Suppression list, Journaling and dual delivery, Audit trail, Administrator roles, Remote domains, Allow and block list, Greylisting bypass list, Domain white and black list and Setting profiles are the nine since 6.3.3 - the palette indexes 447 settings, the catalogues hold 4,142 texts each, and a save applies at once for 211 of the 241 keys with a mark under each field and a pending bar whose Apply now is a reinitialise. The Control Panel page adds the help pane, the sample domain and where the first-hour checklist is; Control Panel Pages gives every new page its row and marks it in the tree diagram; Control Panel Reference gains a section 5.1 with the nine pages' keys, factories, related links and aliases, and records the domain dialog's fourteen tabs, the account dialog's fifteen and the distribution list dialog's membership query and list manager, each read from the source and labelled as not yet released.

    Christopher Holloway committed Sep 24, 2026
    dcd10c5
  • The pages a new administrator reads first are brought up to master 540347500. What hMailServer Is and Is Not no longer says there is no shared calendaring: it says what the tree after 6.3.3 has (calendars shared with colleagues, groups and delegates, invitations by mail, free-busy, a directory, transport rules, journaling, recall) and what it still has not (ActiveSync, MAPI, Teams, bookable rooms), counts 2,302 tests in 6.3.3 and 3,390 in the tree, and names Linux and the container. Before You Install points a Linux or container reader to their own pages and adds the choice of a setting profile and the first-hour checklist. Installing hMailServer adds the installer's profile page and /profile= switch (written, not yet run in a built installer), the checklist and the sample domain, the drain before an upgrade and [Database] UpgradeOnStart, the schema at 6096, and says the winget and Chocolatey manifests still name GitHub's download. Installing on Linux links Roadmap2's Linux section, lists the AppImages and the GitLab download names, corrects the PKGBUILD's source, gives --set-setting as the way to turn the REST listener on after the first start, lists the new verbs, counts 38 Deck views and 456 of 464 properties, says a save applies at once for 211 keys, and says the Linux suite last ran on 17 September, before its CI host went. Your First Domain and Mailbox adds the sample domain, the quota policy, the out-of-office window, the domain and account dialogs' new tabs, spreadsheet import, SCIM and what a person now does for themselves. How Email Works adds the refusals the tree's SMTP session can give, each off until set.

    Christopher Holloway committed Sep 24, 2026
    e14278e
  • Running in a Container and Connecting a Mail Client said the opposite of the tree after 6.3.3, and now say what it does. The container page called configuration from the environment a roadmap row and warned that a changed HM_REST_* variable is ignored after the first start; since 23 September every [Settings] key and every database setting has an environment name (HM_SETTING_<key>, HM_PROPERTY_<name>, and _FILE forms for a secret), the entrypoint stores them with --apply-environment at every start, the environment wins and an administrator's change to a setting it names is refused, and HM_PROFILE applies a setting profile once. The page says which generation 6.3.3's image is, that none of this has yet been run in a container, and that GHCR belongs to the GitHub organisation while GitLab's registry holds no image, with the steps to build the image from the release's .deb in the meantime. The mail-client page said CardDAV serves one address book, CalDAV one calendar per account, and that iMIP and free-busy are not there; the tree serves every book an account can see (its own, shared ones and the organisation's directory), several calendars shared with accounts, groups and delegates, invitations by mail filed on delivery, and free-busy within the domain. It also says that passkeys and single sign-on reach the webmail and the Deck and not a mail client.

    Christopher Holloway committed Sep 24, 2026
    e1f43c2
  • The APIs Reference's row for the administrator's second factor said an enrolment is refused 'while none is set', which read as the factor; it is refused while no administrator password is set, and while a factor already stands, because a second enrolment would replace the secret every authenticator holds.

    Christopher Holloway committed Sep 24, 2026
    cfd81fb
  • The Web Key Directory's row in the APIs Reference named the domain's and the account's publishing switches as its gate and left out the server's own, OpenPGPWebKeyDirectoryEnabled, which is off by default too.

    Christopher Holloway committed Sep 24, 2026
    8c8a402
  • The Settings Reference's coverage note for the settings store stopped at the gate of 15 September; it now names the latest, batch 33's of 24 September - 3,390 tests in two halves, none failing - and the fixture that proves a save applies what its mark says.

    Christopher Holloway committed Sep 24, 2026
    30c23e5
  • Version History to 6.2.10 went from 6.0.0 straight to 6.2.0, and 6.1.0 was a published release in between: the first Web Control Deck on the REST listener, and themes and a Ctrl+K palette in the classic Administrator, on 6.0.0 build 4's server core at schema 6001. The lineage, the table and the sections now carry it, from the repository's CHANGELOG.md. The 6.0.0 section also says what the CHANGELOG records about its builds: the v6.0.0 tag points at build 2 while the release carried the build 4 installer, and what builds 3 and 4 fixed.

    Christopher Holloway committed Sep 24, 2026
    872ea25
  • The Runbooks Digest said it covered every file in hmailserver/docs, which held thirteen files when it was written and holds 85 Markdown documents at master 540347500. Its scope sentence now says what it digests - the thirteen of 4 September - and section 0 gains a table of the 74 documents added since, grouped by area, each linked on GitLab beside the wiki pages that describe the same ground, with the note that they are not digested here and that Changes Since 6.2.10 has a line for each. The figures it quotes are brought up to that master: the schema is 6096 and the chain runs to Upgrade6095to6096 and new UpgradeScript(6095, 6096), with UpgradeOnStart noted; the suite has 3,390 [Test] attributes to 6.3.3's 2,302; a stored setting applies when it is saved. Two claims it recorded are settled against the documents: the installer has been Authenticode-signed since 6.3.1, though RegulatoryScope.md still says it is outstanding, and section 10 carries a dated note that no binary is committed any more - the manifest lists 35 artifacts and 3 build inputs - and that ThirdPartyBinaries.md's forty is stale in the repository too.

    Christopher Holloway committed Sep 24, 2026
    35609a7
  • The Glossary gains the words the tree after 6.3.3 brought, each saying where it is met and labelled as in the tree after 6.3.3 and not yet released: role, passkey, OpenID Connect, SAML, SCIM and recovery code; mail flow rule, sensitive content, impersonation protection, compromised-account detection, restricted delivery and sandbox; journaling, masked and send-as addresses, the directory, message recall, the list manager, VERP, OpenPGP and its Web Key Directory, protected messages, zero-access mailboxes, the S/MIME authority, gateway encryption, outbound shaping, IP warm-up and the send API; and the settings store, the applies mark, setting levels, environment names, profiles and the drain. Four entries that said the opposite of the tree are corrected: the Control Deck is no longer read-only, the schema version is 6040 in 6.3.3 and 6096 after it, the regression gate is 2,302 tests in 6.3.3 and 3,390 after it, and CodeQL's C++ analysis also ran on pull requests from 18 September, on GitHub Actions, which has not run for the project since that day. The Sigstore entry says that every release up to 6.3.3 was signed through that identity and that the live update still expects it, and the footer names 6.3.3. Settings that are rows of hm_settings are written in code, not in the bold the page keeps for hMailServer.ini keys.

    Christopher Holloway committed Sep 24, 2026
    2967609
  • Capabilities and Configuration is read again at master 540347500. The schema is 6096 there, fifty-six steps after 6.3.3's 6040, and the page says so where it said 6045. The protocol inventory is confirmed unchanged: the EHLO keywords, the IMAP CAPABILITY and the POP3 CAPA are 6.3.3's sets, and what the tree added to SMTP is refusals, which the page now says and points at. The anti-abuse and authentication sections gain one bullet each for the tree after 6.3.3, from sender lists to the attachment sandbox and from roles to SCIM, with their schema steps and what is on by default. The alerts are eleven, seven of them on; the Control Panel has 4,142 texts, 64 pages and a Ctrl+K index of 447; the REST document names 404 paths and 563 operations and the Deck has 38 views, with the census at 456 of 464; the configuration export's ini section is whole since the ini route answers values; and the CalDAV bullet says that iMIP and free-busy have been done since it was written, which it had listed as missing, and that the other three gaps remain.

    Christopher Holloway committed Sep 24, 2026
    7e1a6cb
  • The REST API page's route map stopped at the remote-domain policies, the reports, the audit trail and the alerts of 15 September. It now has a row for every family the OpenAPI document names at master 540347500 - the webmail's calendars, contacts, directory, other accounts, masked and send-as addresses, recovery, OpenPGP, protected messages, zero-access, devices and push; the sign-in, reset and reading pages; the setup checklist, drain, pending settings, environment, levels and profiles; roles, the message trace and every list; DKIM rotation, bounces, complaints, spam traps and reputation; the reports received and the S/MIME authority; webhooks, review, shaping, sandbox, warm-up, migrations and mailbox restore; the send API and SCIM - and the 6.3.3 families it had left out, each labelled 6.3.3 or in the tree after 6.3.3, not yet released. The route count is 404 paths and 563 operations there. The credentials section says where the three credentials overlap in the tree after 6.3.3: an account holding an administrator role reaches the administrative routes its role allows, a key may name a sender and is the only credential of the send API and of SCIM, and a recovery code is taken where an authenticator's code is. The browser-session section gains the four other ways a session is minted - a passkey, OpenID Connect, SAML and the second account's bearer token - and the password reset; the live update gains the drain before it stops the service, the apply on Linux, and the 404 the default feed has answered since 18 September; and the 401 row and one troubleshooting row follow.

    Christopher Holloway committed Sep 24, 2026
    803b629
  • Three rows of the landing page's tables linked Changes Since 6.2.10 and Version History to 6.2.10 as [[Page|Page]], and GitLab splits a table cell at that pipe, so the rendered cell read '[[Changes-Since-6210' with no link and the rest of the row was lost. The rows now link [[Changes-Since-6210]] and [[Version-History-to-6210]], which show the same text.

    Christopher Holloway committed Sep 24, 2026
    2819d5b
  • The APIs Reference is brought up to master 540347500. The OpenAPI document there names 404 paths and 563 path-and-method operations, counted from the path literals in RestApi*.cpp, and 292 of the paths had no row; every family now has one, in the page's own columns, from the account's own routes under /api/v1/me (calendars, tasks and free-busy, contact groups, shared address books, the directory, other accounts, send-as and masked addresses, recover deleted items, messages that expire, offline mail, lists, recall, recovery, both OpenPGP stores, protected messages, zero-access, the S/MIME authority's enrolment, devices and Web Push) through the public sign-in and reading pages (passkeys, OpenID Connect, SAML, the password reset, the list manager, help) to the administration (the setup checklist, the sample domain, drain, pending settings, environment, levels, profiles, roles, the message trace, sender lists, greylisting bypass, domain policy list, DKIM rotation, bounces, complaints, spam traps, reputation, webhooks, the reports received, journaling, the shaping and sandbox queues, warm-up, migrations, mailbox restore), the send API and SCIM. Each row's credential, read-only and domain columns were read from Authorize_, IsApiKeyRoute_, IsMutatingRoute_ and DomainNamedByRoute_, and each is labelled 6.3.3 or in the tree after 6.3.3, not yet released. The second route table had lost its header row, so GitLab showed its forty-odd rows as one paragraph of pipes; it has one again, and the settings PUT row's code span no longer splits its cells. The credentials sections gain the API key's role and send fields, the routes a key is refused with 401, and an account holding an administrator role reaching administrative routes, which section 3d had said no account could. The Control Deck section counts 38 views and the census of 456 of 464; the web services table no longer says the server implements neither CalDAV nor CardDAV, and gains /dav/, the Web Key Directory, the S/MIME authority's publication and the delegated mailboxes in the Autodiscover answer; and the COM section counts 100 coclasses and lists every member the tree has added, by interface.

    Christopher Holloway committed Sep 24, 2026
    aac6ecf
  • The COM page was written against 6.2.28 and knew 94 coclasses, which is 6.3.3's count too. The tree after 6.3.3 has 100, and a new section 23.3a lists what it adds, read from hMailServer.idl at master 540347500 by interface: the six new interfaces (the remote domain policies, the sender list entries and the greylisting bypass entries, each a collection and its item), every member appended to Application, Settings, Domain, Account, Utilities, AntiSpam, Logging, DistributionList, DistributionListRecipient, BackupManager and BackupSettings, the new enumeration values - hStateDraining, five rule criteria, five rule actions, and the outbound TLS and gateway encryption enumerations - and the features that have no COM surface and are REST only. Section 23.2 gains the two changes a script meets: every COM class now carries ISupportErrorInfo, so a refusal comes with its sentence instead of a bare 0x800403E9, and authority is a role that COM asks about through the same RoleManager::Allows the REST API does. Everything new is labelled as in the tree after 6.3.3 and not yet released.

    Christopher Holloway committed Sep 24, 2026
    fd904dc
  • The Settings Reference is re-checked at master 540347500. It said, in three places, that a saved [Settings] value applies at the next start or reinitialise because nothing in SetIniSetting re-runs LoadSettings; that is 6.3.3, and each place now says so and points at a new section 4b for the tree after it, where a save publishes. Section 4b lists every key that does not apply on save - the 28 that wait for a reinitialise and the 2 that wait for a restart, read from the baseline's applies field - the pending list and where it is shown, the one [Settings] key with levels (QuotaWarningPercent, to the account), and every key's name in the environment, HM_SETTING_<key>, with what the environment then refuses. The [Database] table gains UpgradeOnStart, the one bootstrap key added. The CalDavRedirectUrl row said that this server implements neither CalDAV nor CardDAV; it has served CardDAV since 6.3.3 and serves CalDAV in the tree, where an empty value now points discovery at the server's own /dav/, and both rows say what an empty and an unusable value do in each. The baseline is counted again at 267 keys, 241 of them [Settings]; the schema is 6096; the API key file gains its Role and send-API fields; and a new section 17 lists the 164 hm_settings rows the tree has added since 6.3.3, grouped by feature with their defaults from SettingsDefaults.h, since every new setting is such a row now.

    Christopher Holloway committed Sep 24, 2026
    ab1c95e
  • Settings Overview said that making a saved setting take effect without a restart was still a roadmap item, and that a stored value applied at the next start or reinitialise, exactly as before. Both stopped being true on 23 September 2026, in the tree after 6.3.3: a save publishes, 211 of the [Settings] keys are in effect when it returns, 28 wait for a reinitialise and 2 for a restart, and every surface marks each key and lists the ones still waiting. The page now says so, keeps the persist-now-apply-at-next-start rule as 6.3.3's, and notes that the page's per-key timing columns are 6.3.3's, with the listener keys that wait for a reinitialise named. Four new sections describe what the tree added to settings after the store, briefed from SettingsApply.md, SettingLevels.md, EnvironmentConfiguration.md, Profiles.md and ChangedFromStock.md at master 540347500: a save that applies, with the three marks and where they are shown; twenty-seven settings settable per server, domain and account, by kind; every setting named in the environment as HM_SETTING_ or HM_PROPERTY_, and the environment winning; the four profiles with their diff, confirmation and way back; and the list of what a server has changed from stock. The baseline's count is brought to 267 keys, 241 of them [Settings], with [Database] UpgradeOnStart the one key added; the 164 hm_settings rows the tree added are summarised and pointed at the Settings Reference; and the worked example says that the REST listener's keys come up with Apply now.

    Christopher Holloway committed Sep 24, 2026
    b976682
  • The landing page's figures are read again from master 540347500. The schema cell says 6096 in the tree after 6.3.3, fifty-six steps from 6040, and points at the step table rather than listing only the first nineteen. The administration cell counts what the tree has: 64 Control Panel pages to 6.3.3's 55; 404 paths and 563 path-and-method operations in the OpenAPI document, counted from the path literals in RestApi*.cpp as the REST page says to count them, to 6.3.3's 137 and 202; 38 Control Deck views to 6.3.3's 15, reaching 456 of the 464 properties the desktop program writes by DeckParity.md's census; and SCIM provisioning and sign-in by passkey, OpenID Connect or SAML beside the command-line clients. The regression cell gives 2,302 tests in 6.3.3 and 3,390 in the tree, with batch 33's gate of 24 September in its two halves, and says the Linux suite last reported on 17 September. The Control Panel counts elsewhere on the page, the regression-environment row and the settings-reference row follow; the third-party binaries row no longer speaks of forty committed binaries, since the manifest's 35 artifacts and 3 build inputs are none of them in git; and the container row no longer sends a reader to an image on GitHub's registry, which went with the suspended account.

    Christopher Holloway committed Sep 24, 2026
    6e7fb6f
  • Changes Since 6.2.10 is brought up to master 540347500. Section 4e stopped at batch 11, on 16 September; it now carries everything that landed after it, batch 12 to batch 33 between 17 and 24 September 2026, a bullet for each row with its schema step and the repository document behind it, and the fixes the batches' gates found in code that shipped - the message trace's search on SQL Server Compact, a sender domain longer than the column, the heap-corruption abort under concurrent IMAP LIST, and the empty line every relayed message gained. All of it is labelled as in the tree after 6.3.3 and not yet released, and no version number is named. The schema table gains its fifty-one missing steps, 6046 to 6096, each read from its MSSQL upgrade script; the schema sentence, the DBUpdater registration, the chain diagram and the table count (118 in the tree, 51 in 6.3.3, 46 at 6031) follow. The release timeline and the gate table carry the batch 33 gate of 24 September - 3,390 tests in two halves, none failing, three inconclusive from a GnuPG fixture fixed since - and say that the Linux suite last ran on 17 September, before GitHub suspended the project's account. What changes on upgrade without a switch gains nine items from the later batches, the alerts item is corrected to seven of eleven conditions on, and section 7 records the one bootstrap key added since, [Database] UpgradeOnStart, and the applies, levels and environment marks every [Settings] key carries now. The repository's CHANGELOG.md is linked as the version-by-version summary, and the note on where the release bodies came from says they are on the GitLab releases now.

    Christopher Holloway committed Sep 24, 2026
    105a55b
  • The pages that copy repository documents are copied again from master 540347500, so they say what the repository says after the move to GitLab and after the batches that have landed since each was last copied. Contributing and Security Policy follow their files to the root of the repository, where both were rewritten for GitLab: the contributing guide is now the full one - where things are, how to report, the rule for GitHub's issue numbers, the prerequisites, one build command per component, the suites, every checker, the change checklists, commits, sign-off and merge requests - and the security policy supports 6.3.x and takes a report by a GitLab confidential issue or the project's Service Desk address. Governance names two maintainers, and it, the Release Process and the Assurance Case carry the repository's note that the release chain runs on GitHub Actions and cannot run until it moves. The runbooks gain what the tree after 6.3.3 added to them: the settings store in the database and a save that applies the setting, the drain as a state of its own and UpgradeOnStart, the message held for a sandbox, SPF as an RFC 7208 implementation, the Linux update helper, the locked copies of shared collections, the second bench and the gate in halves. Command Line becomes the whole current document, with every verb the clients have gained since 15 September. Most of these pages carry the wiki's own additions - diagrams, tables, worked commands, and corrections the repository has not taken - so each was merged three ways, from the version of the document it was last copied from to master, and the additions were kept wherever they are still true. Where the repository text describes something in the tree after 6.3.3 and not yet released, the page labels it, as the wiki does elsewhere, and says what 6.3.3 does instead where that matters to someone running it. Additions the repository has overtaken are gone or rewritten: the contribution flowchart and the table of required checks, which were GitHub's, are gone; so are the governance duty table and the bus-factor section, which the document now covers with two maintainers; the security flowchart and timeline send a report to GitLab and ask for the CVE there. The Project Handbook and the release diagram describe build/generate-com-wrapper.ps1, which replaced build/regenerate-interop.ps1 on 11 September 2026 when the COM wrapper left git. Each copy says at the top that it was re-copied from master 540347500 on 24 September 2026. Two say plainly where the repository document is itself out of date, and the copy with it: Third-Party Binaries and Regulatory Scope still count forty committed binaries, none of which has been in git since 11 September 2026, and Regulatory Scope still calls Authenticode signing outstanding and the releases GitHub's. The regression environment's 7-Zip path, which the repository document writes with a control character where \7 belongs, reads correctly here. Fuzzing.md has not changed since the wiki's copy, and its page says so.

    Christopher Holloway committed Sep 24, 2026
    3995217