I'm pretty sure that you have encountered this kind of scenario especially if you have enabled the item request feature where a user put a non existing email address. You will later discover the "Delivery to the following recipient failed permanently" message when responding to the users' request/feedback. Although it is the user's fault for using an invalid/non existing email address, we take our user's requests/feedback seriously and as much as possible we want to make sure to respond or serve any of their requests/feedbacks. Is there a workaround for this? Or is there some way to check first and then enforce that the user will use a valid and existing email address? Using some sort of verification link to be sent to the users' email address like during self-registration might be overkill or a hassle to them right? Any ideas?
Thanks in advance and cheers, Elvi -- View this message in context: http://dspace.2283337.n4.nabble.com/Is-it-possible-to-enforce-check-that-the-user-use-a-valid-and-existing-email-address-when-using-DSpa-tp4675097.html Sent from the DSpace - Tech mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
