Skip to main content

Courier IMAP - vpopmail troubles

I like the qmail/vpopmail solution as a email server a lot and use it in lots of places. Usually there is only one domain, but in one special case I had to create more than one. I also use courier-imap as imap/pop3 daemon because of its support for vpopmail.
So last week I went to create a new virtual domain on this site and at first all seemed to work fine, but after a while users on the new virtual domains reported login errors.
After some googling I searched the vpopmail mailing lists and found the following posts:

Since I usually install qmail on SuSE linux systems I wanted to modify the rpm of courier-imap (version 3.0.8) so that it would also build the needed authvchkpw . This turned out not to be easy and required a modification to the spec file that I am attaching here:

--- courier-imap.spec.orig 2005-03-21 09:51:21.000000000 +0100
+++ courier-imap.spec 2005-03-22 16:45:34.544423142 +0100
@@ -317,6 +317,11 @@

%{__chmod} 555 $RPM_BUILD_ROOT%{_datadir}/sysconftool-rpmupgrade

+# (Umberto, Prometeo SRL 2005)
+# Make sure authvchkpw gets copied int libexec/authlib
+cp -f authlib/authvchkpw $RPM_BUILD_ROOT%{_libexecdir}/authlib
# Check if authdaemond was installed, make sure to include authdaemon
# directory
@@ -469,6 +474,7 @@

%dir %{_libexecdir}
%dir %{_libexecdir}/authlib
+%attr(755, root, root) %{_libexecdir}/authlib/authvchkpw
%dir %{_sysconfdir}
%dir %{_sysconfdir}/shared
%dir %{_sysconfdir}/shared.tmp
To use it simply extract the courier-imap.spec file in rpm/SPECS and patch it. Then move the courier imap sources in rpm/SOURCES and build normally.
These are the directions for building courier rpms:



Popular posts from this blog

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

A not so short guide to ZFS on Linux

Updated Oct 16 2013: shadow copies, memory settings and links for further learning.
Updated Nov 15 2013: shadow copies example, samba tuning.

Unless you've been living under a rock you should have by now heard many stories about how awesome ZFS is and the many ways it can help with saving your bacon.

The downside is that ZFS is not available (natively) for Linux because the CDDL license under which it is released is incompatible with the GPL. Assuming you are not interested in converting to one of the many Illumos distributions or FreeBSD this guide might serve you as a starting point if you are attracted  by ZFS features but are reluctant to try it out on production systems.

Basically in this post I note down both the tought process and the actual commands for implementing a fileserver for a small office. The fileserver will run as a virtual machine in a large ESXi host and use ZFS as the filesystem for shared data.