This is a personal mirror from https://github.com/vchrizz/ldap-chpw-cgi
Go to file
Daniel A. Maierhofer 9b74fcabee Remove Message:
2020-04-27 00:35:08 +02:00
tpl Remove Message: 2020-04-27 00:35:08 +02:00
.htaccess Block access to .git directory via web server 2015-10-21 16:23:37 +02:00
index.py Add german translation 2017-06-18 13:59:31 +02:00
LICENSE
README.md Hints for U7 users 2018-12-18 09:41:58 +01:00

VMailMgr chpw CGI

This is a Python CGI script that lets virtual VMailMgr/qmail users change their own mail passwords via a web interface.

This script is specifically tailored to work on hosts at uberspace.de. But it may also work on other qmail-based systems as long as virtual mail users are managed via VMailMgr.

Installation

To install the script, simply extract all the repository contents into a folder under your document root. No paths need to be configured. Only make sure that the location is reachable via HTTPS.

In case you are using a U7 uberspace, you have to add a SELinux permission to allow apache to access both your home directory and the VMailMgr user database: chcon -t httpd_sys_content_t ~ ~/passwd.cdb

Acknowledgements

This is a majorly refined version of a script originally developed by Dirk Boye. See dirkboye/mailpw_change at GitHub for the original source code.

FAQ

  • Q: Can I use the script via unencrypted HTTP?
    A: No, HTTPS is hard-coded. So unless you change that in the code, you can't. And honestly, you really shouldn't.

  • Q: Do I need to put the script in /cgi-bin/?
    A: In most cases, no. The script comes with an .htaccess that enables CGI execution for the current directory. Generally, that should work. If not, your administrator may have disabled option overriding in which case you actually need to put it in /cgi-bin/. But in most cases (and especially on Uberspaces) it should work just fine.

  • Q: I only get an error 500 and the log file says something about suEXEC policy violation. How do I fix that?
    A: Make sure both the index.py as well as the containing directory have the permissions 0755. Any higher permissions will usually result in that error. If you have trouble finding the root cause, possibly a look at journalctl -b will help you.