-----Ursprüngliche Nachricht----- Von: qu...@mydiax.ch [mailto:qu...@mydiax.ch] Gesendet: Freitag, 13. Dezember 2002 14:56 An: cour...@lists.sourceforge.net Betreff: [maildropl] Maildrop and Qmail-Ldap, problems and questions

Greetings,

We have the maildrop running as MDA for the local virtual users with qmail-ldap. The only reason why we want to use it is server side filtering.

So far it works, except 2 problems:

1) Maildrop only accepts one ldap field as search_method / mail_attr, this brings a problem that we can only define "mail" or "mailAlternateAddress" as search criteria. So, having one account with primary and many alternative addresses, as qmail-local allows does not work.

2) Maildrop seems to be unable to understand the "Catchall" addresses, which catch all mails to undefined addresses in some domain.

3) Maildrop does not seem to support automatic home / maildir make as qmail-local does.

The problems one and two can be "walked around" by creating dummy forwardonly accounts which incorporate Alternates or catchall and forward mails to single account maildrop knows how to handle, but this is not a perfect solution :( Is there a way to make maildrop function as qmail-local ?

Is there a walkaround or solution for problem three ?

Also:

I have not studied the maildrop filtering language in detail yet, but it seems as since our mail for virtual accounts is stored under one uid/gid, the users could write the filter rules, which could potentialy do anything in the maildirs of the other users. Is that true ? And if yes, is there a way to avoid/limit it (Besides making every user have his own UID/GID, which kind of defies the idea of Virtual Mail system).

Best Regards and thanks for hints / answers,