Hi,
I have problem with sending email to custom TLD domain. How can I please fix it ?
LOG:
[[32malfresco_1 |^[[0m 2021-06-09 14:35:41,141 ERROR [action.executer.MailActionExecuter] [mailAsyncAction1] Failed to send email to 'xxx.xxx@xxx.acr' as the address is incorrectly formatted ^[[32malfresco_1 |^[[0m Exception in thread "mailAsyncAction1" java.lang.ClassCastException: class com.sun.proxy.$Proxy330 cannot be cast to class org.alfresco.repo.action.executer.LoggingAwareExecuter (com.sun.proxy.$Proxy330 and org.alfresco.repo.action.executer.LoggingAwareExecuter are in unnamed module of loader org.apache.catalina.loader.ParallelWebappClassLoader @35ea5a66) ^[[32malfresco_1 |^[[0m at org.alfresco.repo.action.ActionServiceImpl.onLogException(ActionServiceImpl.java:1840) ^[[32malfresco_1 |^[[0m at org.alfresco.repo.action.AsynchronousActionExecutionQueueImpl$ActionExecutionWrapper.run(AsynchronousActionExecutionQueueImpl.java:449) ^[[32malfresco_1 |^[[0m at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ^[[32malfresco_1 |^[[0m at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ^[[32malfresco_1 |^[[0m at java.base/java.lang.Thread.run(Thread.java:834)
Solved! Go to Solution.
The setting mail.validate.addresses in the alfresco-global.properties controls whether email addresses will be validated via the Apache Commons Email Validator utility. For custom TLDs not defined by default in the Domain Validator utility (called by the Email Validator), this would be the source of the error.
Its not quite clear from the logs about the root cause. it seems like email validation issue but, Can you enable these debug logs and get the full stack trace of the error?
log4j.logger.org.alfresco.repo.action.executer.MailActionExecuter=debug log4j.logger.org.alfresco.repo.transaction.RetryingTransactionHelper=debug
The setting mail.validate.addresses in the alfresco-global.properties controls whether email addresses will be validated via the Apache Commons Email Validator utility. For custom TLDs not defined by default in the Domain Validator utility (called by the Email Validator), this would be the source of the error.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.