ldap-chpw-cgi/README.md

41 lines
1.9 KiB
Markdown
Raw Normal View History

2015-10-19 18:29:41 +02: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](https://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
2015-10-19 18:29:41 +02:00
location is reachable via HTTPS.
2018-12-16 18:54:11 +01:00
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`
2015-10-19 18:29:41 +02:00
## Acknowledgements
This is a majorly refined version of a script originally developed by Dirk Boye.
See [dirkboye/mailpw_change](https://github.com/dirkboye/mailpw_change) at GitHub
for the original source code.
## FAQ
* *Q:* Can I use the script via unencrypted HTTP?<br>
*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/`?<br>
*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?<br>
*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.
2018-12-16 18:54:11 +01:00
If you have trouble finding the root cause, possibly a look at `journalctl -b`
will help you.