Bonjour
Nous avons migrer sur le solution bluemind il y a quelque mois.
Nous rencontrons un bug avec EAS via l’application mail de samsung lorsque l’on souhaites activer le répondeur.
Une erreur s’affiche sur les smartphone et apparait également dans les logs.
Voici le log eas correspondant:
2026-09-22 12:24:32,065 [vert.x-eventloop-thread-3] n.b.e.p.ProtocolExecutor ERROR - No enum constant net.bluemind.eas.dto.settings.SettingsResponse.Oof.BodyType.text
java.lang.IllegalArgumentException: No enum constant net.bluemind.eas.dto.settings.SettingsResponse.Oof.BodyType.text
at java.base/java.lang.Enum.valueOf(Enum.java:293)
at net.bluemind.eas.dto.settings.SettingsResponse$Oof$BodyType.valueOf(SettingsResponse.java:1)
at net.bluemind.eas.command.settings.SettingsProtocol.builOofGetSettingsResponse(SettingsProtocol.java:144)
at net.bluemind.eas.command.settings.SettingsProtocol.execute(SettingsProtocol.java:93)
at net.bluemind.eas.command.settings.SettingsProtocol.execute(SettingsProtocol.java:1)
at net.bluemind.eas.protocol.ProtocolExecutor$RequestDTOHandler.lambda$2(ProtocolExecutor.java:112)
at net.bluemind.lib.vertx.VertxPlatform.lambda$14(VertxPlatform.java:261)
at io.vertx.core.impl.ExecuteBlocking$1.execute(ExecuteBlocking.java:36)
at io.vertx.core.impl.WorkerTask.run(WorkerTask.java:57)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1090)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:1474)
Bluemind est il informer ce ce comportement?