What is planned regarding the problem with easy managing the default vdelivermail behaviour PLUS forwarding? The need for two config files is a very big problem I think in this case. Consider the three relevant cases: 1. Default maildir delivery: No .qmail files are needed. 2. Forwarding: Either - domain/.qmail-user - domain/user/.qmail (suggested method by documentation and other software, and general qmail approach as well) is good. 3. Default maildir delivery + forwarding Now I have to move ALL forwards from domain/user/.qmail to domain/.qmail-user where I also must care for filename conversions due to the . characters in filenames. I don't know what the case with dash-ended localparts is. I also have to copy the content of .qmail-default. Therefore I must do a workaround, which is not even managed by qmailadmin and other software I think, and definitely not a preferable approach. Using a single configuration file in domain/user makes it much more manageable, and I don't have to look at possible stray .qmail-user files in the domain directory. If I need to use domain/.qmail-user then domain/user/.qmail is needless, since a superset of its functionality can be provided with domain/.qmail-user however these are much less manageable. I suggest that at least the line ./Maildir/ should be interpreted by vdelivermail and it should act for it as its default behaviour without any forwards, but it look at the other instructions in the .qmail file as well, enabling it to solve the problem I outlined . It does not need a big change, does not provide conflicts with quota checking and mail-retrieving as delivering to arbitrary maildirs would. Regards, Robert Varga
