History / Changes Since 6210

Changes Since 6.2.10 and Security Hardening, this wiki's own pages, say what the CHANGELOG, ForkAndOriginal.md and PackageManagers.md say with batch54 on master, 9336fdd59, and what the published CVE records say. Changes Since 6.2.10's timeline row for 6.3.7 calls the fix of CVE-2026-107567, CVE-2026-107568, CVE-2026-107566, CVE-2026-114478 and CVE-2026-114474 mail sent, and signed, in the name of a hosted domain, as the CHANGELOG's 6.3.7 section heads it, where it said mail signed in that name, and gives a REST request a browser made from another site (CVE-2026-114470) and the ACME challenge responder (CVE-2026-114472) places of their own, where 3552b06 put them under what a credential confined to named domains may change, which describes neither: that label now names CVE-2026-114489, CVE-2026-114490, CVE-2026-114476, CVE-2026-114475 and CVE-2026-114477, and ForkAndOriginal.md, which gives each identifier a row of its own, groups none of them. Its 6.3.4 entry on the winget and Chocolatey manifests is headed Listed in Chocolatey's community repository since 23 October 2026; not yet in winget's, where 3552b06 headed it In the public repositories, which is not so of winget, to which nothing has been submitted (PackageManagers.md, "winget: not submitted"), and a semicolon parts the moderator's request of 21 October 2026 from the second sending, where a comma ran the two sentences together. The Affected cells of its tables of what 6.3.6 and 6.3.7 fixed give the versions ForkAndOriginal.md gives, which the records read from the CVE Services API on 24 October 2026 give too, CVE-2026-114490's platform by naming the COM administration API: CVE-2026-103010 Windows, every version up to 6.3.3, where it said every version up to 6.3.3, which took in the Linux builds of 6.3.0 to 6.3.3, its record naming 6.0.0 through 6.3.3 on Windows and the COM method Utilities.BlowfishDecrypt; CVE-2026-104659 every version up to 6.3.5; CVE-2026-114478 and CVE-2026-114474, CVE-2026-114470, CVE-2026-114472 and CVE-2026-114471 every version; CVE-2026-114489 every version, CVE-2026-114475 from 6.3.4 and CVE-2026-114477 from 6.2.25; and CVE-2026-114490 and CVE-2026-114476 from 6.3.4, CVE-2026-114490 on Windows - where each of those seven rows said earlier versions. The page's header says so. Security Hardening's 17.11 says that CVE-2026-100741 was published on 27 September 2026, where it said that it was marked for publication: its record's state is PUBLISHED, published at 07:12 UTC that day, and Roadmap3.md says that it was requested and published. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 24, 2026

Installing hMailServer and Changes Since 6.2.10, this wiki's own pages, say what the documents say with batch54 on master, 9336fdd59, of the Chocolatey package and of 6.3.7's CVE identifiers. Installing hMailServer's paragraph on the package managers is headed choco since 23 October 2026; winget not yet, where it said that neither was usable yet, and says that the chocolatey-publish job sent 6.3.7 a third time on 23 October 2026, with the credit of the original hMailServer's author, Martin Knafve, and that a moderator approved it at 11:56 UTC that day, so that the community repository's feed lists it as Approved and choco install hmailserver-progressiverobot installs 6.3.7 from the release's signed installer, every new version waiting for a moderator the same way, as PackageManagers.md and Channels.md say, where it said that the feed listed it as Submitted and that it would install once a moderator had passed it; that until winget works the installer is downloaded or installed with Chocolatey, where it said downloaded; and that the Chocolatey package passes /LOG and that Chocolatey's CLI makes setup's TEMP its cache folder, by default the chocolatey folder in the temporary folder of the account that ran choco, so that the log and the file with the refusal's words that setup from the release after 6.3.7 writes are there, as Upgrading.md and PackageManagers.md now say. Changes Since 6.2.10's 6.3.4 entry on the winget and Chocolatey manifests says the same of the third sending and the approval, where it said that the feed listed the package as Submitted, not approved, and is headed In the public repositories, where it said Not in the public repositories yet. Its timeline's row for 6.3.7 gives each fix it names the CVE identifiers the CHANGELOG's 6.3.7 section and ForkAndOriginal.md give it - mail signed in the name of a hosted domain CVE-2026-114478 and CVE-2026-114474 besides its three, what a credential confined to named domains may change CVE-2026-114489, CVE-2026-114490, CVE-2026-114476, CVE-2026-114475, CVE-2026-114470, CVE-2026-114477 and CVE-2026-114472, the anti-virus strip action CVE-2026-114479, SRS CVE-2026-114473 and the SMTP log CVE-2026-114471 - where it gave those four fixes none, and the page's header says that the row was given them on 24 October 2026. The identifiers of the page's tables of what 6.3.6 and 6.3.7 fixed already agree with the CHANGELOG and ForkAndOriginal.md, and are unchanged. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 24, 2026

Changes Since 6.2.10, this wiki's own page, gives each flaw of its tables of what 6.3.6 and 6.3.7 fixed its CVE identifier, where twenty-four rows said CVE requested and each table said that such a request was still queued when the page was written: GitLab's CNA assigned and published the sixteen identifiers of 6.3.6's work items 62 to 77 on 8 October 2026 (CVE-2026-107572 to CVE-2026-107587) and the twelve of 6.3.7's work items 86 to 97 on 21 October 2026 (CVE-2026-114470 to CVE-2026-114479, CVE-2026-114489 and CVE-2026-114490), as each published record at cve.org gives them, each record naming its own work item; a row that names several work items names their identifiers in its work items' order. Each table's sentence on queued requests now says when the identifiers were assigned, and the page's header says that the identifiers were added on 23 October 2026. Nothing else on the page changes. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 23, 2026

Eight of this wiki's own pages say what the documents say with batch53 on master, 6fb8164c6, of the container image and MariaDB, of the installer and the original hMailServer's 5.7, and of the Chocolatey package. Running in a Container says that the image carries libpq and, from the release after 6.3.7, MariaDB Connector/C, which the server opens when HM_DB_TYPE is MySQL, and that 6.3.7's image and the ones before it carry libpq alone, reach PostgreSQL only and, told HM_DB_TYPE=MySQL, stop at the entrypoint's --create-database, as ContainerImage.md says, where it said only to point the image at a PostgreSQL or MariaDB server; its row for HM_DB_TYPE and its row for the chart's database values say the same, the latter also that the chart from the release after 6.3.7 passes database.port only when it is set, the type's own port otherwise, and that the chart of 6.3.7 and earlier passes 5432 whatever the type, as the chart's README and values say; and How the image is built and proven says that the image jobs of a v* tag's pipeline made 6.3.6's and 6.3.7's images and that container-image-start and container-image-start-arm64 start each pushed image beside PostgreSQL alone up to 6.3.7 and, from the next release's tag pipeline, beside PostgreSQL and beside MariaDB, where it said that the smoke test had no replacement yet. Before You Install says that a container image reaches MariaDB from the release after 6.3.7, and Installing on Linux that the image installs libmariadb3 itself from that release, as the packaging README says. Upgrading hMailServer's 18.2, after its flowchart and in its table's row for the original's 5.7 builds of August and September 2026, Installing hMailServer, Home's download line and Migration's row for a server of the original's 5.7 say that from the release after 6.3.7 the installer refuses an installation of the original's 5.7 before it changes anything and that the installers of 6.3.7 and earlier do not look and must not be run over one, as Upgrading.md, ForkAndOriginal.md, Migration.md and README.md say, where Upgrading hMailServer said only that setup replaced the program files before DBUpdater stopped and not to run this fork's installer over one, and the other three said nothing of a refusal. Upgrading hMailServer also says that over an installation that the original's 5.7.0 build 3013 or later made new, setup up to 6.3.7 takes it for a new installation and sets up a new, empty database beside the original's, and Installing hMailServer's table of what setup checks before it shows anything has the refusal as a row of its own, with its exit code 1, its log line and its file in %TEMP%. Installing hMailServer and Changes Since 6.2.10's 6.3.4 entry on the winget and Chocolatey manifests say that a moderator returned the Chocolatey package of 20 October 2026 on 21 October, asking that its authors also credit the original hMailServer's author, Martin Knafve, and that chocolatey-publish sent 6.3.7 again on 22 October 2026, saying that it is the fork but not yet crediting him, which the community repository's feed lists as Submitted, as PackageManagers.md says, where they said that the package of 20 October waited for moderation. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 22, 2026

Five of this wiki's own pages say what the documents say with batch52 on master, 72be22b4e, where 22057dd or 988cfbb left them saying otherwise. Upgrading hMailServer's 18.2, after its flowchart and in its table's row for the original's 5.7 builds of August and September 2026, says to install this server on another machine, make the domains and accounts there first and move each mailbox's mail with a migration of kind imap from the original server, a Windows machine holding one of the two since both installers register as hMailServer_is1, as Migration.md's From the original hMailServer and ForkAndOriginal.md say, where it said to set this server up beside it and move the mail over IMAP, which on one Windows machine would have had this fork's installer take the original's installation for its own. Changes Since 6.2.10's 6.3.4 entry on the winget and Chocolatey manifests says that winget's first submission is made by hand and has not been made yet and that Chocolatey's was made by the chocolatey-publish job, which pushed hmailserver-progressiverobot 6.3.7 on 20 October 2026, where it waits for moderation, as PackageManagers.md says, where it said that the first submission to both was by hand; and that the GitHub workflow package-managers.yml was to render and check the manifests on every release, but arrived on 15 September 2026, after the v6.3.3 tag, so that no release ran it, and was not ported to GitLab, where it said that a workflow renders and checks them on every release. The Runbooks Digest's section 6a, on Migration.md, says in What it covers and in Routes (verified) that the original hMailServer moves in place up to 5.6 and its 5.7 releases by a migration of kind imap, with the domains and accounts made here first, as the document says since 21 October 2026 and as the page's own table of routes already said, where both said the upstream hMailServer in place. What hMailServer Is and Is Not's About this fork and Version History to 6.2.10's lineage, in its text and its drawing, no longer say that the original went quiet for years, which README.md no longer says since batch52, the original being developed again; the lineage names the original as Martin Knafve's and says, as README.md does, that it has since resumed development separately. The Contributing copy keeps the clause, CONTRIBUTING.md at 72be22b4e still having it. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 22, 2026

Nine of this wiki's own pages say what the documents say with batch52 on master, 72be22b4e, of the fork and the original, of the channels and of the container image's copies, where they said otherwise. Home says that the wiki documents Progressive Robot's fork of hMailServer, not the original hMailServer by Martin Knafve, with a link to ForkAndOriginal.md, which says how the two differ, where it called it the modernised fork, and that the installer upgrades in place every earlier release of this fork and the original up to 5.6, not the original's 5.7 releases, where it said that it upgraded any earlier hMailServer. What hMailServer Is and Is Not's About this fork says the same, that the original released 5.7.0 on 28 September 2026 and 5.7.1 and a 5.7.2 pre-release on 29 September, and that this fork is not made by Martin Knafve or the original project and is not its successor, and links ForkAndOriginal.md; its two sentences on the design rule say that an installation it upgrades behaves no differently until something is turned on, where they said that an existing hMailServer installation upgrades. Migration's table of routes has the original's 5.7, a migration of kind imap with the domains and accounts made here first, and the Runbooks Digest's table of routes has the original up to 5.6 in place and its 5.7 by that migration, where it had the upstream hMailServer in place; Upgrading hMailServer's 18.2 points at ForkAndOriginal.md. Installing hMailServer says that the Chocolatey package is hmailserver-progressiverobot, pushed by chocolatey-publish on 20 October 2026 and waiting for moderation, that choco install hmailserver finds nothing and is not this project's, the id being the original's, that winget is not submitted and that winget install hMailServer will install the original once a community packager's pull request is merged, and that both installers register as hMailServer_is1, where it said that winget install hMailServer and choco install hmailserver would work once a first submission was reviewed; Changes Since 6.2.10's 6.3.4 entry on the manifests is titled for the manifests and names both ids, where its title was those two commands. Installing on Linux says that OBS, Copr and the PPA carry 6.3.7, for which releases and with what commands, as Channels.md gives them on 21 October 2026, and that the AUR and the Snap Store have nothing yet; it and Running in a Container say that the owner made the copy on ghcr.io public on 20 October 2026 and that the image was copied to Docker Hub as docker.io/progressiverobot/hmailserver on 21 October 2026, each pulling without signing in, where they said that the copy was private and being made public. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 22, 2026

Six more passages of this wiki's own text, found by comparing each copy with its document as master has it from batch51, 5e49abf06, and by a further pass over the pages, say what changes where the service may not write hMailServer.ini, as ServiceAccount.md's table of the writes to hMailServer.INI says, where they said without that condition what the server writes into the file. The Upgrading Guide's paragraph on rolling back across schema 6042, under Rolling back, says that the file the newer server left is a full copy of the stored settings, which the older server reads as the truth, only where the service may write the file, and not under NT SERVICE\hMailServer or the Linux packages' hmailserver user, where the copy is as the last account that could write it left it, as Upgrading hMailServer's note in 18.6 has said since 8d8ed94; and its note on where the [Settings] values come from on a new machine says that since 6.3.4 the restored values are written into the new file at the first start where the service may write it, not under NT SERVICE\hMailServer, a new installation's account. Neither passage is Upgrading.md's, and the page's header names every passage of this wiki's own a comparison with the document finds, none of them in Upgrading.md at any point of its history, where it named five: the pointer to Upgrading hMailServer after the opening, the section What one run looks like with its flowchart and the exit codes, the bullet Not hMailServer.ini, the section on what a failed step leaves on each backend, the note that An upgrade without a window is new in 6.3.4, the installer's two refusals and the notes on the two numbers HM5011 carries and on HM5010 under If the upgrade fails, the paragraph on rolling back across schema 6042, the notes under Special cases on the [Settings] values on a new machine, on the database password and on an installation from before hMailServer 5, the notes for contributors and the corrections under Verified against the code; and it says which three of them say what a file the service may not write changes. Changes Since 6.2.10's 6.3.4 entry on the settings store says that a line still holding what the server last wrote is brought back into line where the file may be written, as its other clauses say since 8d8ed94. The Runbooks Digest says that on the same machine the line the store writes into the file, where the service may write it, is adopted by the new database at its first start, and that under NT SERVICE\hMailServer, where the store writes no line, BackupMessagesDBOnly is checked on the new database before the restore, as MigratingDatabaseBackend.md says. Settings Reference's section 4a says that the whole [Settings] section stays mirrored into the file where the service may write it, the copy not refreshed and stale for whatever reads the file itself under NT SERVICE\hMailServer, and that restoring an archive that carries a pepper into a file the service may not write says so as HM5805, for an administrator to put the value there with an elevated editor (IniSettingStore::XMLLoad). Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 21, 2026

Ten more passages of this wiki's own text, on seven pages, say what changes where the service may not write hMailServer.ini, as ServiceAccount.md's table of the writes to hMailServer.INI says with batch51 on master, 5e49abf06, and IniSettingStore has done since the tag v6.3.4, where they said without that condition what the server writes into the file, or that an edit to it is undone, the shape of the passages the previous commit corrects. Migrating the Database Backend's own sentence on the stored settings under Rolling back says that the rolled-back server rewrites the file's [Settings] section to match where the service may write the file. Warm Standby's worked commands say that a value typed into the INI is not used once the key has a stored value, where they said it was undone. Settings Overview says that DELETE /api/v1/settings/ini/{name}, hmctl ini delete and Settings.DeleteIniSetting remove the line and the row together where the service may write the file, and that where it may not and the file has the line the line stays and the row is kept holding the key's default, which the server treats the same, or the removal is refused for PasswordPepper and a key this build does not read, and that the server adds the [SettingsStore] section where it may write the file. Settings Reference's section 4a says the same of a removal, a dropped row being put back from the line at the next start and the removal said in the application log (IniSettingStore::RemoveSetting), and that what a file the service may not write changes, which the tag v6.3.4 already has, is read from the tree at 5e49abf06, where the section named 3233b0cc4 alone, a tree from before it. Installing on Linux says that on a package installation, whose file is 0640 root:hmailserver, a value stored over the API is in effect and the line left as it was is not an error, the application log saying, where application logging is on, that the file is read-only to the account the server runs as and that its [Settings] copy is not refreshed (IniFileSettings::InitializationFileWritable, IniSettingStore::WriteSetting and Synchronize), where it said that such a value was reported as HM5806 when it was stored and as HM5803 at every start; the packaging README at 5e49abf06 still says so under What lands where, and this wiki follows the code and ServiceAccount.md, which says of the Linux packages that a setting saved is no longer an error at every start. Changes Since 6.2.10's 6.3.4 entry on the settings store and its note on the closed table say that the server writes the [SettingsStore] section where it may write the file, and Upgrading hMailServer's note on rolling back from 6.3.4 says that the newer server writes the [Settings] secrets into the file as HMK1: envelopes where it may write the file. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 21, 2026

Six more passages of this wiki's own text, on four pages, say of a [Settings] line edited in hMailServer.ini, and of a setting saved or removed over REST, what ServiceAccount.md's table of the writes to hMailServer.INI says with batch51 on master, 5e49abf06, and IniSettingStore does: the line is put back, written back or taken out only where the service may write the file, and under NT SERVICE\hMailServer, to which the file is read-only, an edit stays in the file and is not used, a save writes the row alone and a removal of a key whose line is still in the file keeps the row holding the key's default, which the server treats the same, where they said so without the condition 8d8ed94 gave the passages around them. The Upgrading Guide's bullet Not hMailServer.ini under What the upgrade touches, this wiki's own text and not Upgrading.md's, says that an edit to the section is not used at the next start (HM5804), its line put back where the service may write the file and left as edited under NT SERVICE\hMailServer, where it said that the edit was undone, and the page's header names the bullet among this wiki's own additions and says so. Changes Since 6.2.10's note on the settings store finished at the edges says that an edit to the file is not used at the next start, and item 20 of its section 5 is headed that an edit to [Settings] is not used, where both said that the edit was undone; and its 6.3.4 entry on the settings store says that a removal takes out the line and then the row where the service may write the file, and where it may not and the file has the line keeps the row at the key's default, or refuses the removal of PasswordPepper and of a key this build does not read (IniSettingStore::RemoveSetting), where it said that the removal took out the line and the row. The APIs Reference's row for /api/v1/settings/ini/{name} says that PUT brings the file's copy into line where the service may write the file, the row alone under NT SERVICE\hMailServer, a write of the file that fails being HM5806; that DELETE removes the line and then the row where the service may write the file, the line staying and the row kept holding the key's default where it may not, and that there it is a 500 for PasswordPepper and for a key this build does not read, the reason in the error log as HM5806; that a line deleted by hand is written back where the service may write the file, the row kept either way; and that a PUT of PasswordPepper is a 500 where the service may not write the file, the reason in the error log as HM5806, as cb4f10c has Changes Since 6.2.10 and Settings Reference say of the pepper; where it said that PUT brings the copy into line, that a file that cannot be written is HM5806, that DELETE removes the line and then the row, and that the pepper is written to the file, whatever the account. The REST API's row for the ini routes says the same of PUT and DELETE, naming the Linux packages' hmailserver user beside NT SERVICE\hMailServer, where it said that both bring the file's copy into line and that a line deleted by hand is written back. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 21, 2026

Changes Since 6.2.10's 6.3.4 entry on the settings store, Settings Overview, Settings Reference's section 4a and Security Hardening's paragraph on where the pepper lives say that PasswordPepper, set over COM or REST, is written to the file only where the service may write it and is refused with a sentence where it may not, so that under NT SERVICE\hMailServer an administrator sets it in the file with an elevated editor and restarts the service, as ServiceAccount.md's table of the writes to hMailServer.INI has said since the tag v6.3.4 and says with batch51 on master, 5e49abf06, where they said that COM and REST write it to the file whatever the account the service runs as. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 21, 2026

Nineteen of this wiki's own pages say of a [Settings] line edited in hMailServer.ini what RelocatingAnInstallation.md says with batch51 on master, 5e49abf06, and ServiceAccount.md has said since the tag v6.3.4: at the next start the stored value is used and HM5804 names the key, once, and the line is put back where the service may write the file, while under NT SERVICE\hMailServer, to which the file is read-only, as under the Linux packages' hmailserver user, the edit stays in the file (IniSettingStore::Synchronize), where they said without that condition that the line is put back, undone or restored: the APIs Reference, Backup and Restore, Capabilities and Configuration, Changes Since 6.2.10 (its 6.3.4 entry on the settings store and item 20 of its section 5), Control Panel Pages, Encryption and Certificates, the Glossary, Installing hMailServer's table of what writes each key, Monitoring and Health, Ports Reference, Routes and Relays, the Runbooks Digest, Security Hardening, Settings Overview, Settings Reference, The Control Panel, The REST API, Troubleshooting and Upgrading hMailServer. Where the same passages said that the server keeps the file's copy current, writes a deleted line back, brings an older line up to date or rewrites the line after a save, they now say so of a file the service may write, as step 9 of RelocatingAnInstallation.md now says of a save (IniSettingStore::WriteSetting) and ServiceAccount.md's table of the writes to hMailServer.INI says of every start, reinitialise and save: Settings Overview's flowchart has a step for a file the service may not write, where nothing is written, an edit is still named once and a reinitialise names the older lines in the application log where application logging is on; Settings Reference's section 4a says the same of each of its rules, and its rows for HM5803 and HM5804 say that a file the service may not write is not written at all, which the application log says, not as an error, and that HM5804 is said once there because the row records the edited line; and Upgrading hMailServer's note on rolling back from 6.3.4 to 6.3.3 says that the file's permissions under NT SERVICE\hMailServer, like a Linux package installation's unit, keep the server from writing the copy that note relies on. Where Changes Since 6.2.10, Control Panel Pages, the Control Panel Reference, Settings Overview and The Control Panel said that a Control Panel with no connection refuses rather than write a line or a file the server would undo, they say one whose edit the server would not use. The copies of documents that still say it without the condition - Contributing, Diagnosing Stalled Mail, Event Scripts, Migrating the Database Backend, The Update Feed and Warm Standby - follow their documents and are left as they are. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 21, 2026

Six passages of this wiki's own text say what the documents say with batch51 on master, 5e49abf06, where they said otherwise: the Glossary's entry on CodeQL and Changes Since 6.2.10's note on the C++ analysis say that since 18 October 2026 CodeQL analyses the code of the copy on GitHub, GitHub's default setup at first and then the project's workflow .github/workflows/codeql.yml in its place, the Glossary adding that OpenSSF Scorecard's SAST check counts the workflow where it did not count the default setup, where they said that GitHub's own default setup, no workflow of the project's, analysed it; the Project Handbook's section 8 says that from batch51 .github/ also holds CODEOWNERS and workflows/codeql.yml, the two workflows of the project's that GitHub Actions runs, where it called Scorecard's the one; Installing hMailServer says that under NT SERVICE\hMailServer the service says in the application log at a reinitialise, where application logging is on, that the file's copy is not refreshed, as ServiceAccount.md now says, where it said so once a start, and that the file keeps from 6.3.6 the live update's trust beside PasswordPepper; Migration sends a move to another folder or drive to Relocating an Installation and one to a new machine to Backup and Restore, where it sent a new machine to Relocating an Installation, which covers another directory or drive; and Relocating an Installation's own paragraph on moving to new hardware says that from 6.3.6 the live update's trust is read from the file alone and no backup carries it, so that a site that sets it copies it to the new machine with the file (Backup.md), and its header says so. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 21, 2026

Four more places in this wiki's own text name the rule action that calls a function of the event script "Run script function", as the Control Panel's action dialog lists it and EventScripts.md names it with batch50 on master, 0c0b6bae7, where they said "Run function": the APIs Reference and Capabilities and Configuration, each in its account of the JScript escaping fix of 6.3.4; the entry on that fix in section 4e of Changes since 6.2.10, as Security Hardening's account of it says since 9a56d55; and the header of Rules and Sieve, as the page's table of actions already does. Item 27 of section 4h of Changes since 6.2.10 keeps "Run function", as 6.3.7's notes word it, and so does the header of Event Scripts in its account of the copy of 18 October 2026, which it follows with the document's new name. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 20, 2026

The wiki's own pages say what the documents say with batch50 on master: Before You Install's table of databases has the login allowed to create the database - every privilege on its name on MySQL and MariaDB, dbcreator on SQL Server, CREATEDB on PostgreSQL - with DBSetup creating the database itself and refusing a name that exists, and its checklist an empty database made beforehand refused, where they asked for an empty database and a user that may create tables (MigratingDatabaseBackend.md, step 3); Installing on Linux that --create-database does over COM on Windows what DBSetup does, CreateExternalDatabase, DBSetupQuick creating only the built-in database, where it named DBSetupQuick; the Runbooks Digest, under its record of 4 September 2026, that since 19 October 2026 the document's step 3 runs DBSetup.exe and that DBSetupQuick creates only the built-in SQL Server Compact database when [Database] names no type, the step as it recorded it having made no usable database; the Upgrading Guide's backends table, this wiki's own, that DBUpdater runs the whole chain in one transaction on SQL Server and on SQL Server Compact, but for a chain on SQL Server Compact from a database older than 6072 that crosses 6107, which a failure from 6107 on leaves at 6106, and that on MySQL and MariaDB each step's DDL commits as it goes and the failed step may leave part of itself, where it had SQL Server Compact commit DDL as it executes and SQL Server transactional for most DDL (Upgrading.md); Monitoring and Health that Installation paths lists every path-shaped [Settings] and [Database] value but [Database] TlsCaFile, where it said every one (RelocatingAnInstallation.md); Security Hardening, The COM API and Scripting and section 5 of Changes since 6.2.10 that the rule action is "Run script function", as the Control Panel's action dialog lists it and EventScripts.md now names it, where they said "Run function", and Rules and Sieve that the mail flow rule action is "Add disclaimer", where it said "Add a disclaimer" (MailFlowRules.md); and the Glossary, Installing hMailServer, Upgrading hMailServer and the Project Handbook that SPDX and CycloneDX SBOMs come with every release from 6.2.3, the five earlier releases that carry an installer having a CycloneDX SBOM of it alone, made afterwards, where they said every release (README.md, SECURITY.md), that the release assets from 6.2.19 to 6.3.3 are signed with Sigstore but for the two SBOMs of 6.2.22-pre3, which carry no bundle, where they said every release from 6.2.19, or every asset up to 6.3.3, and that the releases up to 6.3.3 whose files GitLab has are re-published there byte for byte, 6.2.0 and 6.0.0-B4 being notes-only, where they said every release up to 6.3.3 (RegulatoryScope.md). Changes since 6.2.10's section 4h keeps "Run function" as 6.3.7's notes word it. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 20, 2026

The wiki's own pages say what the documents say with batch49 on master: the Project Handbook's Scorecard record that the OpenSSF API serves the GitHub copy's score since 19 October 2026, published by the copy's workflow on its first run on master, where it said the API served none for the copy yet; Changes since 6.2.10 and the Settings Reference that nothing has run the Linux suite or the checkers on GitHub Actions since 18 September 2026, and that GitLab CI's checkers job runs every build/check-*.py since 26 September 2026, where they said GitHub Actions had not run for the project at all and the checkers were run by hand; the Glossary, Installing hMailServer and the Project Handbook that the releases before 6.3.1 stay unsigned because every release up to 6.3.3 is re-published on GitLab, and copied to GitHub since 18 October 2026, with its original files and signatures, byte for byte, where they gave a published release's immutability as the reason (SECURITY.md: the GitHub copies were published before the immutable-releases setting was switched on, and can be changed); the Glossary, Installing hMailServer, the Release Process, Upgrading hMailServer, the Settings Reference and Changes since 6.2.10 that GitHub's release workflow signed the releases from 6.2.19 to 6.3.3, where they said every release up to 6.3.3 (no release from 6.0.0-B1 to 6.2.18 carries a Sigstore bundle; SECURITY.md, Verifying a release); Regulatory Scope's Annex I table that the 6.3 line's support period is defined, security fixes until 30 September 2027 and, unless the maintainers write otherwise before then, no support from 1 October 2027, where it said no support period was defined; the Release Process's note at step 9 that since 6.3.6 static-analysis and semgrep fail the pipeline on a finding new to their baselines that master's exceptions file does not accept, while dependency-scan still does not, where it said all three may fail without failing it; and Contributing's paragraphs on the Service Desk and the board without the sentence that the address may change if the project moves to the group hmailserver, which it did on 29 September 2026, and without the clause that a scoped label is not exclusive on GitLab's Free tier, the group having been on GitLab's open-source plan since 13 October 2026. The re-check of the wiki brought to batch49 found these on 19 October 2026; the same shapes were swept on the wiki's own pages, and the copies of repository documents left as their documents have them. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 19, 2026

Six of this wiki's own pages name the feed a server from 6.2.28 to 6.3.3 reads by default as the suspended account's Releases API on GitHub, which has answered 404 since 18 September 2026, as UpdateFeed.md says from batch49 and Upgrading hMailServer and Troubleshooting already say, where they called it GitHub's feed or GitHub's API, answering 404, or said that such a server still reads GitHub, which reads as GitHub itself unavailable now that it serves the project's releases again; the Project Handbook and Changes Since 6.2.10 say that GitHub's own CodeQL default setup has analysed the copy on GitHub since 18 October 2026, where the Handbook said that nothing ran CodeQL; and Capabilities and Configuration calls the Scorecard workflow .github/ holds from batch49 a new one. Installing hMailServer, What a server's own update check trusts: a server from 6.2.28 to 6.3.3 reads by default the Releases API of the suspended account's repository, github.com/Progressiverobot/hmailserver, which has answered 404 since 18 September 2026 and still does, the releases copied to GitHub since 18 October 2026 being under another account, where such a server does not look, as Upgrading hMailServer says, where it said GitHub's release feed. Installing on Linux, the update checker: a server from 6.3.0 to 6.3.3 reads the suspended account's Releases API on GitHub, which has answered 404 since 18 September 2026 and still does, where it said GitHub's feed. Capabilities and Configuration, The feed and the signers, as of 6.3.4: up to 6.3.3 the default feed is the Releases API of the suspended account's repository on GitHub, where it said GitHub's Releases API. The Control Deck, the Update view: the default feed since 6.3.4 is in place of the suspended account's Releases API on GitHub, and a server from 6.2.28 to 6.3.3 still reads the suspended account's Releases API on GitHub until UpdateFeedUrl is set, where it said in place of GitHub's and still reads GitHub. Ports Reference, the update feed's row, and Settings Overview, the comment on UpdateFeedUrl: up to 6.3.3 the suspended account's Releases API on GitHub, which answers 404, where both said GitHub's API. On 19 October 2026 api.github.com answered 404 for the releases of Progressiverobot/hmailserver and 200 for the latest release of RainbowWizard-coder/hMailServer, v6.3.7. The Project Handbook, section 13, Static analysis: codeql.yml, a GitHub Actions workflow of the project's, has not run since 18 September 2026, and nothing runs it on GitLab; since 18 October 2026 GitHub's own CodeQL default setup, no workflow of the project's, analyses the code of the copy on GitHub on each push to master, on each pull request and weekly, and holds no change and no release (SECURITY.md, What ran on GitHub, from batch49; the default setup read as configured, weekly, on 19 October 2026), where it said that CodeQL had not run since 18 September 2026 and nothing ran it on GitLab yet, as the Glossary's row on CodeQL now says too. Changes Since 6.2.10, batch 14: after nothing runs it on GitLab yet, that the default setup analyses the code of the copy on GitHub since 18 October 2026. Capabilities and Configuration, the quality-gates line: from batch49 .github/ holds the pull-request template and a new workflows/scorecard.yml, not the workflow of that name the line lists - the tag v6.3.3's, run on a push to master, weekly on Sundays and on demand, where the new one, for the copy on GitHub, runs on a push to master, weekly on Mondays and on a change to branch protection - where it named workflows/scorecard.yml with nothing to tell the two apart. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 19, 2026

Home, the sidebar, the footer and thirteen of this wiki's own pages say where the project is worked on and where to ask as the documents say it from batch49 - GitLab the one place the project is worked on, and github.com/RainbowWizard-coder/hMailServer its mirror since 18 October 2026, with Discussions and no Issues - where they said that GitHub had been unavailable to the project since 18 September 2026, sent a question to GitLab alone, called the original hMailServer unmaintained and gave the licence as AGPL-3.0; the suspension of the account Progressiverobot on 18 September 2026, and what did not run or answered 404 after it, stay as history. Home's Source and issues: the repository on GitLab, the one place the project is worked on, its mirror on GitHub with copies of the releases and of this wiki, Discussions and no Issues, a pull request there landed through GitLab, and the former account's addresses answering 404 since its suspension, where it said the project's GitHub addresses answered 404; a new Questions: an issue with the Question template, the Q&A of GitHub's Discussions or the forum, and a vulnerability privately, never in a public issue, a discussion or a pull request (SUPPORT.md, SECURITY.md and README.md from batch49). Its row for The Update Feed says since GitHub suspended the project's old account, where it said since GitHub went. The sidebar names the mirror and where a question goes, and the footer links the mirror. Troubleshooting 19.12: issues opened on GitLab alone, a question also in GitHub's Discussions or on the forum, the former project's issues and discussions still gone, a vulnerability reported privately, never in a public issue, a discussion or a pull request; and its row for an update feed answering 404 names the former account's API, where it said the project's GitHub account had been unavailable. The Glossary's footer names the mirror and the licence AGPL-3.0-or-later, and its CodeQL row says that GitHub's own CodeQL default setup analyses the copy on GitHub since 18 October 2026, no workflow of the project's, and that since 6.3.6 static-analysis (cppcheck and clang-tidy) and semgrep fail the pipeline of master, a batch* branch or a release tag on a finding new to their baselines that master's exceptions file does not accept, while dependency-scan (Trivy with OSV) blocks no pipeline and the release job reads its report, as README.md says, where it said only that the workflow had not run since the suspension and that the jobs in its place were not yet blocking. The Project Handbook's and the Runbooks Digest's status notes say that GitLab is the project's home and the one place it is worked on, the account Progressiverobot suspended and GitHub's copy GitLab's mirror, where they began "GitHub has been unavailable to the project since 18 September 2026"; the Handbook also says where a question and a security report go now - a security report never to a public issue, a discussion or a pull request - that sbom.yml and sign-release.yml ran once on 18 October 2026 on the copies of the releases up to 6.2.22-pre6 and have been disabled since, what .github/ holds from batch49, the third reporting route, and that the OpenSSF API, which on 19 October 2026 still served the old workflow's last result, of 18 September 2026, and none for the GitHub copy, is to carry the copy's score once its workflow has run on master (ContinuousIntegration.md from batch49). Changes Since 6.2.10's preamble and Capabilities and Configuration's quality-gates line say the same of the old workflows, where they said that none had run since GitHub became unavailable. Running in a Container and Installing on Linux say that the image was copied to ghcr.io/rainbowwizard-coder/hmailserver on 18 October 2026 and is private, and is not to be pulled from there, as ContainerImage.md words it from batch49, where Running in a Container said that the old account's registry had been unavailable and Installing on Linux that GitLab's registry held no image yet. Installing hMailServer says that every release from 6.0.0-B1 to 6.3.7 is also on GitHub's releases page, copied from GitLab byte for byte, where it called 6.3.4 the first release published on GitLab alone, and gives the licence as AGPL-3.0-or-later; Upgrading hMailServer names the suspended account's Releases API that a server from 6.2.28 to 6.3.3 reads, and the original hMailServer without "unmaintained"; Version History to 6.2.10 says the original project had gone quiet for years and has since resumed development separately, as README.md does from batch49, and What hMailServer Is and Is Not's About this fork says so too, and that Progressive Robot Ltd forked it in 2026 and released 6.0.0 on 12 June 2026, where it said that the original project stopped being maintained; and The COM API and Scripting names GitHub's private vulnerability reporting beside the confidential issue and the Service Desk address. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 19, 2026

Changes Since 6.2.10, Upgrading hMailServer and Home say that 6.3.7 is not on the Snap Store, that MariaDB Connector/C 3.4.11 is in the x64 installer alone, where the three trust settings are cleared and which 6.3.6 servers the live update does not upgrade, and the history's picture ends at 6.3.7, where they said that the snap job puts 6.3.7 on the store, that both Windows installers carry the client, pointed at 18.5 for the clearing, said that every 6.3.6 server's live update installs 6.3.7, and marked 6.3.4 as the latest release. Changes Since 6.2.10, section 4h's Known issues: 6.3.7 is not on the Snap Store, which holds the project's name and no snap yet - the job that puts a release on its edge and candidate channels, started by hand once the release is published, failed for 6.3.7 on a tool missing from its image, after both snaps were built - where it gave the CHANGELOG's sentence from before the release, that the job puts it there (the store answers that it has no snap named hmailserver). The timeline's row for 6.3.7, 4h's Also fixed or hardened and section 4.6: the .NET Desktop Runtime 10.0.13 is in both Windows installers and MariaDB Connector/C 3.4.11 in the x64 one, and the ARM64 installer carries no MySQL or MariaDB client (section_files_common.iss:31-34, which ships libmysql.dll only #ifndef HM_ARM64, section_files_arm64.iss:47 and WindowsOnArm.md:47 at v6.3.7), where they gave the client to both installers. 4h's pointer for clearing the three GitLab trust settings is Upgrading hMailServer 18.7, What the live update installs, where the instructions are, where it said 18.5, which is Things that changed; the same pointer is mended in 18.4e, wrong since 35b7545 wrote it on 5 October 2026 - a section number, not what the section says of 6.3.6 - and in 18.4f. The same history as a picture: 6.3.4 is no longer marked LATEST, and a box for 29 September to 17 October 2026 adds 6.3.5 (6105), 6.3.6 (6108) and 6.3.7 (6108, LATEST). Home, the Download paragraph and the Current release row: a 6.3.6 server's live update installs 6.3.7 but for one installed from a distribution release's own package, which is upgraded with its package manager, as the CHANGELOG's From 6.3.6 says (apt refuses the generic package on Debian 12 and dnf on Enterprise Linux 9), and a server whose three GitLab trust settings still name the path the project began at refuses it until they are cleared, and a container's update check names the image to pull and installs nothing, as 18.4f says, where Home gave the route with no exception. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 18, 2026

Changes Since 6.2.10, Upgrading hMailServer and Home call 6.3.7 the first security release since releases paused, and say of the libraries, the schema and the AArch64 files what is true at 6.3.7, where three sentences still said it of 6.3.6. Changes Since 6.2.10's timeline row and section 4h, Upgrading hMailServer's 18.4f and Home's Current release row say "since releases paused" where they said "made while releases pause": the fact is the same, and the pages that state the pause itself stay the four that state the policy - Security Policy, Release Process, the Project Handbook and Home. Changes Since 6.2.10, section 4.6: today, at 6.3.7, OpenSSL 4.0.3, Boost 1.92.0 and PostgreSQL 18.6's libpq, as at 6.3.6, and on Windows MariaDB Connector/C 3.4.11, where 6.3.6 carried 3.4.9 (build/Get-LibraryVersions.ps1 at the tags v6.3.6 and v6.3.7), where it said today, at 6.3.6. Capabilities and Configuration: 6.3.6 and 6.3.7 require schema 6108, where it named 6.3.6 alone. Installing on Linux: 6.3.6 and 6.3.7 carry the AArch64 packages and AppImages again, where it said 6.3.6 does. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 18, 2026

The release record and the pages on upgrading and installing say what 6.3.7 is - build 46 at schema 6108, which it leaves as 6.3.6 has it, the first security release made while releases pause, tagged and published on 17 October 2026 at the group's path, the same sixty-two files - and how each kind of server reaches it, and Home, the footer, the sidebar and the Glossary name it as the latest release, where they named 6.3.6. Changes Since 6.2.10: the timeline's rows for 6.3.5, 6.3.6 and 6.3.7, 6.3.4's row no longer marked the latest, with the tag pipeline's gates for 6.3.7 (windows-gate on bench150, 2,794 tests, 2,732 passed, 0 failed, 62 skipped; windows-gate-s1vm on S1-WINBENCH, 1,652 tests, 1,634 passed, 0 failed, 18 skipped; linux-suite, 2,652 tests, 2,284 passed, 0 failed, 368 skipped) and the installer smoke test (an upgrade from 6.3.6, 98 checks, and a new installation, 64, none failed); 6.3.7's stamp; section 2 to 6108, and 6.3.7 adding no step; and a section 4h for 6.3.7 - the files and their bundles (160 links), the x64 installer's SHA-256, the container image and its tags, who installs the release by the live update, the flaws fixed with the five identifiers GitLab has assigned and "CVE requested" for the twelve requests still queued, the hardening beside them, the three reports from outside, the four cases of the program folder's permissions not fixed in this release, the thirty-three items of "What changes on upgrade without a switch" in the CHANGELOG's numbering, and what else 6.3.7 carries; section 5's heading points at it, and the CHANGELOG pointer names 6.3.7's section. Upgrading hMailServer: 18.1 gives 6.3.7's schema, 6108, where it gave 6.3.4's 6104 as the current release's; the path's chart and table gain 6.3.5, 6.3.6 and 6.3.7, with the count of steps from each older version to 6108; 18.4's download, its check and the version About shows are 6.3.7's; a section 18.4f for upgrading to 6.3.7, in the release notes' order (the backup and no schema step; the live update's routes from 6.3.6, from 6.3.4 and 6.3.5 and from older versions; the three leftover trust settings; the install by hand; the container; what may need doing before the upgrade; the .NET 10 runtime an upgraded server keeps; what 6.3.7 does not fix; the Control Panel's moved pages); and 18.7's Updates page and the refusal of every release after 6.3.6 by the three leftover settings. Home: the latest release, the download's check, the Current release, Database schema and Regression suite rows and the Changes Since 6.2.10 row. Installing hMailServer: the download link's release, and the program folder, Bin and ControlPanel that /ProtectFolders hardens from 6.3.7. Installing on Linux: 6.3.7's files and schema, and the update applied by the helper of the version it replaces - 6.3.6's helper applies 6.3.7 - where it said so of 6.3.6. Before You Install and Running in a Container: 6.3.7's files and image, and the registry, which held no image when that page's note was written. Each page's header says it was brought up on 18 October 2026 to 6.3.7 for what 6.3.7 changes on it, or what of 6.3.7 is not yet reflected. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 18, 2026

Changes Since 6.2.10 says, as the Project Handbook has said since the copies were brought to the tree, that the builds and suites run only on the project's own runners - the two Windows benches and the three machines that share the tag linix - where its preamble kept the project's own two machines of 29 September, a sentence the tree no longer says (CONTRIBUTING.md and ContinuousIntegration.md at 31d656c0c) and the only corrected text the push of master to main would still have made live for the first time, which the second check of the option-2 commit found with every SAYS text read on every page. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 17, 2026

The release record and the pages on upgrading and installing say what 6.3.6 is - build 45 at schema 6108, published 6 October 2026, signed at the group's path, the last release for the time being - and what an upgrade from 6.3.5 needs. Changes Since 6.2.10: section 2's schema table gains the steps 6104 to 6105, 6105 to 6106, 6106 to 6107 and 6107 to 6108; a section 4f for 6.3.5 (build 44, schema 6105, the first release the tag's pipeline made, its five items) and a section 4g for 6.3.6 - the flaws fixed, with the identifier GitLab has assigned to each or "CVE requested" where the request was still queued, the hardening beside them, the forty-six items of "What changes on upgrade without a switch" in the CHANGELOG's numbering, and what else changes in Operations; section 5's heading points at them. The libraries at the tag (OpenSSL 4.0.3, PostgreSQL 18.6's libpq), days to keep -1 for a move, and the AArch64 packages 6.3.6 carries again. Upgrading hMailServer: 18.2a's step table, 18.4d (upgrading to 6.3.5) and 18.4e (upgrading to 6.3.6, in the release notes' order: the backup and the three one-way steps; DANE and a resolver that strips DNSSEC; the outbound TLS deferrals; days to keep; COM; the administrator's commands, the service account and the installer; the live update's trust and the three leftover settings; the by-hand install under NT SERVICE\hMailServer; Linux by the package manager; the reverse proxy and Host; port 25, the URI lists, ManageSieve, IP addresses in text and the auto-ban across a stop; the webmail's S/MIME certificates; an account's retention; the full restore; the Compose file, the monitor sentence and tlds.txt); 18.5 clears the three leftover trust settings before the update; 18.6 has the installer's exit codes 10 and 11 and the Linux helper's rule. Home: the latest release, the downloads, the Current release and Platform rows. The footer, the sidebar and the Glossary: the stamp. Installing hMailServer: /ProtectFolders at every installation and upgrade, the grant through a junction the administrators control and /GrantServiceAccess's exit code 7, --grant-database-login, the program folder's folders private, a new installation set up with no window; the download link's release. Installing on Linux: 6.3.6's packages for both architectures and each supported distribution release, the version-less download links, the AppImage's folders made 0700, the schema line, the packages' requirements and licence files, the .rpm's character-set converters, a store command run as root, --check-config's character sets, tlds.txt gone, the backup and event logs in UTF-8, the live update helper's --unit and --image and the copies it installs from, the drain left on a refused request (HM7151), the auto-ban after a stop, and the AArch64 row. Before You Install: what 6.3.6 carries, libpq 18.6, the pre-flight line. Running in a Container: the image at the group's registry path and its 6.3.6 tag, PostgreSQL 18 at /var/lib/postgresql in the Compose file, the container's update check, HM_DB_WAIT_SECONDS. Each page's header says it was brought up on 5 October 2026 to 6.3.6 for what 6.3.6 changes on it. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 5, 2026

Every link to the project points at its address in the group, gitlab.com/hmailserver/hmailserver, where it has been since 29 September 2026; the identities 6.3.5 was signed with, and the setting row that lists both paths, keep the path the project began at. The project's path in all 63 pages that linked it (548 links), 6.3.6 being the first release made at the group's path. Left as they were: the seven signing identities https://gitlab.com/Progressiverobot/hmailserver//.gitlab-ci.yml@refs/tags/v... (Release Process, Security Policy, The Update Feed, and the UpdateSigningIdentity row of Settings Reference), which name what 6.3.5 was signed as; and the UpdateSourceRepository row of Settings Reference, which lists both paths on purpose. The container registry's name is corrected with the container page. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Oct 5, 2026

The pages on CI, the release process, the test environment and the project's home are brought up to the tree as it stands for 6.3.6 (batch42 at d8a84f66c, with the branch b42-feeds-docs) and to master's first full pipeline (GitLab work item #21). The five copies of repository documents take every change their documents have had since the tag v6.3.4 (51e2dbda0), merged three ways from the document at the tag to the document now, so that this wiki's own additions stay: Security Policy (SECURITY.md: "While releases pause" - 6.3.6 the last release for the time being, security fixes for the 6.3 line until 30 September 2027 by the maintainers' decision, what gets a release, how a report is handled, the five steps of a security release only the owner can take, what a release depends on that expires; no Azure secret on GitLab; the .sigstore.json copies and the SLSA provenance from 6.3.6), Release Process (RELEASE.md: "A security release during the pause", placed before this wiki's "The release at a glance"; the release jobs' fifty-seven files from 6.3.6 and the batch branches' rehearsal), Contributing (Roadmap3.md, the AppImage's own runtime, the upgrade gate from 6029's create script, linux-repro, three new checkers, and the package, release and rehearsal jobs in place of the release job the document called a placeholder, which the tree now corrects as well), Fuzzing (the commit the old workflow is at) and Regression Test Environment (the Linux suite's counts and the coverage schedule). Each header says what it was brought up to, and where it still differs from its document: the latest release is given as 6.3.4, published on 27 September 2026, until 6.3.5 is out, where the tree is already stamped for 6.3.5; Security Policy keeps its account of the 455 findings accepted at 6.3.4. The statements that no GitLab job had run are replaced with what ran. Master's pipeline 2886389460, 27 September 2026 04:19 to 07:55 UTC on 6bc09509d, read from GitLab's API on 29 September 2026: 29 jobs, 25 passed; windows-gate on bench150, 3,811 tests, 3,736 passed, 0 failed, 74 skipped, 1 inconclusive, and linux-suite on linix, 2,020 tests, 1,710 passed, 0 failed, 310 skipped, each 8,563 s; db-matrix left manual; secret_detection, semgrep and static-analysis failed, each on a fault of the tree's that batch41 mends (#21's notes). So on Home (the regression suite; the current release, with the pause; following releases, with updates.progressiverobot.com/releases.atom from 6.3.6 beside GitLab's own feed; the Security Policy and Release Process rows), the Project Handbook (the status note and sections 7, 8, 9, 11 and 12: GitLab CI's jobs have run, a change lands through a merge request the other maintainer approves with build/land-via-mr.py, the pause), Installing on Linux (linux-cross passed, 559 s), Running in a Container (linux-image and chart-and-compose passed), Changes Since 6.2.10 (GitLab CI runs the checks' replacements; the first full pipeline on the fixed tree), Contributing (a note marked Now) and Regression Test Environment (its header). Fuzzing's Now note: the schedule exists (4461177), and its first two nights, pipelines 2887914840 and 2891652158 on 28 and 29 September 2026, ran linux-fuzz alone and passed, about an hour each. Governance and Regulatory Scope were read and left: their documents have not changed since v6.3.4, and what they say of CI and the release jobs (written, not yet run on a release tag) is still true. Every wiki link and in-page anchor the changes add resolves. Signed-off-by: Christopher Holloway <chris.holloway@progressiverobot.com>

Christopher Holloway committed Sep 29, 2026

The wiki is brought up to the published release: 6.3.4 is the signed tag v6.3.4 at 51e2dbda0, published on GitLab on 27 September 2026 (02:37:56 UTC), not 8adce850a of 26 September, where the tag was first made and whose release gate failed. Every page that named 8adce850a as the tag or the release names 51e2dbda0, and every page that dated the release 26 September dates it 27 September: the footer, the sidebar, the page headers, the landing page's Current release, the release timeline's row and picture, section 4e's heading. Each fact those pages took from 8adce850a was checked at 51e2dbda0: the commits between the two change 42 files, whose only documents are CHANGELOG.md, BrandLogos.md, OpenPGP.md and SecretsAtRest.md, none of which a page copies, and which include none of Constants.h, Version.h, formMain.cs, the create scripts, IniFileSettings.cpp, SettingsDefaults.h, the IDL, the Control Panel or .gitlab/allowed_signers, so every file and line cited at the tag holds. Where a page said it read the tag on 26 September, it says it read 8adce850a and that what it read is the same at the tag. The suite has 3,811 [Test] attributes at the tag, not 3,809 (the fixes add two tests); twelve places say so. Changes Since 6.2.10 gains, in batch 40, what the release gate found and the eleven fixes: three change tests alone; of the other eight, three fix what 6.3.3 did too - a relay that refused the OAuth2 login got the server's token into the bounce and the logs (open since 6.2.22-pre1), a rule's forward, copy, reply or notice and an account's forwarding could wait a minute in the queue, and IMAP LIST and LSUB took a literal's length for the pattern - and five fix code new in 6.3.4 (sealed mail and an unnamed part, a closed key's FETCH refusal logged as a critical error, the help desk's password reset read as bytes, the logo and key-directory holds, an alert's encoded Subject over 76 characters). The gate table and the timeline give the re-run on 51e2dbda0 as the logs have it: 2,349 on the first bench (2,252 passed, 0 failed, 97 skipped) and 1,462 on the second (1,446 passed, 0 failed, 16 skipped), the 71 live-update tests elevated, all passed, and the Linux suite on the packaged binary, 2,013 tests, 1,562 passed, 0 failed, 451 skipped (results/b40full3 on linix); the database upgrade gates, the security scans, the fuzzers and the installer smoke test, 65 of 65. The JScript flaw is CVE-2026-100741 (CVSS 3.1 9.8), and the project's issue #43 is public: Security Hardening 17.11, the scripting page, the changes, the capabilities and the API reference name them. The project's download links work (the site has served HTTPS since 26 September; on 27 September they led to 6.3.4's files), so Installing on Linux and Running in a Container no longer say they work once it does. The copies of SECURITY.md and CONTRIBUTING.md give the day GitLab published the release, and the security policy's copy counts the 455 findings .gitlab/security-exceptions.yml accepts at the tag - the 169 of the SAST triage and the 286 that held the release scan - where the repository document still says 169; each header says where the copy differs. Three places said no pipeline had run on the fixed tree; one has, the schedule of 27 September 2026 on master 6bc09509d, which ran the update feed's pages and package-repos jobs alone, and they say so.

Christopher Holloway committed Sep 27, 2026

What the check of 2e1d40e against the tag v6.3.4 (8adce850a) found, put right. Changes Since 6.2.10, section 4e, named the seven High findings of GitLab's SAST as .gitlab/security-exceptions.yml at the tag does not: the seven are the crash-dump helper's dbghelp.dll, the Control Panel's elevated restart, DBSetupQuick handing DBUpdater the password on its command line (two), the backup index parser (two) and a MIME parser test that compared pointers into two arrays; the MySQL client's DLL search, the installer's command line and the %FILE% scanner path were found beside them. The audit item said an app password could change the account's keys; it could replace the own S/MIME key and publish an OpenPGP key, and a support session could change any of them or switch zero access off (CHANGELOG 6.3.4). Release Process: the note at step 9 said no pipeline had run the scans on the project's own runners; the first pipeline, on master 40c7d3e0c, ran dependency-scan, static-analysis and semgrep, which failed as they may without failing the pipeline, and semgrep-sast came in batch40. The note at step 12 said a tree lands on master by fast-forward with no merge request; that is so up to 6.3.4, and from the first landing after it a batch lands through an approved merge request (ContinuousIntegration.md, "Landing on master"). Installing hMailServer: the administrator password "may hold any character" and HM_ADMIN_PASSWORD "takes any character" were wider than the tag, which refuses a password holding U+0000 and whose /adminpassword switch drops a double quote; they now say what the variable carries. Control Panel Reference: the tag adds no page, text or index entry but rewrites one text, the one that explains ProtectStoredSecretsWithDPAPI, in every catalogue. Settings Reference: no passkey is taken while a relying party is set without PasskeyAllowedOrigins, not "until then". Regression Test Environment: the header says this copy gives the [Test] count where the document says roughly 2,000.

Christopher Holloway committed Sep 26, 2026

The wiki is brought up to the release itself, the signed tag v6.3.4 at 8adce850a: what it said of 6.3.4 had been read from master 92b8f9f63, which the tag's last batch, batch40, follows. Schema 6104, not 6103: 6.3.4 is sixty-four steps from 6.3.3's 6040, the last, 6103 to 6104, adding hm_fetchaccounts.faorigin (Constants.h:1224, formMain.cs:314 and the three create scripts at the tag); every header, table, count and diagram that gave 6103 as 6.3.4's schema says 6104, the upgrade table's step counts are each one more, the step tables gain the 6104 row, and where 6103 means the secrets-at-rest step it stays. No page calls 92b8f9f63 the release or the tree 6.3.4 was cut from any more: a page checked against it says so and that the tag adds a last batch, and a page that copies a repository document the tag leaves as it was says the document is the same at the tag. The copies of repository documents batch40 changes are brought up to the tag, hunk by hunk from the version each copy had reached, their own additions kept: Security Policy (the SSH-signed sums of a release made by hand and the two commands that check a download, an SBOM for every compiled file, a release held by its security scans, secrets refused before they are pushed; its note no longer says the document calls 6.3.3 the latest), Release Process (A release made by hand, the security gate, the SBOM jobs), Upgrading Guide (the installer's HM_ADMIN_PASSWORD, the named lock on MySQL and MariaDB, the probe that stops an upgrade on too old a server at 6041 and the repair of a half-done one), Contributing, Governance (rebuilt on the tag's document, which gives the GitLab roles the owner set on 26 September 2026; the map and the note on code-signing material kept), Assurance Case, Regulatory Scope, Third-Party Binaries, Fuzzing, Migrating the Database Backend and Regression Test Environment. The installer's password handling as the tag has it: the password page is skipped for HM_ADMIN_PASSWORD as for /adminpassword, the database step hands the password (or the live update's token, as token:<hex>) to DBSetupQuick and DBSetup in HM_ADMIN_PASSWORD and DBSetupQuick to DBUpdater the same way, never on a command line, the switch table has the variable, and the unattended upgrade takes either (Installing hMailServer, Upgrading hMailServer 18.4a). How to verify a download: 6.3.4's hmailserver-6.3.4-SHA256SUMS.txt and its .sig, checked with ssh-keygen -Y verify against .gitlab/allowed_signers and sha256sum -c, as SECURITY.md at the tag gives them, and each installer's and package's own SBOM (Installing hMailServer 4.1, Installing on Linux, Upgrading hMailServer 18.4 and 18.4c, home, Release Process, Project Handbook, Troubleshooting, Glossary, Assurance Case, Regulatory Scope). The /download/ links no longer wait on issue #30: the feed's site has had its certificate since 26 September 2026. Changes Since 6.2.10 gains batch 40 in section 4e (the audit before the release, GitLab's SAST and the release gate, the installer's password, the SBOMs and signed sums, the stable download links, the release chain and landing through merge requests, what the first pipeline found, Windows on ARM compiled), items 47 to 51 in section 5 (reserved domain names, a one-time code taken once, the outbound relay's OAuth2 token over TLS only, the fetchers and schema 6104, a pre-6.3.4 hash of a password above U+00FF refused), SQLOLEDB in item 38, the 6041 probe in item 36, and the installer's own PBKDF2 in item 39. Also what the tag makes false elsewhere: the suite has 3,809 [Test] attributes, not 3,698; hmailserver/docs holds 105 documents; Windows on ARM compiles and has never run, where it was "not built"; IMAP offers STARTTLS only before sign-in and TLS and COMPRESS=DEFLATE only after sign-in (Capabilities and Configuration); a parent-domain passkey relying party needs passkey_allowed_origins (Sign-in and Identity); the Settings Reference counts 193 hm_settings rows with PasskeyAllowedOrigins and WebPushLoopbackHttpForTests; and the Linux suite's CI job first ran in the pipeline of 26 September 2026 rather than never.

Christopher Holloway committed Sep 26, 2026

What the check of the batch40 wiki pass found, put right. The group signer was described from e3df8b5e6, before 396c01d4d moved the rule to the match: a certificate that names hmailserver/hmailserver, or its repository, is refused without the project's id whatever UpdateSigningIdentity, UpdateSigningIssuer and UpdateSourceRepository say, `-` included. Security Policy lacked SECURITY.md's "whatever its update settings say"; the Settings Reference said `-` switches the repository check off with no exception and cited the older lines, now SigstoreVerifier.cpp at 396c01d4d; and the Settings Reference, Upgrading and the 6.3.4 changes now carry UpdateFeed.md's warning that a server from 6.2.28 to 6.3.3, which checks no id, is never to have the three settings pointed at the group's path and is upgraded by hand after the move. From ci-hyg, which is now committed: Contributing says the two machines take no job for a push that changes only Markdown at the root or under .gitlab/, and its header no longer says the repository document names the renovate schedule by a variable; Security Policy replaces "Nothing scans pushes to GitLab yet" with the secret_detection job and the one scan of the whole history. Governance said Christopher Holloway alone holds the project's administration, where GitLab listed all three members - Progressiverobot, zainulabidin1990 and chrisholloway5 - as Owner on 26 September 2026 (GET projects/86730559/members/all); it says so, and that lowering those roles is the owner's decision.

Christopher Holloway committed Sep 26, 2026

The wiki is brought up to the tree batch40 will contain: the branches ns-verifier, gl-project, gov, ci-hyg and tf, read from the repository on 26 September 2026. The copies of repository documents take the changes batch40 makes to them - CONTRIBUTING, SECURITY, RELEASE, GOVERNANCE, ASSURANCE-CASE, Fuzzing, RegulatoryScope, ThirdPartyBinaries and RegressionEnvironment - each header saying so. The seven links into /-/blob/master/.github/ point at .gitlab/allowed_signers, .gitlab/hmailserver.openvex.json, or name the GitHub workflow as being in the git history at v6.3.3, since .github/ is gone from the tree; the verify-tag commands read .gitlab/allowed_signers. What the sweep made false is put right: the PKGBUILD builds from the tag on GitLab; the Compose file and the chart name registry.gitlab.com/progressiverobot/hmailserver, a registry that is switched on and holds no image yet; OpenSSL's release archive comes from Debian's archive against its pinned hash; linuxdeploy is no longer downloaded; the build-inputs-1 files come from the package registry; the manifests name the installer's file there. The live update's third signer, the group hmailserver the project is to move to, with the project's id required, is on the update and security pages, the Settings Reference and the changes for 6.3.4, with the three GitLab settings that keep a server to the present path. Governance names Zain Ul Abidin as zainulabidin1990 on GitLab and gives the owner's rule that release tags are created by the Progressiverobot account alone. The /download/ links at updates.progressiverobot.com are given beside the permalinks, labelled as working once that site serves HTTPS (issue #30; it still failed at 05:16). Contributing gains a section of its own on the issue and merge-request templates, the Service Desk, the two boards and the labels as they are on GitLab.

Christopher Holloway committed Sep 26, 2026

What the check of the merged wiki found, put right. The landing page counted 61 pages, 34 guides and 'the other 60', and listed none of the four pages written for 6.3.4: it counts 65, 38 and 64, and Message Storage, Compliance and eDiscovery, Rooms and Equipment and Mail In to a Webhook have their rows where the sidebar groups them. Twelve sentences named the next release as 6.3.5; each now says the releases after 6.3.4, since nothing after 6.3.4 has a number yet. Installing on Linux said the AppImages began in 6.3.2, where the GitLab releases of 6.3.0 and 6.3.1 carry both of them. Capabilities and Configuration gave 23 per-account tables as today's count, where AccountStores.cpp declares 62 in 6.3.4, 24 carried and 38 exceptions; the old figures stay, labelled with 3233b0cc4. The Settings Reference counted 26 bootstrap keys, where build/ini-settings-baseline.txt has 29. And Stopping Spam said the quarantine digest needs its domain's switch and hour, when an account may hold a value of its own for both (EffectiveSetting.cpp, QuarantineDigestTask.cpp).

Christopher Holloway committed Sep 26, 2026