Bug 2234 - Make cart email from/reply-to/return-path address configurable
Summary: Make cart email from/reply-to/return-path address configurable
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: PC All
: P3 enhancement
Assignee: Galen Charlton
QA Contact:
URL:
Keywords:
: 3679 (view as bug list)
Depends on: 10269
Blocks:
  Show dependency tree / graph
 
Reported: 2008-06-10 01:48 UTC by Frédéric Demians
Modified: 2022-02-07 17:47 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Cormack 2010-05-21 00:48:06 UTC 


---- Reported by frederic@tamil.fr 2008-06-10 01:48:05 ----

Basket email comes from KohaAdminAddress syspref email address.
It should be better to have a distinct syspref: OpacBasketFrom.

This should be a branch-wide syspref

http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_system_groups



---- Additional Comments From jmf@liblime.com 2008-07-20 08:26:36 ----

Changing to rel_3_2 Version



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 00:48 UTC  ---

This bug was previously known as _bug_ 2234 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=2234

Actual time not defined. Setting to 0.0
Comment 1 Katrin Fischer 2013-04-13 18:26:30 UTC 
Resetting version as the described behaviour is still the same in current versions of Koha.
Comment 2 Katrin Fischer 2019-05-04 17:39:27 UTC 
I've extended this a bit, since often these days you need to be able to set from, return-path and reply-to specifically to make sure emails can pass anti-spam mechanisms of the mail servers (especially applies to hosted Kohas).
Comment 3 Martin Renvoize (ashimema) 2020-04-09 06:01:24 UTC 
*** Bug 3679 has been marked as a duplicate of this bug. ***
Comment 4 Andrew Fuerste-Henry 2022-02-07 17:47:06 UTC 
This bug is still valid and is problematic for large multi-library systems.