<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postfix on ads' corner</title><link>https://andreas.scherbaum.la/tags/postfix/</link><description>Recent content in Postfix on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 07 Aug 2024 00:00:00 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/postfix/index.xml" rel="self" type="application/rss+xml"/><item><title>warning: btree:/var/lib/postfix/smtp_scache is unavailable. unsupported dictionary type: btree</title><link>https://andreas.scherbaum.la/post/2024-08-07_warning-btree-var-lib-postfix-smtp_scache-is-unavailable-unsupported-dictionary-type-btree/</link><pubDate>Wed, 07 Aug 2024 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-08-07_warning-btree-var-lib-postfix-smtp_scache-is-unavailable-unsupported-dictionary-type-btree/</guid><description>&lt;p&gt;Upgraded a server, and moved it to &lt;em&gt;Arch Linux&lt;/em&gt;. And along the way the &lt;em&gt;Postfix&lt;/em&gt; version was also upgraded. Suddenly there is a warning in the logfile: &lt;code&gt;warning: btree:/var/lib/postfix/smtp_scache is unavailable. unsupported dictionary type: btree&lt;/code&gt;. Turns out that is easy to fix.&lt;/p&gt;</description></item><item><title>Install Telegraf using Ansible</title><link>https://andreas.scherbaum.la/post/2020-06-24_install-telegraf-using-ansible/</link><pubDate>Wed, 24 Jun 2020 18:56:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2020-06-24_install-telegraf-using-ansible/</guid><description>&lt;p&gt;I have an &lt;a href="https://www.influxdata.com/products/influxdb-overview/"&gt;InfluxDB&lt;/a&gt; up and &lt;a href="https://andreas.scherbaum.la/post/2020-06-21_move-influxdb-data-directory-to-a-sdcard/"&gt;running&lt;/a&gt; in my network, and decided to monitor all (well, all possible - the &lt;em&gt;QNAP&lt;/em&gt; seems to be a problem) devices. That&amp;rsquo;s quite easy to do by installing &lt;a href="https://www.influxdata.com/time-series-platform/telegraf/"&gt;Telegraf&lt;/a&gt; as a server agent, and add some configuration. Everything is deployed using &lt;a href="https://www.ansible.com/"&gt;Ansible&lt;/a&gt;, so I can re-use the same &lt;a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks.html"&gt;Playbook&lt;/a&gt; for many devices.&lt;/p&gt;&#10;&lt;p&gt;Let&amp;rsquo;s assume I have a laptop which I want to monitor. The hostname is &lt;code&gt;sunlight&lt;/code&gt; (it&amp;rsquo;s not, I&amp;rsquo;m just using this as an example).&lt;/p&gt;</description></item><item><title>Cron mails from root@localhost</title><link>https://andreas.scherbaum.la/post/2007-09-07_cron-mails-from-rootlocalhost/</link><pubDate>Fri, 07 Sep 2007 13:55:48 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2007-09-07_cron-mails-from-rootlocalhost/</guid><description>&lt;p&gt;If your &lt;code&gt;cron&lt;/code&gt; keeps sending mails from &lt;code&gt;root@localhost&lt;/code&gt; (which is bad, if the mails are forwarded to another system), check your mailserver settings. In &lt;a href="https://www.postfix.org/"&gt;Postfix&lt;/a&gt;, your &lt;a href="https://www.postfix.org/postconf.5.html#myhostname"&gt;$myhostname&lt;/a&gt; setting should point to an existing and valid &lt;code&gt;domainname&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>