<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Where to post what: a map of the forum categories]]></title><description><![CDATA[<p dir="auto">The category tree is small on purpose, but a few boundaries are not obvious. This is where each thing goes. If you get it wrong, a moderator moves the topic rather than closing it.</p>
<h2><a class="anchor-offset" name="running-hmailserver"></a>Running hMailServer</h2>
<p dir="auto"><strong>General support.</strong> The catch-all. If none of the categories below is clearly right, post here.</p>
<p dir="auto"><strong>Installation, migration and upgrades.</strong> Installer failures, moving an install to new hardware, changing database backend, and anything that went wrong during an upgrade. Read §18 of the <a href="https://www.progressiverobot.com/hmailserver-documentation/" rel="nofollow ugc">documentation</a> first.</p>
<p dir="auto"><strong>Linux.</strong> Packaging, systemd, file permissions, and anything specific to the <code>.deb</code>, <code>.rpm</code> or AppImage builds. Linux support arrived in 6.3.0. A protocol question that would be identical on Windows goes to General support.</p>
<p dir="auto"><strong>Webmail, portal and Control Deck.</strong> The web interfaces themselves. Mail that never arrived is a delivery problem, not a webmail problem.</p>
<p dir="auto"><strong>TLS certificates and deliverability.</strong> Certificate chains and renewal, TLS on the mail ports, SPF, DKIM, DMARC and reverse DNS. Anything ending in "the recipient rejected it" starts here. Documentation §8 and §9.</p>
<p dir="auto"><strong>Anti-spam and message filtering.</strong> Scoring, blocklists, false positives, virus scanning. Documentation §10 and §11.</p>
<p dir="auto"><strong>Guides and tutorials.</strong> Finished, tested write-ups. Not questions. If you are still asking, ask elsewhere and write the guide afterwards.</p>
<h2><a class="anchor-offset" name="automation-and-integration"></a>Automation and integration</h2>
<p dir="auto"><strong>Scripting and the COM API.</strong> Server-side scripts and anything driving hMailServer through COM.</p>
<p dir="auto"><strong>REST API and integrations.</strong> The HTTP API, and third-party systems talking to it.</p>
<p dir="auto"><strong>Rules, Sieve and routing.</strong> Server and account rules, Sieve scripts, routes and relays. Documentation §12 and §14.</p>
<p dir="auto"><strong>Monitoring, metrics and logs.</strong> Reading the logs, <code>JsonLogging=1</code> output going into Elasticsearch, Loki or Splunk, health checks and alerting. Documentation §16. A log line you cannot interpret that turns out to be a delivery fault still belongs in the relevant support category.</p>
<h2><a class="anchor-offset" name="development-and-roadmap"></a>Development and roadmap</h2>
<p dir="auto"><strong>Bug reports.</strong> Reproducible defects only. Version including build stamp, platform, database backend, and the steps that reproduce it. Confirmed bugs are tracked at <a href="https://gitlab.com/hmailserver/hmailserver" rel="nofollow ugc">https://gitlab.com/hmailserver/hmailserver</a>.</p>
<p dir="auto"><strong>Pre-release builds.</strong> Anything that is not a signed release. Keep pre-release findings out of the support categories, because the answers there assume a released build.</p>
<p dir="auto"><strong>Feature requests.</strong> One request per topic, so each can be discussed and closed on its own.</p>
<h2><a class="anchor-offset" name="community"></a>Community</h2>
<p dir="auto"><strong>Off-topic.</strong> Everything else.</p>
<p dir="auto"><strong>Forum feedback and help.</strong> Problems with this forum: accounts, formatting, moderation, categories.</p>
<h2><a class="anchor-offset" name="managed-hmailserver"></a>Managed hMailServer</h2>
<p dir="auto">For customers of the <a href="https://www.progressiverobot.com/hmailserver-services/" rel="nofollow ugc">managed service</a>. Do not post account or billing details in public.</p>
<p dir="auto">Whichever category you pick, the checklist in the pinned posting guide still applies. Version with build stamp, platform, database backend, upgrade or fresh install, logs with credentials redacted.</p>
]]></description><link>https://www.hmailserver.co.uk/topic/28186/where-to-post-what-a-map-of-the-forum-categories</link><generator>RSS for Node</generator><lastBuildDate>Fri, 06 Nov 2026 09:05:48 GMT</lastBuildDate><atom:link href="https://www.hmailserver.co.uk/topic/28186.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 23 Sep 2026 01:05:00 GMT</pubDate><ttl>60</ttl></channel></rss>