> I think you were running an ancient version of maildrop, from Courier 0.47.
>
> The current version of maildrop only checks for world writable permissions
> on the home directory. The mailfilter file still cannot have group and
> world permissions of any kind.
Aha! Thank you. That's just the datum I was looking for... the rules of
the permissions game *have* changed in newer Maildrop versions. Excellent!
This leaves me with at least three workable solutions - patch the source
for the 0.47-based maildrop I have here, or switch to the 0.51 Debian
package currently being tested, or pull down a current Courier/Maildrop
source distribution and build it myself. I'll look 'em all over and
try to figure out what's the best long-term solution.
At this point, I think my rcptfilter problems are pretty much resolved.
They turned out to be due to a combination of three factors, at least
one of which was the me-being-stupid I had anticipated:
[1] When reading the install documentation I'd missed the point of
mapping '.' to ':' when setting up filters for aliases. As a result,
when I mailed to the "[EMAIL PROTECTED]" alias, maildrop wasn't locating
the filter file. Easily fixed by renaming the file.
[2] When testing maildrop manually, I failed to pass in the correct HOME
environment variable for the alias-user - I wasn't emulating Courier's
back-door method of specifying the search location. Easily corrected,
and my manual tests of maildrop in delivery mode work just as they
should. This let me figure out the me-stupid [1] problem.
[3] The alias's filter wasn't being executed due to Maildrop's unwillingness
to allow the user's home directory to have world- or group-read.
Problem understood, several solutions possible.
I've been able to port my rcptfilter/smtpfilter scripts over from my old
heavily-patched qmail configuration without much trouble at all. Some
useful simplifications will be possible e.g. I can now depend on Courier's
esmtpd to perform the necessary SPF checks, rather than having to have
the rcptfilter script "shell out" to a separate query program.
Updating my auto-whitelister (which automagically whitelists any email
address to which I send email, based on the MTA's mail logs) to parse
Courier's logs in addition to qmail's should be no trouble at all.
Courier is looking better and better, and it's very comforting to be moving
to an MTA which is being actively maintained!
Thanks again for the assist!
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
