Activity for Oliver Heil
-
Oliver Heil committed [r3198] on Code
toggle empty search folders bug
-
Search window: hide empty folders
-
Resolved: https://github.com/oheil/NOCC/commit/f69c33416cff7001f3af2e0cdc85f1b191f8e4ec
-
Search window: hide empty folders
-
NOCC 1.9.15 released
-
Some unit tests don't work with phing
-
Auto-Update fails with php 8.2.3
-
Search feature
-
1.9.15
-
1.9.15
-
1.9.15
-
1.9.15
-
1.9.15-pre
-
1.9.15
-
1.9.15
-
http to https
-
http to https
-
http to https
-
multi accounts in differents tabs
-
Currently working on this feature!
-
All cookies are set to "/". I have to setup another NOCC instance with a root path e.g. /nocc/... to test things and do it right.
-
A quick look into the code shows nothing exceptional. My guess is that it may be the authentication process. NOCC doesn't send mail like you did with your quick php check, which is generally trusted, like sending email from the shell. NOCC sends email more like if you want to send email from some external client through some SMTP server on the internet, so there needs to be a authentication step to prevent e.g. malicious mass spam mail. Depending on your authentication method, this may take a bit...
-
I think this is a good idea and a missing feature. I can't promise when it will be finished, but I will definitely work on it. You can help me by telling me what you expect, how it should appear, what is especially important and so on. More information is better, but of course not everything is reasonable possible. Thanks for this proposal.
-
And you can use the Horde implementation, have you tried it?
-
The effort is quite low, that's fine for niches ;-)
-
Whats the problem with pecl install?
-
It would be best if you would open a Feature Request at Tickets, if you still like your idea.
-
(There is no PHP "sendmail". ) You mean probably PHP functions mail or mb_send_mail . In general this would be possible but needs to be implemented in NOCC. It would be some kind of worst case fallback. The email sent would originate from the server where NOCC is installed and not from the proper SMTP server configured for the email account you are sending from in NOCC. Of course, if you are the NOCC administrator you are probably the server administrator too, so you should know what you are doing....
-
Perhaps the problem is the combination of Server Temp Key: ECDH and OpenSSL/1.1.1q This old openssl does not understand elliptic curve algorithms (but I am not an expert, just guessing).
-
I must admit, I do not have anything particular in suspicion. Can you check your servers php openssl library? I do this for my server by calling a phpinfo.php file with content: <?php phpinfo(); This gives me for my server: OpenSSL support enabled OpenSSL Library Version OpenSSL 3.0.13 30 Jan 2024 OpenSSL Header Version OpenSSL 3.0.13 30 Jan 2024 Openssl default config /usr/lib/ssl/openssl.cnf Directive Local Value Master Value openssl.cafile no value no value openssl.capath no value no value You...
-
Do you running NOCC on an older Windows? Your local CAs are perhaps out of date?
-
NTLM SMTP auth
-
SMTP NTLM authentication method
-
Thanks for the reminder. Note there is: - https://pear.php.net/package/Auth_SASL This package is not maintained anymore and has been superseded. Use Auth_SASL2 instead. This being said: No, I didn't worked on it yet. But there may be some spare time in the near future for this. To be explicit about what we are talking about: The wish is, that the server side NOCC code authenticates to the SMTP and the IMAP/POP3 servers via SCRAM, right?
-
Perhaps this is the root cause of all the problems. Your NOCC server does not have the proper root certificate installed which are needed to verify the certificate which is shown by your smtp mail server. Have a look for example here: https://stackoverflow.com/questions/24372942/ssl-error-unable-to-get-local-issuer-certificate but there are many more if you just google the error. You should solve this issue here and revert the relaxing settings below to the stringent ones.
-
Good to know and thanks for your patience and effort to bring the issues up here! It's invaluable!
-
last change documented
-
added example for smtp host configuration
-
For a solution (still experimental) please do the following below. BEWARE: the issue with your certificate is still present, so you should try to fix your certificate or at least found out what the real problem is. But for NOCC and the SSL SMTP connection set your configuration values to: $conf->domains[$i]->smtp_allow_self_signed = false; $conf->domains[$i]->smtp_verify_peer = true; $conf->domains[$i]->smtp_verify_peer_name = false; // <-- a bit relaxed $conf->domains[$i]->smtp_peer_name = ''; $conf->domains[$i]->smtp_security_level...
-
Experimental solution to issue/discussion https://sourceforge.net/p/nocc/discussion/38301/thread/ac827e8c9e/?limit=25
-
The problem is not the smtp servers name missing in the certificate, because in this case the first error would be: Warning: stream_socket_client(): Peer certificate CN=`mail.mydomain.com' did not match expected CN=`test.mydomain.com' in C:\xampp8.2.4\htdocs\nocc-code-r2861-trunk\webmail\classes\class_smtp.php on line 110 Relaxing the smtp security context settings doesn't help neither in this case.
-
From your webserver (where NOCC is installed) you can run the following command: openssl s_client -connect mail.a......e.ca:465 I assume that your ssl smtp port is 465. Do you see any certificate problems in the output?
-
Thanks for the .htaccess hint, will do. Hm, I am unsure how to proceed with the certificate errors. Of course, port 25 is not a good work around! Can you give me more details about the certificate? Is it true that it is the same which I get when connecting https://mail.a......e.ca/ ? If yes I can try to mimic this on my installation. If yes can you pm me the servers name again, I didn't wrote it down for memory.
-
I did not have $conf->domains[$i]->smtp_security_level = -1; at all. That's normal as with new version people don't update their config to the newest version, which is typically not necessary. It's not easy to handle your issue, I can mainly only guess. It would be best if you could update to the current version (1.9.14) first. Second check all new config settings in conf.php.dist and update your config.php. (well this is a bit of work and chances are good that the error stays the same) Perhaps it...
-
995/pop3/ssl/novalidate-cert this switches cert validation off for receiving mails. Above errors are from sending mails via smtp. Can you check your smtp settings like: $conf->domains[$i]->smtp_allow_self_signed = true; $conf->domains[$i]->smtp_verify_peer = false; $conf->domains[$i]->smtp_verify_peer_name = true; $conf->domains[$i]->smtp_security_level = -1; The last one is probably set ot -1 for you too, which means it is not set and ssl default is on. Setting this value to 0 means "No restrictions....
-
I am on NOCC v1.9.13-dev. Probably after recent scheduled SSL cert renewals, my users started to get the following errors when they try to send emails: In the header of the page: Warning: stream_socket_client(): SSL operation failed with code 1. OpenSSL Error messages: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed in classes\class_smtp.php on line 106 Warning: stream_socket_client(): Failed to enable crypto in classes\class_smtp.php on line 106 Warning: stream_socket_client():...
-
In case it is the same certificate which I see when connecting to https://mail.a......e.ca/ : the hostname 'mail' is missing in the certificate therefor correctly seen as invalid.
-
PHP version and openssl version on your server may be important to know too. Check if everything is up to date.
-
I will have a look into it...
-
remove old simplepie
-
project webspace up to php74, upgrade simplepie
-
Remove To: column when showing folder contents
-
Cache POP3 requests
-
independed smtp login from pop/imap
-
More options for RSS feed
-
Need more developers!
-
Auto-Update fails with php 8.2.3
-
sha256 for update
-
Still unresolved on php 8.2.4, same error.
-
wrong date for release 1.9.13
-
NOCC 1.9.14 released
-
early release 1.9.14 before people change to php 8.2
-
early release 1.9.14 before people change to php 8.2
-
early release 1.9.14 before people change to php 8.2
-
Bug #511 Auto-Update fails with php 8.2.3
-
Auto-Update fails with php 8.2.3
-
Auto-Update fails with php 8.2.3
-
NOCC 1.9.13 released
-
release 1.9.13
-
release 1.9.13
-
release 1.9.13
-
http to https
-
Initial version: 07 March 2023 Using Horde Imap Client with an imap server over SSL(port 993) and authentication method PLAIN is not possible, because of a bug in the current development sources of the Horde Imap Client library. It works with the following changes: File lib/Horde/Imap/Client/Socket.php from line 764: Original code: case 'PLAIN': // RFC 2595/4616 - PLAIN SASL mechanism $cmd = $this->_authInitialResponse( $method, base64_encode(implode("\0", array( $username, $authusername, $password...
-
Resolves problems with Horde Imap Client and PLAIN SASL AUTH if login name is something like ad\user
-
Initial version: 06 March 2023 This is a little HowTo for using the Horde Imap Client with php8. The official download source of the Horde Imap Client is https://dev.horde.org/imap_client/ but the library there is quite outdated and will throw many errors when used with php8. The current development is on github at https://github.com/horde . These are the steps to provide the necessary files of the Horde Imap Client library to NOCC: cd /SOME_FOLDER mkdir Horde_Imap_Client-Git-horde cd Horde_Imap_Client-Git-horde...
-
Initial version: 07 March 2023 Using Horde Imap Client with an imap server over SSL(port 993) and authentication method PLAIN is not possible, because of a bug in the current development sources of the Horde Imap Client library. It works with the following changes: File lib/Horde/Imap/Client/Socket.php from line 764: Original code: case 'PLAIN': // RFC 2595/4616 - PLAIN SASL mechanism $cmd = $this->_authInitialResponse( $method, base64_encode(implode("\0", array( $username, $authusername, $password...
-
Initial version: 06 March 2023 This is a little HowTo for using the Horde Imap Client with php8. The official download source of the Horde Imap Client is https://dev.horde.org/imap_client/ but the library there is quite outdated and will throw many errors when used with php8. The current development is on github at https://github.com/horde . These are the steps to provide the necessary files of the Horde Imap Client library to NOCC: cd /SOME_FOLDER mkdir Horde_Imap_Client-Git-horde cd Horde_Imap_Client-Git-horde...
-
Initial verion: 06 March 2023 This is a little HowTo for using the Horde Imap Client with php8. The official download source of the Horde Imap Client is https://dev.horde.org/imap_client/ but the library there is quite outdated and will throw many errors when used with php8. The current development is on github at https://github.com/horde . These are the steps to provide the necessary files of the Horde Imap Client library to NOCC: cd /SOME_FOLDER mkdir Horde_Imap_Client-Git-horde cd Horde_Imap_Client-Git-horde...
-
Initial verion: 06 March 2023 This is a little HowTo for using the Horde Imap Client with php8. The official download source of the Horde Imap Client is https://dev.horde.org/imap_client/ but the library there is quite outdated and will throw many errors when used with php8. The current development is on github at https://github.com/horde . These are the steps to provide the necessary files of the Horde Imap Client library to NOCC: cd /SOME_FOLDER mkdir Horde_Imap_Client-Git-horde cd Horde_Imap_Client-Git-horde...
-
Initial verion: 06 March 2023 This is a little HowTo for using the Horde Imap Client with php8. The official download source of the Horde Imap Client is https://dev.horde.org/imap_client/ but the library there is quite outdated and will throw many errors when used with php8. The current development is on github at https://github.com/horde . These are the steps to provide the necessary files of the Horde Imap Client library to NOCC: cd SOME_FOLDER mkdir Horde_Imap_Client-Git-horde cd Horde_Imap_Client-Git-horde...
-
language logic
-
debug output removed
-
htmlpurifier-4.15.0-lite
-
htmlpurifier-4.15.0-lite
-
default language and session language
-
removed experimental code
-
php 8.2 deprecations
-
Great to know! Remember for the next release that you have to configure it again.
-
I have added two ssl context settings to classes/class_smtp.php : //stream_context_set_option($context, "ssl", "peer_name", "localdomain"); //stream_context_set_option($context, "ssl", "security_level", 0); There are some more changes which you can ignore. Please download https://sourceforge.net/p/nocc/code/HEAD/tree/trunk/webmail/classes/class_smtp.php?format=raw and overwrite your current classes/class_smtp.php with that. Uncomment the two lines (perhaps one after another) and give it a try. Hopefully...
-
experimental ssl options
-
$conf->domains[$i]->smtp_verify_peer_name = false; should actually do that, but you already have this, I guess.
-
Perhaps you have an issue with a missing root certificate. Can you go through this https://docs.sembark.com/blog/2021/10/04/install-letsencrypt-root-certificate-isrg-root-x1/ installing the ISRG Root X1 certificate on your machine which runs NOCC. (my other fix above was again too fast and bad, sorry for this, just ignore it for now.)
-
html_smtp_error_no_con instead if html_smtp_no_con
-
A side note, which does probably not help for your TLS problem. in classes\class_smtp.php on line 99 it must be $html_smtp_error_no_conn instead of $html_smtp_no_con But perhaps, if you change this, it gives a hint with the error message printed.
-
A side note, which does probably not help for your TLS problem. in classes\class_smtp.php on line 99 it must be $html_smtp_error_no_conn instead of $html_smtp_no_con But perhaps, if you change this, it gives a hint with the error message printed.
-
I see you are on Windows. Is this a reasonable new version of Windows?
-
Updated files ./classes/nocc_languages.php ./common.php in current head branch. Just exchange the your local files with: https://sourceforge.net/p/nocc/code/HEAD/tree/trunk/webmail/common.php?format=raw https://sourceforge.net/p/nocc/code/HEAD/tree/trunk/webmail/classes/nocc_languages.php?format=raw
-
regression bug from release 1.9.12
-
Thanks for the error report, I can confirm some of them. They are oversights of me and I will create a new version soon addressing them. Sending mails works for me except for producing the errors.
-
minor update
1 >
