<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exim on The Gnu Pit</title><link>https://gnupit.net/exim/</link><description>Recent content in Exim on The Gnu Pit</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 12 Aug 2025 07:12:15 -0500</lastBuildDate><atom:link href="https://gnupit.net/exim/index.xml" rel="self" type="application/rss+xml"/><item><title>Upgrading to Debian 13 Trixie</title><link>https://gnupit.net/posts/upgrading_to_debian13/</link><pubDate>Tue, 12 Aug 2025 07:12:15 -0500</pubDate><guid>https://gnupit.net/posts/upgrading_to_debian13/</guid><description>&lt;p&gt;Ah, the trials and tribulations of upgrading Debian 12 Bookworm to Debian 13 Trixie! I learned a valuable lesson this weekend with the update - always read the apt listchanges email. Always.&lt;/p&gt;
&lt;p&gt;The upgrade itself went smoothly with no errors during the packages upgrading/installing. I run three main services on my server - nginx, exim, and dovecot. On reboot, all three had issues with the upgraded packages.&lt;/p&gt;
&lt;h3 id="nginx"&gt;nginx&lt;/h3&gt;
&lt;p&gt;I received the following error in my nginx error.log:&lt;/p&gt;</description></item><item><title>Let's Encypt SSL Certificates with Exim, Dovecot &amp; NGINX</title><link>https://gnupit.net/posts/exim_dovecot_nginx_letsencrypt/</link><pubDate>Fri, 19 May 2017 14:32:24 -0500</pubDate><guid>https://gnupit.net/posts/exim_dovecot_nginx_letsencrypt/</guid><description>&lt;p&gt;I ran into two issues when setting up Let&amp;rsquo;s Encrypt SSL certificates on two of my servers - permission issues for Exim and the certbot cron job supplied by the package doesn&amp;rsquo;t handle the renew very well for nginx, exim or dovecot.&lt;/p&gt;
&lt;h3 id="resolving-exims-permission-problems"&gt;Resolving Exim&amp;rsquo;s Permission Problems&lt;/h3&gt;
&lt;p&gt;1. Create a new group. I named it sslcerts. Add the exim user to that group. If you&amp;rsquo;re not using Debian, adjust the user in the command below.&lt;/p&gt;</description></item><item><title>Possible Android Botnet and Yahoo! Mail</title><link>https://gnupit.net/posts/spam_android_yahoo/</link><pubDate>Mon, 09 Jul 2012 21:43:24 -0500</pubDate><guid>https://gnupit.net/posts/spam_android_yahoo/</guid><description>&lt;p&gt;I&amp;rsquo;ve read a number of articles over the past few days about the possible Android botnet and Yahoo! mail. No consensus yet but that&amp;rsquo;s not necessary to stop the spam at the server level, at least in my case. Of the spam I received so far, these characteristics stand out:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Only one of my mail accounts is receiving the spam. It&amp;rsquo;s not an account that usually receives spam. My long-time mail addresses that seem to have made it to most of the spam lists don&amp;rsquo;t get this spam. Makes me wonder where they picked up this address from.&lt;/p&gt;</description></item></channel></rss>