I recently migrated our DSpace 1.7.2 instance to a new server. While waiting
for our network team to grant access to our local SMTP server, I noticed that
when DSpace can't reach the mailserver to send email notifications, the result
is a Java error. (Now that we're up and running I don't have a stack trace on
hand to send, but it was a "connection timed out" error during the attempt to
send a notification.)
The engineer responsible for our mail server warns me that because of the
possibility of unexpected maintenance, he can't guarantee that the mail server
will be up 24/7. Local applications are expected to queue their own mail in an
event of an outage.
Right now, if the mail server were to go down temporarily, the timeout error
would interrupt the DSpace workflow (i.e., during review when a notification is
sent after each step) and prevent further activity while we waited for it to
come back up. This isn't a pressing problem for us at the moment, but it could
become one in the future, particularly once we start receiving automated
deposits.
Has this issue come up before? (Apologies if there's a simple solution I'm
missing -- I'm not an IT professional, although I wear two hats as both the
sysadmin and the primary end user of our DSpace instance.) It's beyond my own
ability to implement, but a simple queue for outgoing notifications would be a
helpful feature.
N
Nicholas Webb
Assistant Archivist
Mount Sinai Medical Center
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
