Everything is broken (Finish refactoring Mailpile)

[BjarniRunar]

As stated in the current README, the Mailpile code base is in the middle of being refactored. This bug is a place-holder catch-all bug for any problems caused by the refactoring: we know, and we will fix it as soon as we have time!

Generally speaking, we are not interested in bug reports about things being broken at this point in time. We know, it's all broken, mostly deliberately because we are in the process of restructuring the code.

Please understand that us aggressively closing bugs related to this is nothing personal, we are just trying to reduce the noise a bit. :-)

[danx0r]

Fair enough, sorry I didn't quite get that the refactoring meant these sorts of reports are redundant.

[shartte]

What are your plans for the WWW UI? Are you going to start using a microframework for the web part (i.e. Flask or similar), or will you stick to using a custom one? Using something WSGI compatible would be very nice since mailpile could then efficiently be run behind something like nginx.

[ulikoehler]

@shartte In another pull request @BjarniRunar told me he wanted to keep dependencies as minimal as possible. I think this is the right way to go, because standalone packaging will be way easier that way.

[liliakai]

I'm getting the "global name '_' is not defined" error from #267. Is there a last-known-good revision for people just trying to get up and running?

[BjarniRunar]

Some thing are no longer broken. :-)

[ulikoehler]

@shartte Just to mention, MP can run behind nginx anyway, because you can simply run MP on e.g. port 33411 and configure nginx as an reverse proxy for it.