  Release Summary for 4.3-107
  [![Generic badge](https://img.shields.io/badge/release_status-failed-red.svg)](https://shields.io/)
  Changes to branch `4.3` after version `4.3.106`.
  * [- DUPT-193: Granularize conference blackhole event bindings](https://github.com/2600hz/kazoo/pull/6532) - _by John White_
      - export published conference events
      - move published conference events to `kapi_conference`
      - update `bh_conferences` event bindings to take an event argument
      - refactor `bh_conferences` to pass * as event binding for backwards compatibility
      - [4.3] [kazoo](https://github.com/2600hz/kazoo/pull/6532)
      - [Master] [kazoo-core](https://github.com/2600hz/kazoo-core/pull/5)
      - [Master] [kazoo-ecallmgr](https://github.com/2600hz/kazoo-ecallmgr/pull/2)
      - [Master] [kazoo-blackhole](https://github.com/2600hz/kazoo-blackhole/pull/2)
  * [HELP-14436: update gen_smtp to fix multiple to header lines](https://github.com/2600hz/kazoo/pull/6528) - _by Hesaam Farhang_
      This is updating gen_smtp to have a our fix to the multiple occuring `to`
      headers by properly encoding addresses in a comma separared fashion.
      Also adding X-Teletype-Log-ID headers to identify and debug tickets about email easy.
      master: https://github.com/2600hz/kazoo/pull/6527
  * [HELP-14474: Mimic knm_other:disconnect_number/1 on placeholder carrier modules](https://github.com/2600hz/kazoo/pull/6525) - _by Harenson Henao_
      Master https://github.com/2600hz/kazoo-core/pull/1
  * [Move account creation/deletion to core module (#5266) - 4.3 request](https://github.com/2600hz/kazoo/pull/6489) - _by James Aimonetti_
      Backport to 4.3
      * move validation of accounts to core
  * [KCRO-24: address pagination issue when querying MODBs](https://github.com/2600hz/kazoo/pull/6519) - _by James Aimonetti_
      Prior, when page_size and filters are in play with a query, the
      next_db clause would not match (since PageSize wasn&#039;t
      &#039;infinity&#039;). This would lead to results being missed in the intial
      query and subsequent queries would skip over to the next group of
      results.
      Instead, consider if there is a next last key only for whether to
      query the current DB again.
  -- 2600Hz Official <packages@2600hz.com> +Sat, 09 May 2020 19:34:13 
