- Python 76.5%
- HTML 11.1%
- Shell 4.1%
- Dockerfile 2.2%
- JavaScript 2.1%
- Other 3.9%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
4110: Clear webmail session cookies on SSO login r=nextgens a=spomata ## What type of PR? bug-fix ## What does this PR do? After an SSO login as a different user, or after the Mailu session expired while the webmail cookie survived, the webmail keeps its old session. Its IMAP credential is a temp token bound to the replaced Mailu session (`flask.session.regenerate()`), so IMAP rejects it (`Folders error: AUTHENTICATIONFAILED`). Snappymail only goes back through `sso.php` when it has no session, so it never picks up the new user. This PR expires the webmail cookies (`smsession`, `roundcube_sessauth`, `roundcube_sessid`) on every successful SSO login (form login and both proxy-auth paths), as `/sso/logout` already does. The cookie-clearing loop is moved into a helper shared with logout. ### Related issue(s) - closes #4109 ## Prerequisites - [x] In case of feature or enhancement: documentation updated accordingly - [x] Unless it's docs or a minor change: add changelog entry file. ## Testing Tested on a 2024.06.60 deployment with Snappymail: switching A→B and B→A works with and without closing the browser in between; a normal single login and logout keep working. Co-authored-by: spomata <49432438+spomata@users.noreply.github.com> |
||
| .github | ||
| core | ||
| design | ||
| docs | ||
| optional | ||
| scripts | ||
| setup | ||
| tests | ||
| towncrier | ||
| webmails | ||
| .gitignore | ||
| .mergify.yml | ||
| AUTHORS.md | ||
| bors.toml | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| ISSUE_TEMPLATE.md | ||
| LICENSE.md | ||
| PULL_REQUEST_TEMPLATE.md | ||
| pyproject.toml | ||
| README.md | ||
| RELEASE_TEMPLATE.md | ||
| SECURITY.md | ||

Mailu is a simple yet full-featured mail server as a set of Docker images. It is free software (both as in free beer and as in free speech), open to suggestions and external contributions. The project aims at providing people with an easily setup, easily maintained and full-featured mail server while not shipping proprietary software nor unrelated features often found in popular groupware.
Most of the documentation is available on our Website. You can also try our demo server before setting up your own.
Features
Main features include:
- Standard email server, IMAP and IMAP+, SMTP and Submission with auto-configuration profiles for clients
- Advanced email features, aliases, domain aliases, custom routing, full-text search of email attachments
- Web access, multiple Webmails and administration interface
- User features, aliases, auto-reply, auto-forward, fetched accounts, managesieve
- Admin features, global admins, announcements, per-domain delegation, quotas
- Security, enforced TLS, DANE, MTA-STS, Letsencrypt!, outgoing DKIM, anti-virus scanner, Snuffleupagus, block malicious attachments
- Antispam, auto-learn, greylisting, DMARC and SPF, anti-spoofing
- Freedom, all FOSS components, no tracker included
Contributing
Mailu is free software, open to suggestions and contributions. All components are free software and compatible with the MIT license. All specific configuration files, Dockerfiles and code are placed under the MIT license.
