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

David Liddle <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #14 from David Liddle <[email protected]> ---
(In reply to Thomas Klausner from comment #13)
> Coming here from the thread "gmail account disabled - how to proceed?" on
> the koha mailing list, where someone posted that they where blocked by
> Google because of a high number of bounced messages.
> 
> In another non-Koha project I have to send a lot of mail and we're using
> self-hosted mail infra. We learned that we have to very closely monitor
> bounces and do not send further mails to users that have permanent bounces.
> 
> We do this by actually handling the incoming bounce mails, extracting the
> bounced email and setting the users to "blocked". And then we don't send
> them any more mails (at least until they change their email or we manually
> unblock them after inspecting the cause)
> 
> I'm not sure how and if something like this would make sense to add to Koha.
> It would be rather complex, because getting the bounces greatly depends on
> the mail infra you use. We found that a web-hook / API-Endpoint that takes
> the email address and message id and then find the mail and set the user to
> "bounced" works quite well: Some of the bigger transactional mail providers
> will hit the web-hook; and for self-hosted mail infra we wrote an incoming
> mail parser that extracts the info and then hits the web-hook.
> 
> BTW, regarding the original question: There is no way to check if a mail
> exists except sending a mail and checking for a bounce. Which is NOT
> RECOMMENDED!!

I'm with Thomas here... I think that a means of parsing bounces, flagging the
relevant accounts, and disabling notifications for those patrons is a great
idea. That keeps the process internal and effective.

Using an external service to check address validity would pose issues of
privacy, among other things.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to