There is a system preferenece, AutoEmailPrimaryAddress, that determines which email is used to send notices. One of the options, "first valid", checks the emails in the order: primary, secondary, alternate. The first field that is populated with a valid email address (on a per-user basis) is used to send the notices. I recommend you verify that setting first, then proceed from there. Cheers, -Ian On Tue, Dec 6, 2011 at 2:27 AM, R Sunil Kumar <sunil.kumar@ecoleglobal.com>wrote:
Dear All,
I am also facing the same problem for email notices. Notices are only received by member who has given the primary email id for Koha 3.04
My problem is that, email are not send to all the patron who's email id is given in the primary section, email is going to only ONE patron. Eventhough primary email id are given in some accounts. Secondly majority of the email id is given in the secondary email ID section and koha is not picking the secondary email id for sending the reminder.
Can anybody have a solution/suggestion.
Thanks and Regards
R Sunil Kumar Library Technologist +91-9686576695
-----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of koha-request@lists.katipo.co.nz Sent: 06 December 2011 04:30 To: koha@lists.katipo.co.nz Subject: Koha Digest, Vol 74, Issue 12
Send Koha mailing list submissions to koha@lists.katipo.co.nz
To subscribe or unsubscribe via the World Wide Web, visit http://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request@lists.katipo.co.nz
You can reach the person managing the list at koha-owner@lists.katipo.co.nz
When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..."
Today's Topics:
1. Re: Problems with Apache when trying to access Koha Admin (culiforge) 2. Primary & secondary email addresses (Cab Vinton) 3. Re: Improving permissions on lists (virtual shelves) (Robin Sheat) 4. Re: Search by copy number not working properly (Marijana Glavica)
----------------------------------------------------------------------
Message: 1 Date: Mon, 5 Dec 2011 10:59:48 -0800 (PST) From: culiforge <culinaryforge@gmail.com> To: koha@lists.katipo.co.nz Subject: Re: [Koha] Problems with Apache when trying to access Koha Admin Message-ID: <1323111588693-5049780.post@n5.nabble.com> Content-Type: text/plain; charset=us-ascii
I found this post and it's exactly the issue I'm having. the problem is... I'm new to Linux, koha and mysql and therefore don't quite know how to follow through on the solution given.
speak slowly and use small words and I will be grateful.
cul
-- View this message in context:
http://koha.1045719.n5.nabble.com/Problems-with-Apache-when-trying-to-access -Koha-Admin-tp5037373p5049780.html Sent from the Koha-general mailing list archive at Nabble.com.
------------------------------
Message: 2 Date: Mon, 5 Dec 2011 16:46:59 -0500 From: Cab Vinton <bibliwho@gmail.com> To: Koha list <koha@lists.katipo.co.nz> Subject: [Koha] Primary & secondary email addresses Message-ID: <CABW43UQ6uxqWs77WA_Q+30Gs0uTS9we=4h9q3BjhWfTSKg6g9w@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Does anyone know how Koha (3.04.02) handles emailed notices when there is a secondary email address, but no primary address?
My suspicion is that no notice is sent out & the notice is bundled into the compiled "Overdue Notices" message to the admin for patrons w/out addresses ...
Cheers,
Cab Vinton, Director Sanbornton Public Library Sanbornton, NH
"Politeness and consideration for others is like investing pennies and getting dollars back." Thomas Sowell
------------------------------
Message: 3 Date: Tue, 06 Dec 2011 11:35:50 +1300 From: Robin Sheat <robin@catalyst.net.nz> To: koha@lists.katipo.co.nz Subject: Re: [Koha] Improving permissions on lists (virtual shelves) Message-ID: <1323124550.18798.13.camel@zarathud> Content-Type: text/plain; charset="utf-8"
BWS Johnson schreef op ma 05-12-2011 om 03:00 [-0800]:
I'm still struggling with this. While I realise that some Patrons who shall remain nameless and spammers might create stuff we don't want floating round the OPAC, some of the best bibliographies are created by Patrons, not Staff. I feel like at the bare minimum, there needs be a way for a Patron to send their list to Staff to be made public. I like just giving them the ability to make lists public better, though.
Yeah, I'm not a fan of universally preventing the public from creating lists. It makes sense in a lot of situations, however for e.g. company libraries, it's able to be quite useful if staff can build lists for a topic.
-- Robin Sheat Catalyst IT Ltd. ? +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D