Mjarl

We tried this before and looked like it didn't work. However, now i tried the change (again) in config-itop.php. Confusingly it still first displayed port 465 after the change (?!?), so i restarted httpd and php-fpm (with systemctl) to eliminate possible cache issues. After this the second test still the same error ... only after basically just waiting for some minutes the third testcase suddenly worked ! Now outgoing emails seem to fly out This delay probably also caused us to dismiss prior tests...

Any ideas ?

We also tried to upgrade our iTop 3.2.2 to 3.2.3. We are using Google Workspace, which seems to be problematic. Our env is php 8.3.31, mariadb 11.8.6 on Oracle Linux 9.7. We are using latest Mail to Ticket Automation extension version 3.9.3. After upgrade new tickets are still created fine with new 3.2.3, but all outgoing emails fail with error message "Email sending failed: Connection to "smtp.gmail.com:465" has been closed unexpectedly." This happens both with emails created by triggers and by...

According to [https://www.itophub.io/wiki/page?id=latest:admin:rich_text_limitations] htmlnullsanizer is not recommended but it should be working ... in our tests if you set it then you get an error when trying to open any incident. If you first add an incident with API when htmlnullsanitizer is ON, you get the graphics as expected into an incident. But you cannot open that incident unless you set htmldomsanitizer back ... not very smart ... We are now on iTop version 3.2.2 (rhel9).

However, it also cuts off some incoming graphics from the emails which is a shame

I wonder why new "Mail to ticket automation "extension has not been made downloadable although on the documentation page it says that version 3.8.2 already exists ... ?

I wonder why "Mail to ticket automation "extension has not been made downloadable although on the documentation page it says that version 3.8.2 already exists ... ?

The issue was caused by (wrong) value in config-itop.php ... // html_sanitizer: The class to use for HTML sanitization: HTMLDOMSanitizer, HTMLPurifierSanitizer or HTMLNullSanitizer // default: 'HTMLDOMSanitizer' 'html_sanitizer' => 'HTMLDOMSanitizer', I had without knowing and for some historical reason value "HTMLNullSanitizer" as the value and that failed as explained before. HTMLDOMSanitizer is the default and better in any case, as null gives no security.