'No authentication mechansims supported by both server and client' Signalled When Attempting To Send Mail From ODI 12c Via SMTP With OdiSendMail Using Authentication (Doc ID 2017822.1)

Last updated on JULY 19, 2017

Applies to:

Oracle Data Integrator - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to send email messages from Oracle Data Integrator (ODI) 12c OdiSendMail tool using the following syntax:

OdiSendMail "-MAILHOST=my.mail.server.com" "-PORT=587" "-PROTOCOL=smtp" "-AUTH=YES" "-AUTHMECHANISMS=PLAIN" "-USER=YYY/xxxxx" "-PASS=xxxxxxxxxx==" "-FROM=myOtherUser@acme2.com" "-SUBJECT=Testmail ODI" "-TO=myUser@acme.com"
Hello,
This is a Testmail.

... through a Microsoft Exchange server requiring authentication with USER and PASSWORD, if the authentication parameter (AUTH) of ODISendMail is empty or set to "No", the error message is:

javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

This result is to be expected.

If the authentication parameter setting is YES, no matter which AUTHMECHANISMS is configured we get the following java exception when executing the package:

javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client
  at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:756)
  at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:669)
  at javax.mail.Service.connect(Service.java:317)
  at com.sunopsis.dwg.tools.SendMail.actionExecute(SendMail.java:205)
  at com.sunopsis.dwg.function.SnpsFunctionBaseRepositoryConnected.execute(SnpsFunctionBaseRepositoryConnected.java:209)
  at oracle.odi.runtime.agent.execution.SessionTask.execIntegratedFunction(SessionTask.java:870)
  at oracle.odi.runtime.agent.execution.SessionTask.executeOdiCommand(SessionTask.java:551)
  at oracle.odi.runtime.agent.execution.cmd.OdiCommandExecutor.execute(OdiCommandExecutor.java:32)
  at oracle.odi.runtime.agent.execution.cmd.OdiCommandExecutor.execute(OdiCommandExecutor.java:18)
  at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:52)
  at oracle.odi.runtime.agent.execution.SessionTask.processTask(SessionTask.java:189)
  at oracle.odi.runtime.agent.execution.SessionTask.doExecuteTask(SessionTask.java:111)
  at oracle.odi.runtime.agent.execution.AbstractSessionTask.execute(AbstractSessionTask.java:864)
  at oracle.odi.runtime.agent.execution.SessionExecutor$SerialTrain.runTasks(SessionExecutor.java:2024)
  at oracle.odi.runtime.agent.execution.SessionExecutor.executeSession(SessionExecutor.java:562)
  at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:718)
  at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:611)
  at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:203)
  at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doProcessStartAgentTask(TaskExecutorAgentRequestProcessor.java:800)
  at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$1400(StartSessRequestProcessor.java:74)
  at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:702)
  at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:180)
  at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:108)
  at java.lang.Thread.run(Thread.java:745)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms