Releases: truemail-rb/truemail
Releases · truemail-rb/truemail
v2.4.3
v2.4.2
- Fixed security vulnerability for bundler (CVE-2019-3881)
- Fixed test coverage issues
- Updated gem development dependencies
- Updated simplecov/CircleCi config
- Updated gem documentation
- Updated gem changelog
- Updated gem version to
2.4.2
v2.4.1
v2.4.0: Feature/MxBlacklist validation layer
MX blacklist layer provides checking extracted mail server(s) IP address from MX validation with predefined blacklisted IP addresses list. It can be used as a part of DEA (disposable email address) validations.
[Whitelist/Blacklist] -> [Regex validation] -> [MX validation] -> [MX blacklist validation]
Example of usage:
require 'truemail'
Truemail.configure do |config|
config.verifier_email = '[email protected]'
config.blacklisted_mx_ip_addresses = ['127.0.1.2']
end
Truemail.validate('[email protected]', with: :mx_blacklist)
=> #<Truemail::Validator:0x00007fca0c8aea70
@result=
#<struct Truemail::Validator::Result
success=false,
email="[email protected]",
domain="example.com",
mail_servers=["127.0.1.1", "127.0.1.2"],
errors={:mx_blacklist=>"blacklisted mx server ip address"},
smtp_debug=nil,
configuration=
#<Truemail::Configuration:0x00007fca0c8aeb38
@blacklisted_domains=[],
@blacklisted_mx_ip_addresses=["127.0.1.2"],
@connection_attempts=2,
@connection_timeout=2,
@default_validation_type=:smtp,
@dns=[],
@email_pattern=/(?=\A.{6,255}\z)(\A([\p{L}0-9]+[\w|\-.+]*)@((?i-mx:[\p{L}0-9]+([\-.]{1}[\p{L}0-9]+)*\.\p{L}{2,63}))\z)/,
@not_rfc_mx_lookup_flow=false,
@response_timeout=2,
@smtp_error_body_pattern=/(?=.*550)(?=.*(user|account|customer|mailbox)).*/i,
@smtp_fail_fast=false,
@smtp_safe_check=false,
@validation_type_by_domain={},
@verifier_domain="example.com",
@verifier_email="[email protected]",
@whitelist_validation=false,
@whitelisted_domains=[]>>,
@validation_type=:mx_blacklist>
- Added
Truemail::Validate::MxBlacklist
, tests - Updated
Truemail::Core
, tests - Updated
Truemail::Configuration
, tests - Updated
Truemail::Validator
- Updated
Truemail::Validate::Smtp
, tests - Updated
Truemail::Log::Serializer::Base
, dependent tests - Updated
Truemail::Log::Serializer::ValidatorText
, tests - Updated gem development dependencies
- Updated gem documentation, changelog
- Updated gem version to
2.4.0
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.
- Updated
Truemail::RegexConstant::REGEX_PORT_NUMBER
, tests - Updated gem documentation
- Changed location of CircleCI config
- Updated gem changelog
- Updated gem version to
2.3.4
v2.3.3: Technical/Update gem dependencies, CircleCI config (#141)
- Updated gem development dependencies
- Updated rubocop/codeclimate config
- Updated CircleCI config for using multiple Ruby versions
- Updated gem changelog
- Updated gem version to
2.3.3
v2.3.2
v2.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
- Added
Truemail::Dns::Resolver
- Added
Truemail::Dns::Worker
- Updated
Truemail::Configuration
, tests - Updated
Truemail::Validate::Mx
, tests - Updated
Truemail::Audit::Base
- Updated
Truemail::Audit::Dns
, tests - Updated
Truemail::Audit::Ptr
, tests - Updated
Truemail::Log::Serializer::Base
, dependent tests - Updated namespaces for stdlib classes
- Updated linters/codeclimate configs
- Updated gem runtime/development dependencies
- Updated gem documentation, changelog
- Updated gem version to
2.3.0
v2.2.3
- Removed needless
Timeout.timeout
block inTruemail::Validate::Smtp::Request#check_port
, replacedTCPSocket
toSocket
with native timeout detection. Thanks to @wikiti for idea, testing on production and clean PR #127 - Updated gem development dependencies
- Updated rubocop, reek configs
- Updated gem changelog
- Updated gem version to
2.2.3