<?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>Email on Keldo.uk</title>
    <link>https://keldo.uk/tags/email/</link>
    <description>Recent content in Email on Keldo.uk</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 16 Jan 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://keldo.uk/tags/email/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Mail Server Down</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mail-server-down/</link>
      <pubDate>Thu, 16 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mail-server-down/</guid>
      <description>&lt;p&gt;It started when i tired to set up my emails on Thunderbird mail on arch I noticed it wouldn&amp;rsquo;t connect. I checked the logs and found &amp;ldquo;2025-01-16 21:04:11,919 WARN exited: amavis (exit status 1; not expected)&amp;rdquo; I fixed this relatively quickly by removing &amp;ldquo;amavisd.pid&amp;rdquo;. After this it booted but I still couldn&amp;rsquo;t connect.&lt;/p&gt;
&lt;p&gt;I tracked this down by using dig and whats my ip to see that the dns record was wrong. I fixed this by switching to a cname record set to @ so i only need 1 ddns setup. This finally fixed it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Docker Mailserver</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/docker-mailserver/</link>
      <pubDate>Fri, 22 Nov 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/docker-mailserver/</guid>
      <description>&lt;p&gt;Ever since I setup mailcow I have been annoyed that it runs with docker volumes and updates with a script. This makes it imposible to run how I want. I feel the main benefit of docker should be all the files needed are backed up and I can use the docker compose file to spin the container up anywhere.&lt;/p&gt;
&lt;p&gt;I have tried may times to fix these problems in mailcow and have always failed. So I finally gave up with mailcow and started looking at other options. I quite quickly found docker mailserver as my main option. I don&amp;rsquo;t know if I didn&amp;rsquo;t see it the first time round or if I was scared of by the lack of a GUI. What ever the case now I am happy to use the command line for everything.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Broken mailcow</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/broken-mailcow/</link>
      <pubDate>Thu, 30 May 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/broken-mailcow/</guid>
      <description>&lt;p&gt;I began by trying to move my mailcow install from running on docker volumes to storing data on my nas. I started copying the files however after around the 5th volume I remembered the continers were still online. After I continued even finding a copy of the docker compose.&lt;/p&gt;
&lt;p&gt;However when I ran the compose I got serveral errors about mysql. I realised I had corrupted the mysql database. I tried several edits to the mysql files and failed. After that I went to launch the old copy and realised that was corrupted as well.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mailcow ssl</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mailcow-ssl/</link>
      <pubDate>Sat, 13 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mailcow-ssl/</guid>
      <description>&lt;p&gt;The first thing I noticed was wrong was that my Iphone was giving me a pop up telling me it could verify the identity of mail.keldo.uk. My first though was that the ssl cert had expired but as far as I knew Mailcow should automaticly refresh the cert. Luckily it was easy to debug as Mailcow has a nice selection of logs and I just open the acme logs and Imedialty saw the issue &amp;ldquo;mail.keldo.uk - Found AAAA record for mail.keldo.uk: 2a00:23c7:82c2:6401:be24:11ff:fe6d:10fa - skipping A record check&amp;rdquo; was apearing every hour. I setup ipv6 records when I set up mailcow however since I have a dynamic IP and haven&amp;rsquo;t set up a ddns for ipv6 it was seeing ipv6 skiping ipv4 and then seeing the ipv6 didn&amp;rsquo;t match. The simple solution was I just removed the ipv6 record and then the next hour it was fixed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mailcow Install</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mailcow-install/</link>
      <pubDate>Sat, 13 Jan 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mailcow-install/</guid>
      <description>&lt;p&gt;I decided I wanted to be able to get emails from my services as that is the mail method most of them support. For my mail server i decided to use mailcow rather than try to stitch together my own group of programs. The install was easy with no errors by simply just using a Docker compose file. Its smtp work fine with TrueNAS, Pterodactyl, Nextcloud, Proxmox and Passbolt however i could not get it working with Mealie.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
