<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="atom.xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://intranet.ibpm.pl/blog</id>
    <title>Intranet IBPM S.A. Blog</title>
    <updated>2026-02-19T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://intranet.ibpm.pl/blog"/>
    <subtitle>Intranet IBPM S.A. Blog</subtitle>
    <icon>https://intranet.ibpm.pl/img/favicon.ico</icon>
    <entry>
        <title type="html"><![CDATA[Welcome to the new version]]></title>
        <id>https://intranet.ibpm.pl/blog/2026-02-19-welcome</id>
        <link href="https://intranet.ibpm.pl/blog/2026-02-19-welcome"/>
        <updated>2026-02-19T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[🚀 New clothes of front-001: Evolution in the shadow of containers - Hardcore Infrastructure Reconstruction]]></summary>
        <content type="html"><![CDATA[<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-new-clothes-of-front-001-evolution-in-the-shadow-of-containers---hardcore-infrastructure-reconstruction">🚀 New clothes of <code>front-001</code>: Evolution in the shadow of containers - Hardcore Infrastructure Reconstruction<a href="https://intranet.ibpm.pl/blog/2026-02-19-welcome#-new-clothes-of-front-001-evolution-in-the-shadow-of-containers---hardcore-infrastructure-reconstruction" class="hash-link" aria-label="Direct link to -new-clothes-of-front-001-evolution-in-the-shadow-of-containers---hardcore-infrastructure-reconstruction" title="Direct link to -new-clothes-of-front-001-evolution-in-the-shadow-of-containers---hardcore-infrastructure-reconstruction" translate="no">​</a></h2>
<p>Welcome to the new version of our infrastructure! The changes you see on the surface today are just the tip of the iceberg. Beneath, we've waged a battle we've provisionally called "The Great Cleanup of 2026."</p>
<p><img decoding="async" loading="lazy" alt="Hardcore Infrastructure Reconstruction" src="https://intranet.ibpm.pl/assets/images/Gemini_Generated_Image_t9ggtmt9ggtmt9gg-en-93d0d53b61fc5feb27f2ac5e9910ebec.png" width="1792" height="576" class="img_ev3q"></p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-new-clothes">Why "new clothes"?<a href="https://intranet.ibpm.pl/blog/2026-02-19-welcome#why-new-clothes" class="hash-link" aria-label="Direct link to Why &quot;new clothes&quot;?" title="Direct link to Why &quot;new clothes&quot;?" translate="no">​</a></h3>
<p>The previous configuration, while faithful, began to resemble a well-known, yet somehow too tight, suit. We decided to move our ecosystem onto a more modern track – we switched to <strong>AlmaLinux</strong>, invited <strong>Podman</strong> to collaborate, and decided to streamline what's most important in any email system: the flow of information.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="anatomy-of-a-slaughterhouse-or-what-happened-behind-the-scenes">Anatomy of a "slaughterhouse", or what happened behind the scenes<a href="https://intranet.ibpm.pl/blog/2026-02-19-welcome#anatomy-of-a-slaughterhouse-or-what-happened-behind-the-scenes" class="hash-link" aria-label="Direct link to Anatomy of a &quot;slaughterhouse&quot;, or what happened behind the scenes" title="Direct link to Anatomy of a &quot;slaughterhouse&quot;, or what happened behind the scenes" translate="no">​</a></h3>
<p>The road to today's stable <code>front-001</code> wasn't a bed of roses. If you were wondering why the admins were drinking more coffee this week, here are some technical skirmishes:</p>
<ul>
<li class=""><strong>Battle for Domain Identity:</strong> It was crucial to teach the server when a domain belonged to it (<code>ibpm.pl</code>) and when it absolutely had to be forwarded (e.g., to Office365 for <code>.pro</code>). We struggled with an overzealous LDAP that persistently tried to "steal" external emails. The solution? Surgically precise filters that checked administrative groups.</li>
<li class=""><strong>Taming Cross-Domain Aliases:</strong> Even when the domain was routed correctly, Postfix could "suck in" emails destined for Office365 if it found a matching alias in the local LDAP. We introduced "robust" user filters that only accepted a match if the domain in the query was exactly the local domain. And yes – we closed all the parentheses in the filters!</li>
<li class=""><strong>Podman and SELinux Adoption:</strong> Migrating to AlmaLinux with Podman presented us with a challenge of permissions and security contexts. Properly mapping volumes with the <code>:z</code> flag became crucial so that configuration changes on the host were immediately visible inside the container.</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-does-this-mean-for-you">What does this mean for you?<a href="https://intranet.ibpm.pl/blog/2026-02-19-welcome#what-does-this-mean-for-you" class="hash-link" aria-label="Direct link to What does this mean for you?" title="Direct link to What does this mean for you?" translate="no">​</a></h3>
<p>First and foremost – <strong>certainty</strong>. The new architecture means greater service isolation, easier deployment, and configuration that's predictable and secure. Jira and notification systems now operate in an environment tailored precisely to our needs, eliminating message delivery issues.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-final-word">A final word<a href="https://intranet.ibpm.pl/blog/2026-02-19-welcome#a-final-word" class="hash-link" aria-label="Direct link to A final word" title="Direct link to A final word" translate="no">​</a></h3>
<p>Thank you for your patience during these "difficulties." Every corrected bracket and every verified trusted network is a step towards a system we can rely on.</p>
<p><strong>IBPM Special Tasks Team</strong></p>]]></content>
        <author>
            <name>Sławomir Cichy</name>
            <uri>https://slawas.pl</uri>
        </author>
        <category label="Welcome" term="Welcome"/>
    </entry>
</feed>