Hi Arturo,
I don't have email set up on my test installation so can't verify as the
ACCTDETAILS doesn't use the message queue. - Maybe someone else can. My
guess would have been that it would not matter as Koha creates an userid
on saving the record.
Katrin
On 31.01.2018 15:03, Arturo Longoria wrote:
Katrin,
Looking at my notes from when I tested this feature out a few weeks ago, I
noted that I had to keep the username empty and fill out both the password
fields and the primary e-mail address field in order for the e-mail to go out.
I did not have success if I also filled out the username.
-----Original Message-----
From: Koha [mailto:[email protected]] On Behalf Of Katrin Fischer
Sent: Wednesday, January 31, 2018 01:33
To: [email protected]
Subject: Re: [Koha] How does the AutoEmailOpacUser preference work?
Hi Arturo,
looking at the code I think you need to set the username, password and one of
the email addresses before saving the patron for the first time in order for
the email to be generated.
Hope this helps,
Katrin
On 08.01.2018 17:48, Barton Chittenden wrote:
Arturo,
Check the basics first -- are the email addresses valid? Are the
messages in the patron's spam folder?
Next I would check is email logs -- typically /var/log/mail.log
Grep for the email address. If you see that messages have been sent,
there's not much you can do; the issue is entirely upstream.
On the other hand, you may see that the emails are being rejected by
the upstream mail server, in which case you'll need to contact the server admin.
On Mon, Jan 8, 2018 at 11:41 AM, Arturo Longoria <
[email protected]> wrote:
Hello,
Our library enabled the AutoEmailOpacUser preference so that patrons
receive a notification of their account details when we create an
account for them via the staff client -- http://manual.koha-community.
org/17.11/en/administration.html#AutoEmailOPACUser -- and we've set
AutoEmailPrimaryAddress to use the first valid e-mail found in the account.
But we've noticed that the e-mail is not always sent when the account
includes a valid e-mail. The documentation does not mention any
specifics, so I was wondering if anyone can explain how this feature works?
It seems to be sent only if the username field is blank AND there is
a password included. I've found that if staff do not include a value
in the password fields, the e-mail is not sent. If the password
fields are filled out and staff also include a username, the e-mail is not sent.
Is this the intended behavior?
Arturo Longoria
Reference Librarian/Web Manager
Texas State Law Library
www.sll.texas.gov
_______________________________________________
Koha mailing list http://koha-community.org [email protected]
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org [email protected]
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org [email protected]
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
[email protected]
https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org
[email protected]
https://lists.katipo.co.nz/mailman/listinfo/koha
