Update SnappyMail repository references to nextgen-networks

Replaced references to https://github.com/the-djmaze/snappymail with
https://github.com/nextgen-networks/snappymail/ across the repository,
excluding README files as requested.

The replacement handles trailing slashes carefully to ensure bare URLs
include the slash while sub-paths (like /issues/ or .git) do not result
in double slashes. Files that already used the new domain were also
updated to ensure consistent trailing slash usage.

Co-authored-by: nextgen-networks <21206978+nextgen-networks@users.noreply.github.com>
This commit is contained in:
google-labs-jules[bot] 2026-02-20 11:18:25 +00:00
parent a88d24c38a
commit 0b86edb167
83 changed files with 844 additions and 844 deletions

View file

@ -132,7 +132,7 @@ class LdapMailAccounts
return false; // exceptions are only thrown from the handle error function that does logging already
}
//Basing on https://github.com/the-djmaze/snappymail/issues/616
//Basing on https://github.com/nextgen-networks/snappymail/issues/616
$oActions = \RainLoop\Api::Actions();
@ -192,7 +192,7 @@ class LdapMailAccounts
//When the password of the main account changes, SnappyMail asks the user for the old password to reencrypt the keys with the new userpassword.
//On a password change using ldap (or when the password has been forgotten by the user) this makes us some problems. Therefore overwrite
//the .cryptkey file in order to always accept the actual ldap password of the user. This has side effects on pgp keys!
//See https://github.com/the-djmaze/snappymail/issues/1570#issuecomment-2085528061
//See https://github.com/nextgen-networks/snappymail/issues/1570#issuecomment-2085528061
if ($this->config->bool_overwrite_cryptkey) {
if (!$oActions->StorageProvider()->Put($oAccount, StorageType::ROOT, '.cryptkey', "")) {
$this->logger->Write("Could not overwrite the .cryptkey file!", \LOG_WARNING, self::LOG_KEY);