<?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/">
  <channel>
    <title>E-Mail on C&amp;CZ News</title>
    <link>https://cncz.science.ru.nl/tags/e-mail/</link>
    <description>Recent content in E-Mail on C&amp;CZ News</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>postmaster</managingEditor>
    <lastBuildDate>Thu, 12 Mar 2026 00:00:00 +0100</lastBuildDate><atom:link href="https://cncz.science.ru.nl/tags/e-mail/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Science Mail Technical Update</title>
      <link>https://cncz.science.ru.nl/news/2026-03-12_mail-update2/</link>
      <pubDate>Thu, 12 Mar 2026 00:00:00 +0100</pubDate>
      <author>Arnoud Thörig</author>
      <guid>https://cncz.science.ru.nl/news/2026-03-12_mail-update2/</guid>
      <description>&lt;h3 id=&#34;technical-update-for-maildomain-dns-administrators&#34;&gt;Technical update for mail‑domain DNS administrators&lt;/h3&gt;
&lt;h4 id=&#34;what-and-why-we-are-doing-this&#34;&gt;What and why we are doing this&lt;/h4&gt;
&lt;p&gt;With the new setup we are renaming our mail‑component servers so that their
names reflect the function they perform in the mail chain.&lt;/p&gt;
&lt;p&gt;This change has &lt;strong&gt;no impact on end users&lt;/strong&gt;, but it makes troubleshooting and
future feature implementation easier because we can immediately identify the
machine involved.&lt;/p&gt;
&lt;h4 id=&#34;first-step&#34;&gt;First step&lt;/h4&gt;
&lt;p&gt;We have renamed &lt;code&gt;mx3&lt;/code&gt; to &lt;code&gt;inboundmx3&lt;/code&gt;. Because this is essentially only a DNS
change, we have also updated all MX records we manage. Domains for which we
provide mail but do not control the DNS must be updated by their own
administrators.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Science Mail Update</title>
      <link>https://cncz.science.ru.nl/news/2026-02-09_mail-update1/</link>
      <pubDate>Mon, 09 Feb 2026 00:00:00 +0100</pubDate>
      <author>Arnoud Thörig</author>
      <guid>https://cncz.science.ru.nl/news/2026-02-09_mail-update1/</guid>
      <description>&lt;h3 id=&#34;enhanced-email-security&#34;&gt;Enhanced Email Security&lt;/h3&gt;
&lt;p&gt;We are pleased to announce we have completed the first step in the update to our email system. This will improve the security and reliability of your mail handling. As part of this upgrade, we have introduced new software at the start of our email flow (on the inbound MX servers). This advanced system now evaluates incoming emails to determine if they are legitimate.&lt;/p&gt;
&lt;p&gt;If an email fails to meet the required standards or appears very suspicious, it will be blocked at the entry point, in accordance with RFC guidelines for mail transport. This is a crucial first step toward creating a safer and more secure email environment for everyone.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Science Mail Announcement</title>
      <link>https://cncz.science.ru.nl/news/2026-01-26_mail-announcement/</link>
      <pubDate>Mon, 26 Jan 2026 00:00:00 +0100</pubDate>
      <author>Arnoud Thörig</author>
      <guid>https://cncz.science.ru.nl/news/2026-01-26_mail-announcement/</guid>
      <description>&lt;p&gt;C&amp;amp;CZ was the first to implement e-mail (@sci.kun.nl) at the KUN (Katholieke Universiteit Nijmegen), some 35 years ago. Some configurations we have used since then have not kept up with the changing landscape of e-mail implementations worldwide. In Dutch there&amp;rsquo;s a saying for this: &amp;ldquo;De wet van de remmende voorsprong&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;One of the major things that have changed over time is dealing with SPAM. For instance, there are now protocols that major e-mail players require and therefore became the de facto standard for email communication.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
