topic Re: tSendMail Client was not authenticated in Talend Studio

tSendMail Client was not authenticated

Anonymous — Tue, 02 Jan 2018 09:11:36 GMT

[statistics] connecting to socket on port 3484

[statistics] connected

Exception in component tSendMail_1 (DBFileParserLight)

com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.1 Client was not authenticated

at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)

at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)

at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)

at javax.mail.Transport.send0(Transport.java:169)

at javax.mail.Transport.send(Transport.java:98)

at ingestion_pipeline_dev2.dbfileparserlight_0_2.DBFileParserLight.tSendMail_1Process(DBFileParserLight.java:979)

at ingestion_pipeline_dev2.dbfileparserlight_0_2.DBFileParserLight.runJobInTOS(DBFileParserLight.java:4251)

at ingestion_pipeline_dev2.dbfileparserlight_0_2.DBFileParserLight.main(DBFileParserLight.java:3958)

[FATAL]: ingestion_pipeline_dev2.dbfileparserlight_0_2.DBFileParserLight - tSendMail_1 530 5.7.1 Client was not authenticated

com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.1 Client was not authenticated

at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)

at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)

at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)

at javax.mail.Transport.send0(Transport.java:169)

at javax.mail.Transport.send(Transport.java:98)

at ingestion_pipeline_dev2.dbfileparserlight_0_2.DBFileParserLight.tSendMail_1Process(DBFileParserLight.java:979)

at ingestion_pipeline_dev2.dbfileparserlight_0_2.DBFileParserLight.runJobInTOS(DBFileParserLight.java:4251)

at ingestion_pipeline_dev2.dbfileparserlight_0_2.DBFileParserLight.main(DBFileParserLight.java:3958)

[statistics] disconnected

Re: tSendMail Client was not authenticated

lojdr — Tue, 02 Jan 2018 13:11:40 GMT

Hello sjain,

You need to allow anonymous users to use the Exchange server as SMTP server. See how to do it here:

https://www.sonicwall.com/en-us/support/knowledge-base/170504828576336

Regards

Ondrej

Re: tSendMail Client was not authenticated

Anonymous — Wed, 17 Jan 2018 09:37:12 GMT

Then what is the point of having authentication option in place when we have to allow "anonymous"?

Re: tSendMail Client was not authenticated

lojdr — Wed, 17 Jan 2018 09:58:41 GMT

Hello,

Check the configuration you are using with your Exchange admin.

Regards

lojdr

Re: tSendMail Client was not authenticated

Anonymous — Wed, 17 Jan 2018 10:08:17 GMT

Can you be more specific, what configuration need to ask from Exchange side ?

Re: tSendMail Client was not authenticated

lojdr — Wed, 17 Jan 2018 10:48:08 GMT

All the information you see above.

Then try to send an email via PowerShell or Bash (any command line environment you have) from the same computer using the information from the Exchange team.

Do you see the same error?

Re: tSendMail Client was not authenticated

Anonymous — Thu, 18 Jan 2018 05:07:07 GMT

Using all those information, we can send email via python script without any issues.. same setting in talend job throws the error..

Re: tSendMail Client was not authenticated

lojdr — Thu, 18 Jan 2018 09:40:21 GMT

From the same machine where the Talend is installed?

Re: tSendMail Client was not authenticated

Anonymous — Fri, 19 Jan 2018 05:19:47 GMT

Yes, see attached screenshot of error talend job giving & python script with same SMTP is working fine.

Note: SMTP require NTLM authentication, not sure our component support this or not ?

Screen Shot 2018-01-18 at 1.57.38 PM.png
Screen Shot 2018-01-18 at 1.57.50 PM.png
smtp_output.txt
test_ntlm.txt

Re: tSendMail Client was not authenticated

lojdr — Fri, 19 Jan 2018 14:24:16 GMT

Not sure if this is possible with this component. It looks that only Basic authentication is possible.

Re: tSendMail Client was not authenticated

Anonymous — Tue, 07 May 2019 07:13:03 GMT

I got the same error "Client not authenticated"
I was trying to implement Mailing component if a job fails on my company's smtp server.
When using talend to send mails for job failure on a local machine, I tried using port no 587 (as this is the default mailing port on machines) and local machine credentials.
That solved my issue .
Earlier I was using port no 25 but using Talend Studio on my local machine which landed me on this error.
But while trying to deploy it on a cloud server, organisations usually keep port no 25 as their smtp port.

Do try this!
To know more about smtp ports - https://www.mailgun.com/blog/which-smtp-port-understanding-ports-25-465-587