Users

users@lists.roundcube.net

2 participants
2900 discussions

Fontsize
by Andreas Meyer 05 Mar '18

05 Mar '18

Hi! A user complains the font being to small. Can the fontsize be set? Kind regards Andreas -- PGP-Fingerprint: D392 5D21 0299 63D7 5BAE 4562 1E56 B2EA 81A2 59F1

4 5

Cannot send mail via round cube
by ɹןʇnqן 03 Mar '18

03 Mar '18

Mar 1 09:27:02 mail submit-tls/smtpd[86118]: connect from localhost[127.0.0.1] Mar 1 09:27:02 mail submit-tls/smtpd[86118]: SSL_accept error from localhost[127.0.0.1]: 0 Mar 1 09:27:02 mail submit-tls/smtpd[86118]: warning: TLS library problem: error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca:/usr/src/crypto/openssl/ssl/s3_pkt.c:1493:SSL alert number 48: Mar 1 09:27:02 mail submit-tls/smtpd[86118]: lost connection after STARTTLS from localhost[127.0.0.1] Mar 1 09:27:02 mail submit-tls/smtpd[86118]: disconnect from localhost[127.0.0.1] ehlo=1 starttls=0/1 commands=1/2 Sending mail on the submission port outside of roundcube works fine. Mar 1 09:35:35 mail submit-tls/smtpd[26307]: connect from unknown[24.71.178.2] Mar 1 09:35:36 mail submit-tls/smtpd[26307]: Anonymous TLS connection established from unknown[24.71.178.2]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) Mar 1 09:35:36 mail submit-tls/smtpd[26307]: NOQUEUE: permit: RCPT from unknown[24.71.178.2]: action=permit_sasl_authenticated for Client host=unknown[24.71.178.2] ; from=<lbutler(a)covisp.net> to=<user(a)example.net> proto=ESMTP helo=<[10.0.2.45]> Mar 1 09:35:36 mail last message repeated 2 times Mar 1 09:35:36 mail submit-tls/smtpd[26307]: 3zsdMr46Q6zbRf3: client=unknown[24.71.178.2], sasl_method=PLAIN, sasl_username=lbutler -- L Butler 303 219 0564

7 15

Re: [RCU] Cannot send mail via round cube
by Maarten 03 Mar '18

03 Mar '18

When roundcube connects to an imap or smtp server it's being a client therefore I think it would be logical that the client needs to validate the chain. When you are connecting to roundcube webinterface you are connecting to the server serving it, in that setting the browser is the client and the apache/nginx being the server. It's all a matter of who is the client and who is the server perspective as in who needs to validate and who needs to show they have a valid chain. On 03/03/2018 12:44 PM, Reindl Harald wrote: > > > Am 03.03.2018 um 12:29 schrieb Reindl Harald: >> Am 03.03.2018 um 10:08 schrieb Maarten: >>> If I understand ssl correctly I don't see the point to putting >>> fullchain.pem letsencrypt there, because of the following. Your browser >>> has the Root certificates installed, a php application does not. So >>> when >>> >>> you go to a webpage using letsencrypt certificates . You will see >>> something like this: >>> >>> DST Root CA X2 --> Root Certificate in browser >>> >>> Let's encrypt Authority X3 --> >>> >>> webmail.yourdomain.com --> your certificate >>> >>> >>> So the web browser uses the Root Certificate to verify the chain of >>> certificates to be valid. As far as I know a php application has no way >>> knowing if the service it's connecting to is using a valid ssl chain, I >>> don't know enough about php to be sure about this but sounds >>> correct. If >>> I am wrong about this someone may correct me about this and explain it >>> to me how this works in php. >> >> exactly the same way as on the browser side >> no idea why you think PHP is special here >> >> "As far as I know a php application has no way knowing if the service >> it's connecting to is using a valid ssl chain" is pure bullshit - get >> a proper maintained operating system and you have all working >> out-of-the-box >> >> http://php.net/manual/en/migration56.openssl.php >> >> All encrypted client streams now enable peer verification by default. >> By default, this will use OpenSSL's default CA bundle to verify the >> peer certificate. In most cases, no changes will need to be made to >> communicate with servers with valid SSL certificates, as distributors >> generally configure OpenSSL to use known good CA bundles > it's using even the same ca-bundle than everything else on the system, > the ca-bundle from mozilla - frankly do you think the php-devleopers > are idiots and enable verification by default when it won't work on > any reasonable server? > > [harry@srv-rhsoft:~]$ rpm -q --filesbypkg > openssl-libs-1.1.0g-1.fc27.x86_64 > openssl-libs /etc/pki/tls > openssl-libs /etc/pki/tls/certs > openssl-libs /etc/pki/tls/misc > openssl-libs /etc/pki/tls/openssl.cnf > openssl-libs /etc/pki/tls/private > .... > > [harry@srv-rhsoft:~]$ ls /etc/pki/tls/certs > total 4.0K > -rw-r--r-- 1 root root 2.5K 2017-11-06 09:24 Makefile > lrwxrwxrwx 1 root root 49 2018-02-06 14:48 ca-bundle.crt -> > /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem > lrwxrwxrwx 1 root root 55 2018-02-06 14:48 ca-bundle.trust.crt -> > /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt > > [harry@srv-rhsoft:~]$ rpm -q --file > /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem > ca-certificates-2018.2.22-1.0.fc27.noarch > > [harry@srv-rhsoft:~]$ rpm -q --info > ca-certificates-2018.2.22-1.0.fc27.noarch > Name : ca-certificates > Version : 2018.2.22 > Release : 1.0.fc27 > Architecture: noarch > Install Date: Thu Feb 8 09:43:10 2018 > Group : System Environment/Base > Size : 974873 > License : Public Domain > Signature : RSA/SHA256, Tue Feb 6 14:57:19 2018, Key ID > f55e7430f5282ee4 > Source RPM : ca-certificates-2018.2.22-1.0.fc27.src.rpm > Build Date : Tue Feb 6 14:48:33 2018 > Build Host : buildvm-ppc64le-04.ppc.fedoraproject.org > Relocations : (not relocatable) > Packager : Fedora Project > Vendor : Fedora Project > URL : https://fedoraproject.org/wiki/CA-Certificates > Summary : The Mozilla CA root certificate bundle > Description : > This package contains the set of CA certificates chos

1 0

Size of attachments
by Andreas Meyer 01 Mar '18

01 Mar '18

Hello! Writing a mail on the right side I see "maximun allowed size is 5,0 MB. Where is this value set? Kind regards Andreas -- PGP-Fingerprint: D392 5D21 0299 63D7 5BAE 4562 1E56 B2EA 81A2 59F1

1 1

another PGP thingi
by Andreas Meyer 01 Mar '18

01 Mar '18

Hello! I run two domains on one host. With one I have no problem using PGP with the otherone it does not work. Both domains use version 1.3.3 and enigma 0.7. Importing keys works, signing and encryption does not. I set $config['debug_level'] = 4; but nothing is logged at the moment. How can I debug that thing? I get the pinentry thing to input the passphrase and then it says signing failed. Regards Andreas -- PGP-Fingerprint: D392 5D21 0299 63D7 5BAE 4562 1E56 B2EA 81A2 59F1

1 2

Re: [RCU] Design larry
by Andreas Meyer 01 Mar '18

01 Mar '18

Reindl Harald <h.reindl(a)thelounge.net> schrieb am 01.03.18 um 17:36:04 Uhr: > Am 01.03.2018 um 17:28 schrieb Andreas Meyer: > > Is it possible to not let the user choose between the styles larry > > and classic? > > surely, my rpmbuild even removes "larry" before generating the package > in the %install section > > $rcmail_config['skin'] = 'classic'; I have $config['skin'] = 'larry' already set. Nevertheless in the settings one can choose between classic and larry style. Andreas -- PGP-Fingerprint: D392 5D21 0299 63D7 5BAE 4562 1E56 B2EA 81A2 59F1

2 1

Question regarding PGP
by Andreas Meyer 01 Mar '18

01 Mar '18

Hello! Is see this in the log: [01-Mar-2018 18:12:15 Europe/Berlin] PHP Warning: exec() has been disabled for security reasons in /vwww/HIDDEN/root/mailsystem/vendor/pear/crypt_gpg/Crypt/GPG/ProcessControl.php on line 143 Do I have to enable exec() in the php.ini? Kind regards Andreas -- PGP-Fingerprint: D392 5D21 0299 63D7 5BAE 4562 1E56 B2EA 81A2 59F1

2 2

Design larry
by Andreas Meyer 01 Mar '18

01 Mar '18

Hello! Is it possible to not let the user choose between the styles larry and classic? Kind regards Andreas -- PGP-Fingerprint: D392 5D21 0299 63D7 5BAE 4562 1E56 B2EA 81A2 59F1

1 0

How to avoid accessing mailboxes elsewhere
by Mario Jorge Lima 27 Feb '18

27 Feb '18

Hello, I will explain what I need to know. I have 3 Servers: 1) One of them is just a Domains Server. 2) The other two are Mailboxes Servers. They have the email accounts for all the Domains from the first Server. All these mailboxes' POP and SMTP are accessed through the Server address: mail.domainnamea.com. mail.domainnameb.com. mail.domainnamec.com. and so on. If someone who accesses my Roundcube, fill the Server field with any other POP Server name elsewhere, he will read those emails. How to avoid it, so that only mailboxes in one of my two Mailboxes mentioned above can be accessed? Thanks a lot. Mario./ ___________________________ Mario Jorge Lima mariolima(a)multisites.com.br OBS: Eventualmente nao acentuo algumas palavras do Portugues, para evitar bugs na recepcao dos emails.

4 4

Re: [RCU] [misc] failed to connect socket
by Roundcube 24 Feb '18

24 Feb '18

On 2018-02-23 (19:35 MST), Reindl Harald <h.reindl(a)thelounge.net> wrote: > > Am 24.02.2018 um 00:24 schrieb Roundcube: >> When trying to send an email from Roundcube I get: >> Connection failed: Failed to connect socket: fsockopen(): unable to connect to ssl://mail.covisp.net:587 > > it's as simple as port 587 is tls:// and not ssl:// > SSL versus STARTSSL You didn't see 3 lines down: >> If I change it to tls://mail.covisp.net I get: >> >> SMTP Error in /usr/local/www/roundcube/program/lib/Roundcube/rcube.php (1675): Authentication failure: STARTTLS failed (Code: ) -- Honesty may be the best policy, but it's important to remember that apparently, by elimination, dishonesty is the second-best policy.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Users