On Wed, May 14, 2014 at 09:08:39AM +0200, Manu Mohedano wrote: > Since a few days, notifications that collections' admins received after a > new submission is requested are not sent. In the logs appears > > *2014-05-13 13:08:36,249 WARN org.dspace.workflow.WorkflowManager @ > [email protected]:session_id=68C5103874677224B97066A6879C31F2.tomcat1:ip_addr=212.128.168.213:notifyOfArchive:cannot > email user item_id=118450* > > The thing is other kind of notifications like the subscribers ones or > dspace email test on /dspace/bin directory works correctly.
"cannot email user" doesn't tell us very much. Are there adjacent messages which might reveal more? Can you get corresponding log records from the Message Transfer Agent (e.g. sendmail) for these attempts? Unfortunately, WorkflowManager.notifyOfArchive discards the actual MessagingException which might have explained the problem. I've filed an Issue on that. (https://jira.duraspace.org/browse/DS-2003) -- Mark H. Wood, Lead System Programmer [email protected] Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs
_______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
