On 09/15/2018 08:14 AM, Zhao Difei wrote:
> It's been more than 2 years without resolution. I'm sure a lot of mail
> server maintainers are using local package. Resolve this bug seems
> trival to me, maybe just re-add the courier-maildrop package?
Please check all the bugs closed by the removal
Hey fellas,
It's been more than 2 years without resolution. I'm sure a lot of mail
server maintainers are using local package. Resolve this bug seems trival
to me, maybe just re-add the courier-maildrop package?
Cheers,
Difei
Hi Markus,
we are using courier-mta on Stretch too and actually we have
problems when using DEFAULTDELIVERY="| /usr/bin/maildrop -w90" in the
configuration. When using the following Workaround
DEFAULTDELIVERY='| /usr/bin/maildrop -w 90 -V 9 -d "${RECIPIENT}"'
it's working as expected.
It
Control: merge 822683 822446
I'm not quite sure how to fix this, yet, but I ran into the very same issue.
It seems the difference is not in Debian patches, but depends on the
HAVE_COURIER macro. I'll check with the maildrop maintainer.
Kind Regards
Markus Wanner
signature.asc
Description:
Control: reassign -1 src:courier
Hi,
Excuse me for slow response but this is not bug for maildrop but for
src:courier.
There were intentional differences between maildrop packaged in Debian.
I maintain one intended for independent use and have several historical
divergence from the upstream.
Package: maildrop
Version: 2.8.3-0.1
Severity: important
Greetings,
(I filed a bug to courier source previously but I believe it belongs to
here).
The removal of the courier-maildrop package breaks the courier MTA
utilizing the virtual accounts tools. The courier version of maildrop
will import
6 matches
Mail list logo