Posts by fluser

coolternet Please open a new thread and describe your problem - this one is quiet old

Edit the PHP settings for this customer directly in Shell and restart PHP. Check the timeout setting in the Apache2 virtualhost and adjust accordingly.

But this is only a workarround. Cleaner way would be to run the script directly in the shell/cron and not by curl/wget

According to the docs: https://www.php.net/manual/en/…hp#ini.max-execution-time

In command line the max execution time is unlimited. Are you able to run the script through the shell?

If yes: You can list and edit the crontab for every I-MSCP user:

PHP-Curl und Curl unterscheiden sich und teilen sich die Einstellungen aus dem php.ini nicht.

Um Dein Problem lösen zu können, musst Du folgendes ausführen und prüfen:

Das folgende wird wohl abgewählt sein - das muss aber aktiv sein:

Debian Jessie ist aber auch schon in die Jahre gekommen und wird nicht mehr mit Support versorgt - ich würde Dir raten, mindestens auf Debian Stretch zu wechseln, wenn nicht sogar neuer, wenn es möglich ist.

"Quick and dirty" kannst Du curl auch mit "-k" aufrufen, dann wird die Zertifikats-Prüfung übersprungen.

Welches OS setzt Du den ein? Und wenn Du von Curl schreibst: Meinst Du Curl in der Shell oder PHP-Curl?

Quote from fulltilt

how about the main.cf TLS settings, especially smtpd_tls_auth_only = yes?

Code

1. smtpd_tls_auth_only = yes
2. tls_preempt_cipherlist = yes

Should work too, but I did not test this setting.

You can use this listener to enforce TLS for submission:

https://github.com/i-MSCP/imsc…postfix_submission_tls.pl

This entry should be sufficient:

And I think, you do not want to use "tls_wrappermode" for submission - all latest mail clients are correctly using StartTLS.

The TLS-Connection (OpenSSL Output) seems ok. I had a look at your configuration and I don't think you need to configure:

I suggest to try it again after commenting out this entry.

Looks like it is working?

Did you forget to restart the service?

CSF and LFD may be also an alternative: https://www.configserver.com/cp/csf.html

Pros:

* Easy to maintain

* Bruteforce detection

* Customizable with regex

* Build in Firewall, which is easy to configure

* Can work with any CMS which logs bad login attemptions (Custom Log and Custom Rules)

Cons:

* Firewall is limitted to in- and outgoing - not a blocker for I-MSCP