Bug 24233 - Library branches editor doesn't allow email addresses with a name
Summary: Library branches editor doesn't allow email addresses with a name
Status: RESOLVED DUPLICATE of bug 15349
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-12 18:25 UTC by Kyle M Hall
Modified: 2021-07-13 14:27 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall 2019-12-12 18:25:15 UTC
So, when we send email via koha, we set the from field to just the branch email address ( e.g. "us@library.org" ). Some libraries would like to be able to have the library name as part of the email address ( e.g. "Your Library <us@library.org>" ).

The problem is that this does not pass validation in the branches editor. We know this format works because some libraries set this email format before the syntax validation was implemented.

We should update the validation algorithm to allow for the latter format in addition to the former.
Comment 1 Jonathan Druart 2019-12-17 10:05:58 UTC
Instead should not we have the ability to add the library name when the notices are sent?
Comment 2 Katrin Fischer 2020-04-30 21:50:49 UTC
The text can vary a bit from branchname - sometimes there are longer or shorter versions of the library name or they want to add 'on behalf of' as branchemail would be a noreply in our setup (hosted, sending emails from our mail servers, sender needs to be an address in our domain to not end up in spam)

I've also removed the validation from the email field for ours... and it does work as Kyle says.
Comment 3 Katrin Fischer 2021-07-13 14:19:43 UTC

*** This bug has been marked as a duplicate of bug 9815 ***
Comment 4 Katrin Fischer 2021-07-13 14:27:16 UTC

*** This bug has been marked as a duplicate of bug 15349 ***