Bump truemail, simpleidn and simpleidn

[dependabot]

Bumps truemail, simpleidn and simpleidn. These dependencies needed to be updated together.
Updates truemail from 2.2.3 to 2.3.4

Release notes

Sourced from truemail's releases.

v2.3.4: Bugfix/Impossibility to use valid DNS port number

Fixed bug with impossibility to use valid dns port number. Now validation for dns port for range 1..65535 works as expected.

1. Updated Truemail::RegexConstant::REGEX_PORT_NUMBER, tests
2. Updated gem documentation
3. Changed location of CircleCI config
4. Updated gem changelog
5. Updated gem version to 2.3.4

v2.3.3

1. Updated gem development dependencies
2. Updated rubocop/codeclimate config
3. Updated CircleCI config for using multiple Ruby versions
4. Updated gem changelog
5. Updated gem version to 2.3.3

v2.3.2

1. Updated gem development dependencies
2. Updated rubocop/codeclimate config
3. Updated gem changelog
4. Updated gem version to 2.3.2

v2.3.1

1. Updated gem development dependencies
2. Updated rubocop/codeclimate config
3. Updated gem documentation, changelog
4. Updated gem version to 2.3.1

v2.3.0: Feature/Ability to use custom DNS gateway

Ability to use custom DNS gateway. Thanks @​le0pard for the great idea and @​verdi8 for feature request.

Truemail.configure do |config|
  # Optional parameter. This option will provide to use custom DNS gateway when
  # Truemail interacts with DNS. If you won't specify nameserver's ports Truemail
  # will use default DNS TCP/UDP port 53. By default Truemail uses DNS gateway
  # from system settings and this option is equal to empty array.
  config.dns = ['10.0.0.1', '10.0.0.2:5300']
end

1. Added Truemail::Dns::Resolver
2. Added Truemail::Dns::Worker
3. Updated Truemail::Configuration, tests
4. Updated Truemail::Validate::Mx, tests
5. Updated Truemail::Audit::Base
6. Updated Truemail::Audit::Dns, tests
7. Updated Truemail::Audit::Ptr, tests
8. Updated Truemail::Log::Serializer::Base, dependent tests
9. Updated namespaces for stdlib classes

... (truncated)

Changelog

Sourced from truemail's changelog.

[2.3.4] - 2021.04.16

Fixed

Fixed bug with impossibility to use valid dns port number. Now validation for dns port for range 1..65535 works as expected.

• Updated Truemail::RegexConstant::REGEX_PORT_NUMBER, tests
• Updated gem documentation
• CircleCI config moved to .circleci/config.yml

[2.3.3] - 2021.04.14

Changed

• Updated gem development dependencies
• Updated rubocop/codeclimate config
• Updated CircleCI config

[2.3.2] - 2021.03.08

Changed

• Updated gem development dependencies
• Updated rubocop/codeclimate config

[2.3.1] - 2021.02.26

Changed

• Updated gem development dependencies
• Updated rubocop/codeclimate config
• Updated tests

[2.3.0] - 2021.02.05

Added

• Ability to use custom DNS gateway. Thanks @​le0pard for the great idea and @​verdi8 for feature request.

Truemail.configure do |config|
  # Optional parameter. This option will provide to use custom DNS gateway when Truemail
  # interacts with DNS. If you won't specify nameserver's ports Truemail will use default
  # DNS TCP/UDP port 53. By default Truemail uses DNS gateway from system settings
  # and this option is equal to empty array.
  config.dns = ['10.0.0.1', '10.0.0.2:5300']
end

• Added Truemail::Dns::Resolver

... (truncated)

Commits

• 256b36c Bugfix/Impossibility to use valid DNS port number (#143)
• da717dc Technical/Update gem dependencies, CircleCI config (#141)
• 1a5bf67 Technical/Fix changelog typo (#140)
• 872b472 Technical/Update gem dependencies (#138)
• e55ca16 Technical/Update gem dependencies (#136)
• edd53c8 Technica/Update documentation (#135)
• 995b835 Technical/Refactor Configuration class (#134)
• d5f7201 Feature/Ability to use custom DNS (#131)
• 595ea27 Technical/Implement DNS resolver (#132)
• See full diff in compare view

Updates simpleidn from 0.1.1 to 0.2.1

Commits

• See full diff in compare view

Updates simpleidn from 0.1.1 to 0.2.1

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @yulgolem.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[yulgolem]

@dependabot merge