3 messages in net.sourceforge.lists.courier-maildrop[maildropl] maildrop with sendmail
FromSent OnAttachments
Mark NienbergJun 5, 2006 2:13 pm 
Devin RubiaJun 6, 2006 6:03 am 
Mark NienbergJun 6, 2006 11:30 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] maildrop with sendmailActions...
From:Mark Nienberg (gma@tippingmar.com)
Date:Jun 5, 2006 2:13:51 pm
List:net.sourceforge.lists.courier-maildrop

I'm testing maildrop as a replacement for procmail on a Fedora Core 5 server with sendmail 8.13.6.

I used rpmbuild -ta maildrop-2.0.2.tar.bz2 and then installed the resulting rpm.

In sendmail.mc I have this as recommended in the sendmail documentation: FEATURE(`local_procmail', `/usr/bin/maildrop', `maildrop -d $u')dnl

My /etc/maildroprc is as follows:

SHELL="/bin/bash" logfile "/var/log/maildrop.log" VERBOSE="4" if (/^Subject: {Spam?/) { exception { to "$HOME/Maildir/.Spam/" } } else { to "$HOME/Maildir/" }

In the maillog file I get this:

Jun 5 12:02:13 tesla sendmail[11290]: k55J2CAV011289: to=<ma@example.com>, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=30674, dsn=4.0.0, stat=Deferred: local mailer (/usr/bin/maildrop) exited with EX_TEMPFAIL

In the INSTALL file it says that I can fix this by compiling with --enable-restrict-trusted=0

However, when I look in the maildrop.spec file I see (I added linebreaks for clarity):

%configure --with-devel --enable-userdb --enable-maildirquota --enable-syslog=1 --enable-trusted-users='root mail daemon postmaster qmaild mmdf' --enable-restrict-trusted=0 --enable-sendmail=/usr/sbin/sendmail

So it appears that the --enable-restrict-trusted=0 is already being used, as is --enable-syslog=1, which is a good thing. Is there another cause for this and another fix?