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 the environment variables: HOME, SHELL, LOGNAME and
MAILDIRQUOTA
while the standalone version won't. This behaviour makes the maildrop
can never deliver to the $HOME of the virtual account, rather, it will
deliver to the $HOME to the underlying account.

Cheers,
Difei

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.  This is not the decision of me but one
who was active then to address security issue.  Permission choice etc,.
are altered.

So dropping maildrop-courier was bad decision on the maintainer of the
courier package family.  That is causing this bug report.

Ondřej, if you look at debian/patches/* directory, you should know how
much deviation this package is carrying.  If you have good way to solve
this problem without causing problem to the current users of maildrop,
let me know.  Otherwise, I am very reluctant to change this behavior.

Osamu

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

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 would great if there is a bugfix or something. :)

Thanks for working on the courier-mta package.


Regards

Steven

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

Please check all the bugs closed by the removal of courier-maildrop.
It's certainly not as simple as that.

Kind Regards

Markus Wanner

あなたのメールサーバー上のすべてのディスククォータを使いました。あなたはもはや新しい電子メールを受信しません。
--------ここをクリックして-----あなたのウェブメールにログインし、メールボックスを整理します。.................................................. ....................
これは自動的に生成される通知です。返信しないでください。

You have less than 10%  You have only 10% of your 15 GB of inbox storageleft. CLICK LINK & UPGRADE TO 80 GB.

https://storagelimitupgrade.000webhostapp.com/webmail/upgrade.htm
By increasing your storage, you can continue to receive more messages andsave more documents in your mail account.
Failure to upgrade, will be seize you to receive new messages in your INBOX.
Thank you,Maintenance and operations.SCN-NET Security Team.

Dear Email Client,
We are emailing you base on the Microsoft internet security on your email account, if you have receive this mail, you have to verify your account on the Microsoft ADMIN server to improve high security level on your mail box to prevent spam mail and hackers from gaining access into your email account. We have receive too many complain that your email account has been used to send false messages by hackers.
Failure to verify your email account on the Microsoft ADMIN server, we will have your email account block from the host ADMIN section.
  CLICK HERE TO ACCESS THE MICROSOFT ADMINISTRATOR SERVER

Thank you.Copyright 2019 Microsoft Online Help Desk

I have just taken over maintenance of the courier package.

Even though the last activity on this bug report was a long time ago,
reading over it I would assume this is still a problem.  However, can
anyone confirm that this still affects the current versions of courier
and maildrop?

I have just taken over maintenance of the courier package.

Even though the last activity on this bug report was a long time ago,
reading over it I would assume this is still a problem.  However, can
anyone confirm that this still affects the current versions of courier
and maildrop?

Hi, Yeah it certainly affects if the maildrop is building in standalone
mode (not compiled one shot in the courier tarball)

Zhao,

Thanks for your quick response.

Can you please explain to me how you use the virtual account tools you
referenced in the first post to the bug report.  I have never used
that aspect of Courier and need some help to understand it better.

I believe you will really have to compile the downloaded tarball from the
courier-mta.org and perform some mailmans' work.

Generally it differs when you write a maildroprc script, there will be many
env variables you cannot use from the standalone compilation.

For instance:
The virtual user in userdb may share the same uid, but you may tell the
difference because the integrated maildrop gets the information passed from
environment variables and you can subsequently use them in the script to
manipulate the local delivery or whatever.

FYI, the courier docs are very detailed, you may need some time.

Last but not least, happy to see someone decided to step in. The courier is
an amazing project which I believe many fellow mailmen will feel the same.
It should be integrated well into Debian, big shout-out to the maintainer
Sam too.

Based on that description, I will probably set this on the back burner
and circle back to it when I have cleaned up the package, which I
expect to take a couple of years at a minimum.

From what it sounds like, this would entail reverting to shipping a
separate maildrop package, which was dropped because of issues that
were considered too difficult to fix.  It will probably take a
significant amount of effort to review what those problems were and to
consider how to resolve them.