A

accolon

Johnnii360 Echt jetzt… 4 Tage vergangen und keiner hat eine Idee oder ähnliches?! Das ist schon irgendwie… na ja…

Es ist auch, wie der Name sagt, ein Community-Forum. Mit einem englischen Post haettest du auch hoechstwahrscheinlich eine groessere Nutzermenge erreicht.

Johnnii360 Aktiviertes TLS 1.0 und 1.1 ist ziemlich fahrlässig, wenn man nur moderne Mail-Programme nutzt.

Wie @accolon ansprach geht es hierbei um Server-to-Server Kommunikation. Meines Wissens nach: Wenn nur TLSv1.2 und TLSv1.3 hinterlegt ist und aeltere Mail-Server (soll vorkommen) weder noch supporten, wird keine Verschluesselung verwendet. In anderen Worten: Schlechtere Verschluesselung ist besser als gar keine.

ok I fixed the issue, obviously was my faulty configuration. Specifically:

• the MAIL.DOMAIN.TLD nginx proxy config was faulty (thanks @accolon for the hint that allowed me to understand, I thought that SOGo needed a much more complex nginx proxy configuration)
• The error on Sogo WebUI login (password policy 65535) was telling me that I was not allowed to login directly from the SOGo web interface. The reason was that my email user was missing a tick in the checkbox in the Mailcow web configuration under E-Mail -> Configuration -> (select and edit the email user) -> Tick the checkbox to allow direct login to SOGo.

@accolon

thanks for your reply.

Yes, it was indeed an upgrade from 1.5.x and I already did the extra steps mentioned in the docs.
This is what my /web/rc/config/config.inc.php looks like:

GNU nano 4.8 config.inc.php
<?php
error_reporting(0);
if (!file_exists('/tmp/mime.types')) {
file_put_contents("/tmp/mime.types", fopen("http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types", 'r'));
}
$config = array();
$config['db_dsnw'] = 'mysql://' . getenv('DBUSER') . ':' . getenv('DBPASS') . '@mysql/' . getenv('DBNAME');
$config['imap_host'] = 'tls://dovecot:143';
$config['smtp_host'] = 'tls://postfix:587';
$config['smtp_user'] = '%u';
$config['smtp_pass'] = '%p';
$config['support_url'] = '';
$config['product_name'] = 'Roundcube Webmail';
$config['des_key'] = 'XXX';
$config['log_dir'] = '/dev/null';
$config['temp_dir'] = '/tmp';
$config['plugins'] = array(
'archive',
'managesieve',
'password'
);
$config['mime_types'] = '/tmp/mime.types';
$config['imap_conn_options'] = array(
'ssl' => array('verify_peer' => false, 'verify_peer_name' => false, 'allow_self_signed' => true)
);
$config['enable_installer'] = true;
$config['smtp_conn_options'] = array(
'ssl' => array('verify_peer' => false, 'verify_peer_name' => false, 'allow_self_signed' => true)
);
$config['db_prefix'] = 'mailcow_rc1';
#inserted to allow sender editing
$config['identities_level'] = 0;

Looks fine for me, what do you think?

I also tried to set the COMPOSER variable, but it seems like he wants to resolve some package dependencies.

`d481a5a4f70b:/web/rc# COMPOSER=composer.json php composer.phar update –no-dev –with-all-dependencies
Loading “roundcube/plugin-installer” which is a legacy composer-installer built for Composer 1.x, it is likely to cause issues as you are running Composer 2.x.
Loading composer repositories with package information
Package “–no-dev” listed for update is not locked.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires pear/net_smtp ₁.10.0, found pear/net_smtp[1.10.0, 1.10.1] but the package is fixed to 1.8.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 2
- Root composer.json requires pear/net_sieve ₁.4.5, found pear/net_sieve[1.4.5, 1.4.6] but the package is fixed to 1.4.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 3
- Root composer.json requires roundcube/plugin-installer ₀.3.1, found roundcube/plugin-installer[0.3.1, 0.3.2] but the package is fixed to 0.2.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 4
- Root composer.json requires masterminds/html5 ₂.7.0, found masterminds/html5[2.7.0, …, 2.7.6] but the package is fixed to 2.5.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Problem 5
- phpunit/phpunit is locked to version 5.7.27 and an update of this package was not requested.
- phpunit/phpunit 5.7.27 requires php ⁵.6 || ⁷.0 -> your php version (8.1.14) does not satisfy that requirement.`