Suggestion to avoid spam filtering changing EnvelopeFrom in Configuring Outgoing Email
Actually an Institution cannot catch bounced emails because the EnvelopeFrom header field in Alma's emails is set to an address that has the domain @exlibrisgroup.com and it is not accessible. Changing the EnvelopeFrom to an email address in the institution domain may result in spam filtering and blocking. But if you could provide one email address account accessible in the domain @exlibrisgroup.com per Institution it could be use ad EnvelopeFrom address: the email (an example for my institution: 39UPI-email_admin@exlibrisgroup.com) should be readable by the related institution staff and user as EnvelopeFrom address (and/or for other purpose, such as Alma's admin log email), so the institution can read bounced emails avoiding the spam filtering issue.
-
Nazzareno Bedini commented
Perfect, the mail relay is the best solution I don't even dare to ask.
-
The August 2017 release includes a new capability in which you can now configure Alma to use an institution's mail relay, instead of emailing recipients directly from Ex Libris' cloud mail relays. This addresses the issues raised in the idea, albeit using a different approach.