Protocol type "EXCHANGE" missing in FetchBouncesUtility.php in line 88

[responseinformationsdesign]

If chosen protocol type "EXCHANGE" there is an error:

Configuration incomplete. "type" is invalid. Check EM. Aborting.

[Gernott]

Hi, thank you for reporting. We don't use exchange in our company. If you can fix (and test) this issue and would send a pull request, I'll merge it to a new version.

[velletti]

@Gernott

i will fix it and send a Pull request. i found also one other small issue in compatiblity with TYPO3 LTS 10. (CONST typo3_branch is not defined anymore .. )

new version 2.3.1 ?

[Gernott]

If you have only Bugfixes, we have the new version 2.2.1.
If new features, then 2.3.0
Thank you!

[velletti]

Sorry for the confusion :

In ext_emConf we have Version 2.3.0 so i changed Version to 2.3.1
(since my last pull request for LTS 10 compatibility was a new feature i changed it to 2.3.0)

IN TER still 2.2.0

but the access to Exchange is not working anymore :-(

Warning: imap_open():

Couldn't open stream

imap_open("{outlook.office365.com:993/service=imap/ssl/novalidate-cert/authuser=[email protected]/user=[email protected]}","[email protected]", 'My-password')

i tried different Options {outlook.office365.com:993/imap4/ssl/novalidate-cert/authuser=[email protected]}
or TLS and more.

could not get it running again. also not using a simple test tool

[Gernott]

Ah - yes.
I didn't publish your version - so you can fix it and I publish 2.3.0 to TER and Packagist.
Don't forget to set the version in ext_emconf.php and composer.json too :)

[Gernott]

Ok, the version in composer.json is removed. In 2.2.0 it was 2.1.0. This is the reason, why 2.2.0 is missing at packagist. Now and in future it should work out of the box (with no versionnumber in composer.json).