Thank you for your input. We will take a look at this option in upcoming Plesk releasesF. Verdet commented
This is not only needed for VERP (for automatic bounce message processing), but also simply for address tags/plus addresses/subadressing (cf. RFC-5233 ) by real humans as a way of coping with the spam problem.
That's a kind of very simple to use "poor man's disposable email addressing".
When e.g. registering with some online service, provide an e-mail-address with a tag, which will be specific to this service. If that address leaks (or is sold by) that service, you have a track and then you just can reject/drop mails to that address. With tagged addresses, no need to set up a new address/alias/... - just invent whatever tag(s) you want and it's delivered to your base mailbox. (see for instance  or some better reference).
It's an easy way to cope with spam - more on a semantic level though...
You could even do some tag based filter rules (and even drop tag-less mails to rule out spammers that try stripping off the tags)...
Many hosters (MTA providers) support subaddressing since ages - they're obviously not running Plesk...
We have an article with an instruction how to set up django on Plesk server https://www.plesk.com/blog/product-technology/plesk-and-django
So, now we would like to get a feedback what is the most critical things you need to manage with Plesk regarding django.