Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
I have recently changed the password scheme of my Dovecot/Postfix/Roundcube installation. New passwords are encrypted stronger than before. It is not possible to automatically update existing passwords (because the old encryption is not so bad that I can easily crack it). But I'd like to tell my users that they can upgrade to the new password scheme by simply submitting the "change password" form with their old password in all three input fields. Currently a minor optimization prevents this. I think this minor optimization should be removed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
repository
|
|
|
|
|
|
|
|
|
|
|
|
|
|
argument doesn't do the same as with no 2nd argument as it should
|
|
|
|
|
|
message_compose hook (#1489000)
Prevent from re-adding the same forward attachment on compose page refresh
|
|
|
|
|
|
|
|
from commit d30460ad2fc0f78ce44d474fa2c466d660596d27, small improvements
|
|
|
|
|
|
|
|
|
|
|
|
folder name. A message with the same UID may exist in another folder.
|
|
(#1486939)
|
|
prefer_html option value is
|
|
correct no matter if prefer_html is enabled or not.
|
|
|
|
works in "recursive mode" - removed $recursive argument.
|
|
on 403 Forbidden response (#1488960)
|
|
|
|
|
|
contain any element, not only A tag or text node, but also e.g. span
|
|
|
|
|
|
|
|
|
|
version 2005+
|
|
|
|
|
|
|
|
Test content_id with isset instead of a true/false value
|
|
|