[Koha-bugs] [Bug 29501] gather_print_notices.pl does not use SMTP servers

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29501

Tomás Cohen Arazi <tomascohen at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         QA Contact|testopia at bugs.koha-communit |jonathan.druart+koha at gmail.
                   |y.org                       |com
                 CC|                            |andrew at bywatersolutions.com

--- Comment #20 from Tomás Cohen Arazi <tomascohen at gmail.com> ---
(In reply to Jonathan Druart from comment #14)
> You also need to determinate which SMTP server to use (from which library?).

Hi, I've tried to learn more about the feature to answer you, Jonathan. So
correct me if I'm wrong.

The feature is not that evolved. It is designed to generate the notice(s) in a
directory (shared mount?). Print notices are generated in several ways which
should be better documented. CHECKOUT is not one of them :-D Thanks to Andrew I
now know that you can generate a print notice when trapping a hold for a patron
with no valid email.

Once you have that (it shows as 'print' on the patron's notices tab), I ran:

$ perl misc/cronjobs/gather_print_notices.pl /tmp --email
tomascohen at theke.io,andrew at bywatersolutions.com --send --html


As you will notice, the --send addresses list is not tied to any Koha feature.
You just pass the addresses... I can forsee a development in which we could add
print notices addesses configuration to libraries and a --library parameter to
the print notices, but it will still require added a library_id column to the
message_queue table.

Anyway...

The follow-up makes it work. It uses the default configured SMTP server. My
config:

 <smtp_server>
    <host>smtp.gmail.com</host>
    <port>587</port>
    <timeout>50</timeout>
    <ssl_mode>starttls</ssl_mode>
    <user_name>tomascohen at gmail.com</user_name>
    <password>xxx</password>
    <debug>1</debug>
 </smtp_server>


The password I used was generated on the 'generate applilcation password' on my
Google account. debug=1 made the SMTP session super verbose. And email arrived
at destination :-D

-- 
You are receiving this mail because:
You are watching all bug changes.