I'm running patch release 20031001 using the RCPTCHECK option in my
tcp.cdb. I do this to cut down on bounces generated by delivery attempts
to unknown addresses. I've also defined an account that has a
user-catchall address defined in mailAlternateAddress. I do this because
I want the user to be able to control other extension addresses end
delivery options via dot-qmail files.
However it seems that the -catchall extension allows user-ANYTHING
through to this user again, making the RCPTCHECK option not do what I
want to for him. For example, in his home directory are files
.qmail-spam, .qmail-ml, and .qmail-sun. But thanks to the catchall
extension any addresses of the form user-extension are accepted for
delivery and then later bounced with #5.1.1: no mailbox here by that
name, if a .qmail file is not found for the extension. This user account
has qmailDotMode set to dotonly.
I assume qmail-ldap/RCPTCHECK doesn't verify the extension address if
delivery is enabled via a dot-qmail file by design..? Is there a way to
receive the benefits of RCPTCHECK while maintaining the control of
.qmail delivery instructions at the same time?
Is the answer to add only the addresses to mailAlternateAddresses for
which I have .qmail files for the user set up, and do away with
[EMAIL PROTECTED] Is there a setting of qmailDotMode that is
better suited for this?
TIA
DS
