Workflow email notices rejected
Jeffrey Sheldon
I recently upgraded to DSpace 6 and have noticed different behavior with respect to email configuration as seen in DSpace 5.
I'm using a trusted and open SMTP relay which doesn't require authentication. Therefore, I have mail.server populated and mail.server.username and mail.server.password commented out (in DSpace 5, these could simply be left blank).
When I test the email configuration, the response is positive and the email appears in my inbox:
./dspace test-email
About to send test email:
- To: jshe...@ksu.edu
- Subject: DSpace test email
- Server: (my SMTP server address)
Email sent successfully!
However, workflow tasks will not deliver email, but log errors akin to the following:
2020-02-03 09:11:49,354 WARN org.dspace.workflowbasic.BasicWorkflowServiceImpl @ jshe...@k-state.edu:session_id=AF8FE128AE418F4C52CA462EF2BCE798:ip_addr=(address removed):notify_of_reject:cannot email user eperson_id=(eperson UUID removed) eperson_email=jshe...@k-state.edu workflow_item_id=20928\colon; Send failure (javax.mail.AuthenticationFailedException\colon; null)
Any suggestions? I have tried a number of combinations (including mail.server = localhost for Postfix to handle) and would expect this to work without issue as it did in the past. Always the same error.
-Jeff
Tim Donohue
You might want to look more closely at the log lines *around* that WARN message you noted below. They may provide more information about what the problem is with regards to sending the emails -- especially if you see an ERROR just before or after the WARN.
The error "AuthenticationFailedException" implies that either the configuration is incorrect (in some way) *or* maybe there's an SSL Handshake failure (if your mail server requires SSL and the cert cannot be verified by Java on the server running DSpace). But, it's hard to say for certain. Since the `test-email` works though, that would imply the configuration should hopefully be correct.
Sent: Monday, February 3, 2020 11:23 AM
To: dspac...@googlegroups.com <dspac...@googlegroups.com>
Subject: [dspace-tech] Workflow email notices rejected
All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/BN8PR05MB6644442FC0843498B5D2F25DD0000%40BN8PR05MB6644.namprd05.prod.outlook.com.
Jeffrey Sheldon
That's what make this so curious: That the test-email command will result in a successfully delivered email and the lack of any discernible notifications in any logs which reveal problems or association with this issue (including no other WARN or ERROR entries).
I haven't head any issues with email between DSpace 1.x - 5.x. Only 6.
-Jeff
________________________________________
From: Tim Donohue <tim.d...@lyrasis.org>
Sent: Monday, February 3, 2020 1:38 PM
To: Jeffrey Sheldon; dspac...@googlegroups.com
Subject: Re: Workflow email notices rejected
Mark H. Wood
only guess is that the authentication rules for ksu.edu are different
from those for k-state.edu even though they are MXed to the same place.
--
Mark H. Wood
Lead Technology Analyst
University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu
Mark H. Wood
The admin. email address and the workflow address are different. My
only guess is that the authentication rules for ksu.edu are different
from those for k-state.edu even though they are MXed to the same place.