The mail-mta/courier ebuild performs some (correct actions) if the mysql USE flag is set. However, it does not add MySQL support to the maildrop it builds. The mail-filter/maildrop ebuld add the correct configuration flags to the the maildrop package. use mysql \ && myconf="${myconf} --enable-maildropmysql \ --with-mysqlconfig=/etc/maildrop/maildropmysql.cf" \ || myconf="${myconf} --disable-maildropmysql" Reproducible: Always Steps to Reproduce: 1. 2. 3. The maildrop from mail-mta/courier has special behavior (see below), so we just can't overwrite it with mail-filter/maildrop. In fact, we should be prevented from doing so. Excerpt from http://www.courier-mta.org/?maildropfilter.html: There's one exception to this rule which applies to the version of maildrop that comes with the Courier Mail Server. . . .
Mass re-assign, seems like mail-mta/courier needs a maintainer.
Can I get a little bit more info on this bug please? What the actual issue is? The symptoms it displays, etc.
maildrop from the courier-mta package is used with the -m/-M switch, for embedded mode, also courier uses -d to indicate the recepient for any message. however, the recepient for virtual (alas mysql) accounts cannot be found, if maildrop has no mysql-support. we could use some way to have maildrop of the courier-package acknowledge the mysql-useflag and provide the same support for mysql-based virtual accounts as the lone maildrop-package. hope this about summarizes it. feel free to add if you can, rob :)
