<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Postfix | A DevOps Blog</title><link>https://blog.bsdserver.nl/tag/postfix/</link><description>Hands-on DevOps and homelab content: Kubernetes clusters, self-hosted services, CI/CD pipelines and infrastructure as code, by Patrick de Ruiter of We Build Your Cloud.</description><language>en</language><image><url>https://blog.bsdserver.nl/images/app-icon.svg</url><title>A DevOps Blog</title><link>https://blog.bsdserver.nl/</link></image><lastBuildDate>Wed, 18 Nov 2026 09:00:00 +0100</lastBuildDate><atom:link href="https://blog.bsdserver.nl/tag/postfix/rss/" rel="self" type="application/rss+xml"/><ttl>60</ttl><item><title>Set Up Your Own Postfix SMTP Relay with Docker Compose</title><link>https://blog.bsdserver.nl/set-up-your-own-postfix-smtp-relay-with-docker-compose/</link><guid isPermaLink="false">693b523779eb54000160a4c5</guid><dc:creator>Patrick de Ruiter</dc:creator><pubDate>Thu, 11 Dec 2025 23:22:31 +0000</pubDate><description>Imagine having a reliable email relay system under your control - no more dependence on external SMTP servers, no more unnecessary costs, and complete…</description><category>Docker</category><category>Email</category><category>Postfix</category><category>DevOps</category><media:content url="https://blog.bsdserver.nl/content/images/2026/01/postfix-relay-docker.png" medium="image"/><content:encoded><![CDATA[<p>Servers, monitoring tools and applications all need to send mail: alerts, notifications, password resets. Configuring every one of them with credentials for an external mail service is a lot of moving parts, and a third-party service costs money and is hard to troubleshoot.</p>
<p>This post builds one SMTP relay with Docker Compose. Clients authenticate with SASL over STARTTLS, and the relay signs outgoing mail with DKIM and delivers it.</p>
<h2 id="why-an-smtp-relay">Why an SMTP relay? <a class="anchor" data-pagefind-ignore href="#why-an-smtp-relay" aria-label="Link to this section">#</a></h2>
<ul>
<li><strong>Full control</strong> over email routing, logging and security</li>
<li><strong>One place</strong> for authentication, DKIM signing and SPF, instead of per application</li>
<li><strong>Low cost</strong>: one small container, no per-message fees</li>
</ul>
<h3 id="when-to-use-it">When to use it <a class="anchor" data-pagefind-ignore href="#when-to-use-it" aria-label="Link to this section">#</a></h3>
<ul>
<li><strong>Use it</strong> for internal systems that send alerts and notifications, and when you control the DNS of the sending domain.</li>
<li><strong>Skip it</strong> for bulk or marketing mail, or when your hosting provider blocks outbound port 25. Deliverability then depends on IP reputation you have to build yourself; a mail service handles that for you.</li>
</ul>
<h2 id="how-it-works">How it works <a class="anchor" data-pagefind-ignore href="#how-it-works" aria-label="Link to this section">#</a></h2>
<table>
	<thead>
			<tr>
					<th>Component</th>
					<th>Runs on</th>
					<th>Job</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><code>postfix-relay</code> container</td>
					<td>Docker host</td>
					<td>Postfix: accepts mail on port 25 from authenticated clients, delivers it.</td>
			</tr>
			<tr>
					<td>OpenDKIM</td>
					<td>Same container</td>
					<td>Generates the DKIM keys, signs mail from the domains in <code>OPENDKIM_DOMAINS</code>.</td>
			</tr>
			<tr>
					<td>DNS</td>
					<td>Your DNS provider</td>
					<td>Publishes the DKIM public key and the SPF record, so receivers trust the mail.</td>
			</tr>
	</tbody>
</table>
<p>The flow: an application connects on port 25 → STARTTLS → authenticates with SASL → hands over the message → OpenDKIM signs it → Postfix delivers it → the receiving server checks DKIM and SPF in DNS.</p>
<h2 id="step-1-setting-up-the-docker-compose-file">Step 1: Setting Up the Docker Compose File <a class="anchor" data-pagefind-ignore href="#step-1-setting-up-the-docker-compose-file" aria-label="Link to this section">#</a></h2>
<p>The Compose file configures everything through environment variables. The image (<code>mwader/postfix-relay</code>) turns <code>POSTFIX_*</code> variables into Postfix settings.</p>
<table>
	<thead>
			<tr>
					<th>Variable</th>
					<th>What it does</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><code>SASL_Passwds</code></td>
					<td>Path to the file with SASL users and password hashes.</td>
			</tr>
			<tr>
					<td><code>POSTFIX_myhostname</code></td>
					<td>The name the relay announces; should match its DNS name and certificate.</td>
			</tr>
			<tr>
					<td><code>OPENDKIM_DOMAINS</code></td>
					<td>Sender domains to sign with DKIM (see Step 3).</td>
			</tr>
			<tr>
					<td><code>POSTFIX_smtpd_sasl_auth_enable</code>, <code>..._security_options=noanonymous</code></td>
					<td>Turn on SASL authentication; no anonymous logins.</td>
			</tr>
			<tr>
					<td><code>POSTFIX_smtpd_relay_restrictions=permit_sasl_authenticated,reject</code></td>
					<td>Only authenticated clients can relay. Everyone else is refused.</td>
			</tr>
			<tr>
					<td><code>POSTFIX_smtpd_tls_*</code></td>
					<td>Certificate and key for STARTTLS. <code>security_level=may</code> offers TLS; <code>auth_only=yes</code> offers AUTH only after STARTTLS.</td>
			</tr>
			<tr>
					<td><code>RSYSLOG_*</code></td>
					<td>Log to a file in <code>/var/log</code> and forward to a remote syslog server.</td>
			</tr>
	</tbody>
</table>
<p>Other settings:</p>
<ul>
<li><code>healthcheck</code>: marks the container unhealthy when port 25 stops accepting connections.</li>
<li><code>traefik-proxy</code> network and both volumes are <code>external</code>: they must exist before you start (Step 2).</li>
</ul>
<p>Create a file named <code>docker-compose.yml</code> in your project directory:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">services</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">smtp</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">image</span><span class="p">:</span><span class="w"> </span><span class="l">mwader/postfix-relay</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">container_name</span><span class="p">:</span><span class="w"> </span><span class="l">postfix-relay</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">restart</span><span class="p">:</span><span class="w"> </span><span class="l">always</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">environment</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">SASL_Passwds=/etc/postfix/sasl/sasl_passwds</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">POSTFIX_myhostname=smtp.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">OPENDKIM_DOMAINS=smtp.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">POSTFIX_smtpd_sasl_auth_enable=yes</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">POSTFIX_cyrus_sasl_config_path=/etc/postfix/sasl</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">POSTFIX_smtpd_sasl_security_options=noanonymous</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">POSTFIX_smtpd_relay_restrictions=permit_sasl_authenticated,reject</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">POSTFIX_smtpd_tls_cert_file=/etc/postfix/tls/cert.pem</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">POSTFIX_smtpd_tls_key_file=/etc/postfix/tls/key.pem</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">POSTFIX_smtpd_tls_security_level=may</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">POSTFIX_smtpd_tls_auth_only=yes</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">TZ=Europe/Amsterdam</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">RSYSLOG_LOG_TO_FILE=yes</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">RSYSLOG_TIMESTAMP=yes</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">RSYSLOG_REMOTE_HOST=syslog.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">RSYSLOG_REMOTE_PORT=514</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">volumes</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">./passwd_file/passwd_file:/etc/postfix/sasl/sasl_passwds</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">opendkim_keys:/etc/opendkim/keys</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">var_log:/var/log</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">./tls/cert.pem:/etc/postfix/tls/cert.pem:ro</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">./tls/key.pem:/etc/postfix/tls/key.pem:ro</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">ports</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="s2">&#34;25:25&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">networks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">traefik-proxy</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">healthcheck</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">test</span><span class="p">:</span><span class="w"> </span><span class="l">timeout 10s bash -c &#39;:&gt; /dev/tcp/127.0.0.1/25&#39; || exit 1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">interval</span><span class="p">:</span><span class="w"> </span><span class="l">10s</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">timeout</span><span class="p">:</span><span class="w"> </span><span class="l">5s</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">retries</span><span class="p">:</span><span class="w"> </span><span class="m">3</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">start_period</span><span class="p">:</span><span class="w"> </span><span class="l">90s</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">networks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">traefik-proxy</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">volumes</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">opendkim_keys</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">var_log</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="w">
</span></span></span></code></pre></div><h2 id="step-2-preparing-for-deployment">Step 2: Preparing for Deployment <a class="anchor" data-pagefind-ignore href="#step-2-preparing-for-deployment" aria-label="Link to this section">#</a></h2>
<p>Everything the Compose file refers to must exist before the first start: the password file, the volumes, the network and the certificate.</p>
<h3 id="create-required-directories">Create Required Directories <a class="anchor" data-pagefind-ignore href="#create-required-directories" aria-label="Link to this section">#</a></h3>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir -p passwd_file opendkim_keys var_log
</span></span></code></pre></div><h3 id="create-a-sasl-password-file">Create a SASL Password File <a class="anchor" data-pagefind-ignore href="#create-a-sasl-password-file" aria-label="Link to this section">#</a></h3>
<p>One line per user: <code>username:hash</code>. The image&rsquo;s own <code>mkpasswd</code> creates a SHA-512 hash, so the plain password is never stored. Run it again with another name to add users.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">echo</span> <span class="s2">&#34;myuser:&#34;</span><span class="sb">`</span>docker run --rm mwader/postfix-relay mkpasswd -m sha-512 <span class="s2">&#34;mypassword&#34;</span><span class="sb">`</span> &gt;&gt; passwd_file/passwd_file
</span></span></code></pre></div><h3 id="configure-volumes">Configure Volumes <a class="anchor" data-pagefind-ignore href="#configure-volumes" aria-label="Link to this section">#</a></h3>
<p>Named volumes keep the DKIM keys and logs across container rebuilds. Losing <code>opendkim_keys</code> means new keys and a new DNS record.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">docker volume create opendkim_keys
</span></span><span class="line"><span class="cl">docker volume create var_log
</span></span><span class="line"><span class="cl">mkdir -p ./sasl_passwd
</span></span></code></pre></div><h3 id="create-the-external-network">Create the External Network <a class="anchor" data-pagefind-ignore href="#create-the-external-network" aria-label="Link to this section">#</a></h3>
<p>The Compose file joins an existing <code>traefik-proxy</code> network. If it doesn&rsquo;t exist yet, <code>docker-compose up</code> stops with <code>network traefik-proxy declared as external, but could not be found</code>:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">docker network create traefik-proxy
</span></span></code></pre></div><h3 id="add-a-tls-certificate">Add a TLS Certificate <a class="anchor" data-pagefind-ignore href="#add-a-tls-certificate" aria-label="Link to this section">#</a></h3>
<p>The image doesn&rsquo;t encrypt client connections by default (<code>smtpd_tls_security_level=none</code>), so without a certificate the SASL password crosses the network in the clear. Put a certificate and key for <code>smtp.example.com</code> in <code>./tls/</code>; with <code>smtpd_tls_auth_only=yes</code>, AUTH is only offered after STARTTLS.</p>
<p>For a quick test a self-signed one will do:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir -p tls
</span></span><span class="line"><span class="cl">openssl req -x509 -newkey rsa:2048 -nodes -days <span class="m">365</span> -subj /CN<span class="o">=</span>smtp.example.com <span class="se">\
</span></span></span><span class="line"><span class="cl">  -keyout tls/key.pem -out tls/cert.pem
</span></span><span class="line"><span class="cl">chmod <span class="m">644</span> tls/*.pem
</span></span></code></pre></div><h2 id="step-3-dkim---enhancing-email-security">Step 3: DKIM - Enhancing Email Security <a class="anchor" data-pagefind-ignore href="#step-3-dkim---enhancing-email-security" aria-label="Link to this section">#</a></h2>
<p>DKIM signs each message with a private key; receivers check the signature against the public key in your DNS. Unsigned mail is more likely to land in spam.</p>
<p>When you start the container for the first time, it will generate DKIM keys. To add these to your DNS:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">docker <span class="nb">exec</span> postfix-relay sh -c <span class="s1">&#39;cat /etc/opendkim/keys/*/*.txt&#39;</span>
</span></span></code></pre></div><p>You&rsquo;ll see output like:</p>
<pre tabindex="0"><code>mail._domainkey.smtp.example.com. IN TXT ( &#34;v=DKIM1; h=sha256; k=rsa; &#34; &#34;p=PUBLIC_KEY_HERE&#34; )
</code></pre><p>Add this DNS record to your domain&rsquo;s DNS settings.</p>
<p><code>OPENDKIM_DOMAINS</code> decides what gets signed: only mail whose sender address is in a listed domain.</p>
<ul>
<li>With <code>smtp.example.com</code> listed, mail from <code>alerts@smtp.example.com</code> is signed, but mail from <code>alerts@example.com</code> goes out unsigned.</li>
<li>List the domains you actually send from (space-separated, e.g. <code>OPENDKIM_DOMAINS=example.com</code>).</li>
</ul>
<h3 id="spf---ensuring-reliable-email-delivery">SPF - Ensuring Reliable Email Delivery <a class="anchor" data-pagefind-ignore href="#spf---ensuring-reliable-email-delivery" aria-label="Link to this section">#</a></h3>
<p>SPF tells receivers which IP addresses may send mail for your domain. Add the following TXT record to your domain&rsquo;s DNS:</p>
<pre tabindex="0"><code>v=spf1 ip4:YOUR_SERVER_IP ~all
</code></pre><p>Replace <code>YOUR_SERVER_IP</code> with the IP address of your SMTP server. <code>~all</code> soft-fails mail from other addresses instead of rejecting it outright.</p>
<h2 id="step-4-launch-your-smtp-relay-server">Step 4: Launch Your SMTP Relay Server <a class="anchor" data-pagefind-ignore href="#step-4-launch-your-smtp-relay-server" aria-label="Link to this section">#</a></h2>
<p>Start the relay in the background. The first start generates the DKIM keys from Step 3.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">docker-compose up -d
</span></span></code></pre></div><h2 id="step-5-testing-your-smtp-relay">Step 5: Testing Your SMTP Relay <a class="anchor" data-pagefind-ignore href="#step-5-testing-your-smtp-relay" aria-label="Link to this section">#</a></h2>
<p>Test from a client machine the way your applications will use it: STARTTLS, then SASL authentication. <code>swaks</code> is ideal for this (<code>apt install swaks</code>). A plain <code>sendmail</code> on the Docker host would hand the message to the host&rsquo;s own MTA, not to the relay.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">swaks --server smtp.example.com --port <span class="m">25</span> --tls <span class="se">\
</span></span></span><span class="line"><span class="cl">  --auth PLAIN --auth-user myuser --auth-password mypassword <span class="se">\
</span></span></span><span class="line"><span class="cl">  --from alerts@smtp.example.com --to recipient@domain.com
</span></span></code></pre></div><p>What to expect:</p>
<ul>
<li><strong>With auth</strong>: <code>235 2.7.0 Authentication successful</code>, then <code>250 2.0.0 Ok: queued as ...</code>. The mail arrives with a DKIM signature.</li>
<li><strong>Without <code>--auth</code></strong>: refused with <code>554 5.7.1 &lt;recipient@domain.com&gt;: Recipient address rejected: Access denied</code>. That&rsquo;s <code>permit_sasl_authenticated,reject</code> doing its job.</li>
</ul>
<h2 id="troubleshooting">Troubleshooting <a class="anchor" data-pagefind-ignore href="#troubleshooting" aria-label="Link to this section">#</a></h2>
<table>
	<thead>
			<tr>
					<th>Symptom</th>
					<th>Cause / fix</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><code>network traefik-proxy declared as external, but could not be found</code></td>
					<td>Create the network first (Step 2).</td>
			</tr>
			<tr>
					<td>No AUTH offered by the server</td>
					<td>AUTH is only offered after STARTTLS; check the certificate files are mounted.</td>
			</tr>
			<tr>
					<td><code>554 5.7.1 ... Access denied</code></td>
					<td>The client did not authenticate.</td>
			</tr>
			<tr>
					<td>Mail arrives without a DKIM signature</td>
					<td>The sender domain is not in <code>OPENDKIM_DOMAINS</code>.</td>
			</tr>
	</tbody>
</table>
<h2 id="security-considerations">Security Considerations <a class="anchor" data-pagefind-ignore href="#security-considerations" aria-label="Link to this section">#</a></h2>
<ul>
<li><strong>Never an open relay</strong>: keep <code>permit_sasl_authenticated,reject</code>. Test the unauthenticated case after every change.</li>
<li><strong>TLS before AUTH</strong>: <code>smtpd_tls_auth_only=yes</code> keeps passwords off the wire in the clear. Use a real certificate in production.</li>
<li><strong>Limit port 25</strong>: if only internal systems send mail, firewall port 25 to those networks.</li>
<li><strong>Protect the DKIM keys</strong>: whoever has them can sign mail as your domain.</li>
</ul>
<h2 id="automate-it">Automate it <a class="anchor" data-pagefind-ignore href="#automate-it" aria-label="Link to this section">#</a></h2>
<p>The Ansible roles and Terraform code that build this setup are on GitHub:
<a href="https://github.com/pderuiter/blog-postfix-relay-docker" rel="noopener">pderuiter/blog-postfix-relay-docker</a>. It creates an Ubuntu 24.04 VM, installs Docker, and deploys this relay with SASL users, the TLS certificate and DKIM. Run <code>terraform apply</code>, then <code>ansible-playbook site.yml</code>; the last task prints the DKIM record to publish.</p>
<h2 id="conclusion">Conclusion <a class="anchor" data-pagefind-ignore href="#conclusion" aria-label="Link to this section">#</a></h2>
<p>You now have one SMTP relay for your infrastructure: authenticated, encrypted and DKIM-signed. Because it is a Compose file, deploying another one is a repeatable, predictable process.</p>
]]></content:encoded></item></channel></rss>