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:

http://www.mail-archive.com/vchkpw@inter7.com/msg09933.html
http://www.mail-archive.com/vchkpw@inter7.com/msg09943.html

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:
http://www.courier-mta.org/FAQ.html#rpm

Cheers,
Umberto
Labels:

Comments

Post a Comment

Popular posts from this blog

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post. Btw: the recovery, depending on db size and disk speed, is going to take long. The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux. The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking. Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd in
Post a Comment
Read more

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.
1 comment
Read more

How to automatically import a ZFS pool built on top of iSCSI devices with systemd

When using ZFS on top of iSCSI devices one needs to deal with the fact that iSCSI devices usually appear late in the boot process. ZFS on the other hand is loaded early and the iSCSI devices are not present at the time ZFS scans available devices for pools to import. This means that not all ZFS pools might be imported after the system has completed boot, even if the underlying devices are present and functional. A quick and dirty solution would be to run  zpool import <poolname> after boot, either manually or from cron. A better, more elegant solution is instead to hook into systemd events and trigger zpool import as soon as the devices are created.
Post a Comment
Read more