I installed a 0.42.2 version alongside the 0.40.1 to see if an updated version would be my answer, but I'm seeing the same behavior. So back to 0.40.1....

Is there a way to trace the "submit" module so that I can see if maildrop is being called and if so, which file(s) it's looking for? /var/log/maillog doesn't seem to have any mention of maildrop at all, and I set TCPDOPTS in /etc/courier/esmtpd to "-stderr=/var/log/maillog.err -stderrlogger=/usr/lib/courier/sbin/courierlogger -noidentlookup -nodnslookup" -- no /var/log/maillog.err file even gets created when the 'cjm' user receives an email. The /var/log/maillog file shows (I subbed "$" vars for actual names):

Jul 17 11:13:25 $HOSTNAME courierd: started,id=00018451.3F16E745.0000089C,from=<$US...@cox.net>,module=local,host=cjm!!503!503!/home/cjm!!,addr=<cjm> Jul 17 11:13:25 $HOSTNAME courierlocal: id=00018451.3F16E745.0000089C,from=<$US...@cox.net>,addr=<cjm@$FQDN_OF_HOSTNAME>,size=712,success: Message delivered.

any way to increase the verbosity of logging here? I can't seem to find that in the man pages either.

I modified /etc/courier/enablefiltering to read:

esmtp local

since the "module=local" term appeared in the log entry. But that didn't help either.

I'm thinking that the maildrop command (as passed by courier) might not be using the "rcptfilter" filename but "rcptfilter-ext" instead. I tried using "rcptfilter-cjm" which is the system account name, and I'm addressing the email to "cjm@$HOSTNAME" so there should be no domain/alias confusion, but it's still not working.

If I could see the exact 'maildrop' command courier is using (if it's using it at all), I can adjust my ".mailfilters" directory accordingly.

Many maildrop options are not allowed in embedded mode, including 'log' and 'logfile' so it looks like I need to trace this from this "submit" module?

Anyone know how to trace maildrop in embedded mode?

Thanks,

CJM