<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Sizing Zimbra Infrastructures — Part 1 - Tech Articles				            </title>
            <link>https://community.zextras.com/forum/tech-articles/sizing-zimbra-infrastructures-part-1/</link>
            <description>Zextras Community Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Mon, 05 Oct 2026 21:42:48 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Sizing Zimbra Infrastructures — Part 1</title>
                        <link>https://community.zextras.com/forum/tech-articles/sizing-zimbra-infrastructures-part-1/#post-1903</link>
                        <pubDate>Fri, 12 Mar 2021 10:03:47 +0000</pubDate>
                        <description><![CDATA[When speaking to Customers and other SysAdmins, one of the “TopTen most frequent questions” is, “How to correctly size my Zimbra infrastructure?”.]]></description>
                        <content:encoded><![CDATA[When speaking to Customers and other SysAdmins, one of the “TopTen most frequent questions” is, “How to correctly size my Zimbra infrastructure?”.]]></content:encoded>
						                            <category domain="https://community.zextras.com/forum/tech-articles/">Tech Articles</category>                        <dc:creator>Luca Arcara</dc:creator>
                        <guid isPermaLink="true">https://community.zextras.com/forum/tech-articles/sizing-zimbra-infrastructures-part-1/#post-1903</guid>
                    </item>
							        </channel>
        </rss>
		