Hi Bill,

 I checked the templates. They seem to be formed OK; the content of the overdue 
template is:

To: ${EMAIL_RECIPIENT}
From: ${EMAIL_SENDER}
Reply-To: ${EMAIL_REPLY_TO}
Subject: Overdue Notification
${EMAIL_HEADERS}

${DATE}

${LIBRARY}

${LIBRARY_ADDRESS}

${PATRON_NAME}
${PATRON_ADDRESS}

Overdue Item

The following item is overdue:

                Title: ${TITLE}
                Author: ${AUTHOR}
                Call Number: ${CALL_NUMBER}
                Copy Barcode: ${COPY_BARCODE}
                Copy Number: ${COPY_NUMBER}

Please return item and come to the circulation desk at the Mohawk library.
Thank you.


No blank lines before the headers.


I used the use-email-outfile switch for testing. The contents of the outfile 
emails are an exact match of the contents of the template with the variable 
names being written to the file instead of the values.

For example,   ${EMAIL_RECIPIENT} appears where I assume the actual email 
addresses of the recipients should appear in the outfile.

Thanks,
Robert







From: [email protected] 
[mailto:[email protected]] On Behalf Of Bill 
Erickson
Sent: July 23, 2009 2:36 PM
To: Evergreen Development Discussion List
Subject: [OPEN-ILS-DEV] ***SPAM*** Re: ***SPAM*** RE: [OPEN-ILS-GENERAL] 
Overdue notices not sending error

My next guess would be there is something wrong with the email template.  If 
you use the --use-email-outfile switch, you can see what it's trying to send.  
Make sure the headers are well formed.  For example, no empty lines before the 
headers, one header per line,  and at least 1 empty line between the headers 
and body.

-b
On Thu, Jul 23, 2009 at 2:22 PM, Soulliere, Robert 
<[email protected]<mailto:[email protected]>> 
wrote:

Hi Bill,



All the org units seem to have valid addresses . I am using 
[email protected]<mailto:[email protected]>
 for testing. This is what is entered in the “sending email address for patron 
notices” field for all locations in the staff client.



Thanks,

Robert







From: 
[email protected]<mailto:[email protected]>
 
[mailto:[email protected]<mailto:[email protected]>]
 On Behalf Of Bill Erickson
Sent: July 23, 2009 10:17 AM
To: Evergreen Discussion Group
Cc: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] [OPEN-ILS-GENERAL] Overdue notices not sending error



Hi Robert,

I would verify any addresses configured in the staff client Library Settings 
interface (actor.org_unit_setting table) look like valid email addresses.

-b

On Thu, Jul 23, 2009 at 9:52 AM, Soulliere, Robert 
<[email protected]<mailto:[email protected]>> 
wrote:

Hi Guys,



We are still having trouble in getting automatic email notifications to 
function.



When I run the generate_circ_notices.plI get the following Warning in 
osrfsys.log:



 [2009-07-23 06:01:13] generate_circ_notices.pl 
[INFO:14462:CStoreEditor.pm:104:] editor[0|0] action.circulation.search : 
returned 1 result(s)

[2009-07-23 06:01:13] generate_circ_notices.pl 
[WARN:14462:generate_circ_notices.pl:378:] notice: unable to send overdue email 
to [email protected]<mailto:[email protected]>: 
$VAR1 = bless( {

                 'prop' => {},

                 'string' => 'Can\'t call method "address" on an undefined 
value at /usr/share/perl5/Email/Send/SMTP.pm line 24.

',

                 'type' => 'failure',

                 'errno' => 1

               }, 'Return::Value' );



It seems to not like the sender address or information, but I am not sure if it 
is the setting in the opensrf.xml file or the settings in the staff client. I 
am not getting a bounce email notification sent to the addresses specified as 
the sender email. We have correct email addresses in the sender address set up 
in both the opensrf.sml file and in the staff client location configuration.



Here is the notification section of opensrf.xml:





      <notifications>

        <!-- global mail server settings -->

        <smtp_server>localhost</smtp_server>

        
<sender_address>[email protected]<mailto:[email protected]></sender_address>



<!-- Overdue notices -->

        <overdue>



            <!-- optionally, you can define a sender address per notice type -->

            
<sender_address>[email protected]<mailto:[email protected]></sender_address>



            <!-- The system can generate an XML file of overdue notices.  This 
is the

                directory where they are stored.  Files are named 
overdue.YYYY-MM-DD.xml -->

            <notice_dir>/openils/var/data/overdue</notice_dir>

            
<combined_template>/openils/var/data/overdue_notice.example</combined_template>



            <notice>

                <!-- Notify at 7 days overdue -->

                <notify_interval>7 days</notify_interval>

                <!-- Options include always, noemail, and never.  'noemail' 
means a notice

                     will be appended to the notice file only if the patron has 
no valid email address.  -->

                <file_append>noemail</file_append>

                <!-- do we attempt email notification? -->

                <email_notify>true</email_notify>

                <!-- notice template file -->

                
<email_template>/openils/var/data/overdue_notice.example</email_template>

            </notice>

        </overdue>



        <!-- Courtesy notices -->

        <predue>

            <notice>

                <!-- All circulations that circulate between 5 and 13 days -->

                <circ_duration_range>

                    <from>5 days</from>

                    <to>13 days</to>

                </circ_duration_range>

                <!-- notify at 1 day before the due date -->

                <notify_interval>1 day</notify_interval>

                <file_append>false</file_append>

                <email_notify>true</email_notify>

                
<email_template>/openils/var/data/predue_notice.example</email_template>

            </notice>

        </predue>

      </notifications>



I was wondering of the problem would most likely relate to:



1.       The opensrf.xml file configuration

2.       Setup in the staff client.

3.        An issue with a perl script: /usr/share/perl5/Email/Send/SMTP.pm  or  
generate_circ_notices.pl



Thanks,

Robert













________________________________

This E-mail contains privileged and confidential information intended
only for the individual or entity named in the message. If the reader
of this message is not the intended recipient, or the agent responsible
to deliver it to the intended recipient, you are hereby notified that
any review, dissemination, distribution or copying of this communication
is prohibited. If this communication was received in error, please
notify the sender by reply E-mail immediately, and delete and destroy
the original message.



--
Bill Erickson
| VP, Software Development & Integration
| Equinox Software, Inc. / The Evergreen Experts
| phone: 877-OPEN-ILS (673-6457)
| email: [email protected]<mailto:[email protected]>
| web: http://esilibrary.com

________________________________
This E-mail contains privileged and confidential information intended
only for the individual or entity named in the message. If the reader
of this message is not the intended recipient, or the agent responsible
to deliver it to the intended recipient, you are hereby notified that
any review, dissemination, distribution or copying of this communication
is prohibited. If this communication was received in error, please
notify the sender by reply E-mail immediately, and delete and destroy
the original message.



--
Bill Erickson
| VP, Software Development & Integration
| Equinox Software, Inc. / The Evergreen Experts
| phone: 877-OPEN-ILS (673-6457)
| email: [email protected]<mailto:[email protected]>
| web: http://esilibrary.com

________________________________
This E-mail contains privileged and confidential information intended
only for the individual or entity named in the message. If the reader
of this message is not the intended recipient, or the agent responsible
to deliver it to the intended recipient, you are hereby notified that
any review, dissemination, distribution or copying of this communication
is prohibited. If this communication was received in error, please
notify the sender by reply E-mail immediately, and delete and destroy
the original message.

Reply via email to