smtp_mock 1.2.2 → 1.3.1

data/.reek.yml

@@ -1,31 +0,0 @@
-detectors:
-  IrresponsibleModule:
-    enabled: false
-
-  UtilityFunction:
-    exclude:
-      - SmtpMock::CommandLineArgsBuilder#to_camel_case
-      - SmtpMock::DependencyHelper#compose_command
-      - SmtpMock::ServerHelper
-      - SmtpMock::TestFramework::RSpec::Helper#smtp_mock_server
-      - SmtpMock::ContextGeneratorHelper#random_message
-      - SmtpMock::Cli::Resolver#install_to
-
-  NestedIterators:
-    exclude:
-      - SmtpMock::CommandLineArgsBuilder#define_attribute
-
-  TooManyStatements:
-    exclude:
-      - SmtpMock::Server#run
-      - SmtpMock::ServerHelper#create_fake_servers
-      - SmtpMock::Cli::Resolver#install
-      - SmtpMock::Cli::Resolver#resolve
-
-  TooManyInstanceVariables:
-    exclude:
-      - SmtpMock::Server
-
-  LongParameterList:
-    exclude:
-      - SmtpMock::ClientHelper#smtp_request

data/.rspec

@@ -1,3 +0,0 @@
---require spec_helper
---format documentation
---color

data/.rubocop.yml

@@ -1,123 +0,0 @@
-require:
-  - rubocop-rspec
-  - rubocop-performance
-
-AllCops:
-  DisplayCopNames:    true
-  DisplayStyleGuide:  true
-  TargetRubyVersion:  2.5
-  NewCops: enable
-
-# Metrics ---------------------------------------------------------------------
-
-Metrics/ClassLength:
-  Max: 150
-
-Metrics/MethodLength:
-  Max: 15
-
-Metrics/BlockLength:
-  Enabled: false
-
-Metrics/CyclomaticComplexity:
-  Enabled: false
-
-Metrics/PerceivedComplexity:
-  Enabled: false
-
-# Naming ----------------------------------------------------------------------
-
-Naming/VariableNumber:
-  Enabled: false
-
-Naming/RescuedExceptionsVariableName:
-  Enabled: false
-
-Naming/InclusiveLanguage:
-  Enabled: false
-
-# Style -----------------------------------------------------------------------
-
-Style/Documentation:
-  Enabled: false
-
-Style/DoubleNegation:
-  Enabled: false
-
-Style/EmptyCaseCondition:
-  Enabled: false
-
-Style/ParallelAssignment:
-  Enabled: false
-
-Style/RescueStandardError:
-  Enabled: false
-
-# Layout ----------------------------------------------------------------------
-
-Layout/LineLength:
-  Max: 150
-
-Layout/ClassStructure:
-  Enabled: true
-  Categories:
-    module_inclusion:
-      - include
-      - prepend
-      - extend
-  ExpectedOrder:
-      - module_inclusion
-      - constants
-      - public_class_methods
-      - initializer
-      - public_methods
-      - protected_methods
-      - private_methods
-
-Layout/EmptyLineAfterGuardClause:
-  Enabled: false
-
-# Gemspec ---------------------------------------------------------------------
-
-Gemspec/RequireMFA:
-  Enabled: false
-
-# Performance -----------------------------------------------------------------
-
-Performance/MethodObjectAsBlock:
-  Enabled: false
-
-# RSpec -----------------------------------------------------------------------
-
-RSpec/ExampleLength:
-  Enabled: false
-
-RSpec/NestedGroups:
-  Enabled: false
-
-RSpec/MultipleExpectations:
-  Enabled: false
-
-RSpec/MessageChain:
-  Enabled: false
-
-RSpec/ContextWording:
-  Enabled: false
-
-RSpec/AnyInstance:
-  Enabled: false
-
-RSpec/MessageSpies:
-  Enabled: false
-
-RSpec/MultipleDescribes:
-  Enabled: false
-
-RSpec/MultipleMemoizedHelpers:
-  Enabled: false
-
-RSpec/StubbedMock:
-  Enabled: false
-
-RSpec/VerifiedDoubleReference:
-  Enabled: false

data/.ruby-gemset

@@ -1 +0,0 @@
-smtp_mock

data/CHANGELOG.md

@@ -1,104 +0,0 @@
-# Changelog
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## [1.2.2] - 2022-10-05
-
-### Fixed
-
-- Fixed wrong semantic version comparison in `SmtpMock::Dependency#minimal_version?`
-
-### Updated
-
-- Updated gemspecs
-- Updated tests
-- Updated codeclimate/circleci configs
-- Updated gem development dependencies
-- Updated gem version
-
-## [1.2.1] - 2022-07-27
-
-### Fixed
-
-- Fixed documentation
-
-### Updated
-
-- Updated gem documentation, version
-
-## [1.2.0] - 2022-07-27
-
-### Added
-
-- Added ability to use `RSET` SMTP command
-- Added ability to configure multiple message receiving flow during one session
-- Added ability to configure SMTP command delay responses
-
-### Updated
-
-- Updated gemspecs
-- Updated tests
-- Updated rubocop/codeclimate/circleci configs
-- Updated gem development dependencies
-- Updated gem documentation, version
-
-## [1.1.0] - 2022-05-17
-
-### Added
-
-- Ability to check `smtpmock` version from cli
-
-### Updated
-
-- Updated gemspecs
-- Updated codeclimate/circleci configs
-- Updated gem development dependencies
-- Updated gem version
-
-## [1.0.1] - 2022-03-10
-
-### Added
-
-- Development environment guide
-
-### Updated
-
-- Updated gemspecs
-- Updated codeclimate/circleci configs
-- Updated gem development dependencies
-- Updated gem version
-
-## [1.0.0] - 2022-01-31
-
-### Added
-
-- Added `smtpmock` version checker
-- Added command for upgrade `smtpmock` to latest version
-- Added `SmtpMock::Error::Dependency::SMTPMOCK_MIN_VERSION`
-- Added `SmtpMock::Server#version`, tests
-
-### Updated
-
-- Updated `SmtpMock::Dependency.verify_dependencies`, tests
-- Updated `SmtpMock::Cli::Command`, tests
-- Updated gem version, documentation
-
-## [0.1.2] - 2022-01-24
-
-### Updated
-
-- Updated `SmtpMock::Cli::Command`, tests
-- Updated gem version, documentation
-
-## [0.1.1] - 2022-01-18
-
-### Updated
-
-- Updated gem documentation
-- Updated codeclimate config
-
-## [0.1.0] - 2022-01-18
-
-### Added
-
-- First release of `SmtpMock`. Thanks [@le0pard](https://github.com/le0pard) for support 🚀

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at admin@bestweb.com.ua. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

data/CONTRIBUTING.md

@@ -1,48 +0,0 @@
-# Contributing to SmtpMock
-
-Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
-
-Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
-
-## Using the issue tracker
-
-The issue tracker is the preferred channel for [issue/bug reports](#issuebug-reports), [feature requests](#feature-requests), [questions](#questions) and submitting [pull requests](#pull-requests).
-
-## Issue/bug reports
-
-A bug is a _demonstrable problem_ that is caused by the code in the repository. Good bug reports are extremely helpful - thank you!
-
-Guidelines for issue/bug reports:
-
-1. **Use the GitHub issue search** — check if the issue has already been reported
-2. **Check if the issue has been fixed** — try to reproduce it using the latest `master` or `develop` branch in the repository
-3. SmtpMock [issue template](.github/ISSUE_TEMPLATE/issue_report.md)/[bug template](.github/ISSUE_TEMPLATE/bug_report.md)
-
-A good bug report shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What would you expect to be the outcome? All these details will help people to fix any potential bugs.
-
-## Feature requests
-
-Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to *you* to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible.
-
-## Questions
-
-We're always open to a new conversations. So if you have any questions just ask us.
-
-## Pull requests
-
-Good pull requests - patches, improvements, new features - are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.
-
-**Please ask first** before embarking on any significant pull request (e.g. implementing features, refactoring code, porting to a different language), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project.
-
-Please adhere to the coding conventions used throughout a project (indentation, accurate comments, etc.) and any other requirements (such as test coverage). Not all features proposed will be added but we are open to having a conversation about a feature you are championing.
-
-Guidelines for pull requests:
-
-1. SmtpMock [pull request template](.github/PULL_REQUEST_TEMPLATE.md)
-2. Fork the repo, checkout to `develop` branch
-3. Run the tests. This is to make sure your starting point works
-4. Read our [branch naming convention](.github/BRANCH_NAMING_CONVENTION.md)
-5. Create a new branch
-6. Read our [setup development environment guide](.github/DEVELOPMENT_ENVIRONMENT_GUIDE.md)
-7. Make your changes. Please note that your PR should include tests for the new codebase!
-9. Push to your fork and submit a pull request to `develop` branch

data/Gemfile

@@ -1,5 +0,0 @@
-# frozen_string_literal: true
-
-source 'https://rubygems.org'
-git_source(:github) { |repo_name| "https://github.com/#{repo_name}" }
-gemspec

data/README.md

@@ -1,260 +0,0 @@
-# ![Ruby SmtpMock - mimic any 📤 SMTP server behaviour for your test environment with fake SMTP server](https://repository-images.githubusercontent.com/443795043/81ce5b00-0915-4dd0-93ad-88e6699e18cd)
-
-[![Maintainability](https://api.codeclimate.com/v1/badges/315c5fff7449a11868dd/maintainability)](https://codeclimate.com/github/mocktools/ruby-smtp-mock/maintainability)
-[![Test Coverage](https://api.codeclimate.com/v1/badges/315c5fff7449a11868dd/test_coverage)](https://codeclimate.com/github/mocktools/ruby-smtp-mock/test_coverage)
-[![CircleCI](https://circleci.com/gh/mocktools/ruby-smtp-mock/tree/master.svg?style=svg)](https://circleci.com/gh/mocktools/ruby-smtp-mock/tree/master)
-[![Gem Version](https://badge.fury.io/rb/smtp_mock.svg)](https://badge.fury.io/rb/smtp_mock)
-[![Downloads](https://img.shields.io/gem/dt/smtp_mock.svg?colorA=004d99&colorB=0073e6)](https://rubygems.org/gems/smtp_mock)
-[![GitHub](https://img.shields.io/github/license/mocktools/ruby-smtp-mock)](LICENSE.txt)
-[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-v1.4%20adopted-ff69b4.svg)](CODE_OF_CONDUCT.md)
-
-💎 Ruby SMTP mock - flexible Ruby wrapper over [`smtpmock`](https://github.com/mocktools/go-smtp-mock). Mimic any 📤 SMTP server behaviour for your test environment and even more.
-
-## Table of Contents
-
-- [Features](#features)
-- [Requirements](#requirements)
-- [Installation](#installation)
-- [Usage](#usage)
-  - [Dependency manager](#dependency-manager)
-    - [Available flags](#available-flags)
-  - [DSL](#dsl)
-    - [Available server options](#available-server-options)
-    - [Example of usage](#example-of-usage)
-  - [RSpec integration](#rspec-integration)
-    - [SmtpMock RSpec helper](#smtpmock-rspec-helper)
-    - [SmtpMock RSpec interface](#smtpmock-rspec-interface)
-- [Contributing](#contributing)
-- [License](#license)
-- [Code of Conduct](#code-of-conduct)
-- [Credits](#credits)
-- [Versioning](#versioning)
-- [Changelog](CHANGELOG.md)
-
-## Features
-
-- Ability to handle configurable behaviour and life cycles of SMTP mock server(s)
-- Dynamic/manual port assignment
-- Test framework agnostic (it's PORO, so you can use it outside of `RSpec`, `Test::Unit` or `MiniTest`)
-- Simple and intuitive DSL
-- RSpec integration out of the box
-- Includes easy system dependency manager
-
-## Requirements
-
-Ruby MRI 2.5.0+
-
-## Installation
-
-Add this line to your application's `Gemfile`:
-
-```ruby
-group :development, :test do
-  gem 'smtp_mock', require: false
-end
-```
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install smtp_mock
-
-Then install [`smtpmock`](https://github.com/mocktools/go-smtp-mock) as system dependency:
-
-    $ bundle exec smtp_mock -i ~
-
-## Usage
-
-### Dependency manager
-
-This gem includes easy system dependency manager. Run `bundle exec smtp_mock` with options for manage `smtpmock` system dependency.
-
-#### Available flags
-
-| Flag | Description | Example of usage |
-| --- | --- | --- |
-| `-s`, `--sudo` | Run command as sudo | `bundle exec smtp_mock -s -i ~` |
-| `-i`, `--install=PATH` | Install `smtpmock` to the existing path | `bundle exec smtp_mock -i ~/existent_dir` |
-| `-u`, `--uninstall` | Uninstall `smtpmock` | `bundle exec smtp_mock -u` |
-| `-g`, `--upgrade` | Upgrade to latest version of `smtpmock` | `bundle exec smtp_mock -g` |
-| `-v`, `--version` | Prints current version of `smtpmock` | `bundle exec smtp_mock -v` |
-| `-h`, `--help` | Prints help | `bundle exec smtp_mock -h` |
-
-### DSL
-
-#### Available server options
-
-| Example of usage kwarg | Description |
-| --- | --- |
-| `host: '0.0.0.0'` | Host address where smtpmock will run. It's equal to 127.0.0.1 by default |
-| `port: 2525` | Server port number. If not specified it will be assigned dynamically |
-| `log: true` | Enables log server activity. Disabled by default |
-| `session_timeout: 60` | Session timeout in seconds. It's equal to 30 seconds by default |
-| `shutdown_timeout: 5` | Graceful shutdown timeout in seconds. It's equal to 1 second by default |
-| `fail_fast: true` | Enables fail fast scenario. Disabled by default |
-| `multiple_message_receiving: true` | Enables multiple message receiving scenario. Disabled by default |
-| `blacklisted_helo_domains: %w[a.com b.com]` | Blacklisted `HELO` domains |
-| `blacklisted_mailfrom_emails: %w[a@a.com b@b.com]` | Blacklisted `MAIL FROM` emails |
-| `blacklisted_rcptto_emails: %w[c@c.com d@d.com]` | blacklisted `RCPT TO` emails |
-| `not_registered_emails: %w[e@e.com f@f.com]` | Not registered (non-existent) `RCPT TO` emails |
-| `response_delay_helo: 2` | `HELO` response delay in seconds. It's equal to 0 seconds by default |
-| `response_delay_mailfrom: 2` | `MAIL FROM` response delay in seconds. It's equal to 0 seconds by default |
-| `response_delay_rcptto: 2` | `RCPT TO` response delay in seconds. It's equal to 0 seconds by default |
-| `response_delay_data: 2` | `DATA` response delay in seconds. It's equal to 0 seconds by default |
-| `response_delay_message: 2` | Message response delay in seconds. It's equal to 0 seconds by default |
-| `response_delay_rset: 2` | `RSET` response delay in seconds. It's equal to 0 seconds by default |
-| `response_delay_quit: 2` | `QUIT` response delay in seconds. It's equal to 0 seconds by default |
-| `msg_size_limit: 42` | Message body size limit in bytes. It's equal to 10485760 bytes by default |
-| `msg_greeting: 'Greeting message'` | Custom server greeting message |
-| `msg_invalid_cmd: 'Invalid command message'` | Custom invalid command message |
-| `msg_invalid_cmd_helo_sequence: 'Invalid command HELO sequence message'` | Custom invalid command `HELO` sequence message |
-| `msg_invalid_cmd_helo_arg: 'Invalid command HELO argument message'` | Custom invalid command `HELO` argument message |
-| `msg_helo_blacklisted_domain: 'Blacklisted domain message'` | Custom `HELO` blacklisted domain message |
-| `msg_helo_received: 'HELO received message'` | Custom `HELO` received message |
-| `msg_invalid_cmd_mailfrom_sequence: 'Invalid command MAIL FROM sequence message'` | Custom invalid command `MAIL FROM` sequence message |
-| `msg_invalid_cmd_mailfrom_arg: 'Invalid command MAIL FROM argument message'` | Custom invalid command `MAIL FROM` argument message |
-| `msg_mailfrom_blacklisted_email: 'Blacklisted email message'` | Custom `MAIL FROM` blacklisted email message |
-| `msg_mailfrom_received: 'MAIL FROM received message'` | Custom `MAIL FROM` received message |
-| `msg_invalid_cmd_rcptto_sequence: 'Invalid command RCPT TO sequence message'` | Custom invalid command `RCPT TO` sequence message |
-| `msg_invalid_cmd_rcptto_arg: 'Invalid command RCPT TO argument message'` | Custom invalid command `RCPT TO` argument message |
-| `msg_rcptto_not_registered_email: 'Not registered email message'` | Custom `RCPT TO` not registered email message |
-| `msg_rcptto_blacklisted_email: 'Blacklisted email message'` | Custom `RCPT TO` blacklisted email message |
-| `msg_rcptto_received: 'RCPT TO received message'` | Custom `RCPT TO` received message |
-| `msg_invalid_cmd_data_sequence: 'Invalid command DATA sequence message'` | Custom invalid command `DATA` sequence message |
-| `msg_data_received: 'DATA received message'` | Custom `DATA` received message |
-| `msg_msg_size_is_too_big: 'Message size is too big'` | Custom size is too big message |
-| `msg_invalid_cmd_rset_sequence: 'Invalid command RSET sequence message'` | Custom invalid command `RSET` sequence message |
-| `msg_invalid_cmd_rset_arg: 'Invalid command RSET argument message'` | Custom invalid command `RSET` argument message |
-| `msg_rset_received: 'RSET received message'` | Custom `RSET` received message |
-| `msg_quit_cmd: 'Quit command message'` | Custom quit command message |
-
-#### Example of usage
-
-```ruby
-# Public SmtpMock interface
-# Without kwargs creates SMTP mock server with default behaviour.
-# A free port for server will be randomly assigned in the range
-# from 49152 to 65535. Returns current smtp mock server instance
-smtp_mock_server = SmtpMock.start_server(not_registered_emails: %w[user@example.com]) # => SmtpMock::Server instance
-
-# returns current smtp mock server port
-smtp_mock_server.port # => 55640
-
-# returns current smtp mock server port
-smtp_mock_server.pid # => 38195
-
-# returns current smtp mock server version
-smtp_mock_server.version # => '1.5.2'
-
-# interface for graceful shutdown current smtp mock server
-smtp_mock_server.stop # => true
-
-# interface for force shutdown current smtp mock server
-smtp_mock_server.stop! # => true
-
-# interface to check state of current smtp mock server
-# returns true if server is running, otherwise returns false
-smtp_mock_server.active? # => true
-
-# returns list of running smtp mock servers
-SmtpMock.running_servers # => [SmtpMock::Server instance]
-
-# interface to stop all running smtp mock servers
-SmtpMock.stop_running_servers! # => true
-```
-
-### RSpec integration
-
-Require this either in your Gemfile or in RSpec's support scripts. So either:
-
-```ruby
-# Gemfile
-
-group :test do
-  gem 'rspec'
-  gem 'smtp_mock', require: 'smtp_mock/test_framework/rspec'
-end
-```
-
-or
-
-```ruby
-# spec/support/config/smtp_mock.rb
-
-require 'smtp_mock/test_framework/rspec'
-```
-
-#### SmtpMock RSpec helper
-
-Just add `SmtpMock::TestFramework::RSpec::Helper` if you wanna use shortcut `smtp_mock_server` for SmtpMock server instance inside of your `RSpec.describe` blocks:
-
-```ruby
-# spec/support/config/smtp_mock.rb
-
-RSpec.configure do |config|
-  config.include SmtpMock::TestFramework::RSpec::Helper
-end
-```
-
-```ruby
-# your awesome smtp_client_spec.rb
-
-RSpec.describe SmtpClient do
-  subject(:smtp_response) do
-    described_class.call(
-      host: 'localhost',
-      port: smtp_mock_server.port,
-      mailfrom: mailfrom,
-      rcptto: rcptto,
-      message: message
-    )
-  end
-
-  let(:mailfrom) { 'sender@example.com' }
-  let(:rcptto) { 'receiver@example.com' }
-  let(:message) { 'Email message context' }
-  let(:expected_response_message) { '250 Custom successful response' }
-
-  before { smtp_mock_server(msg_msg_received: expected_response_message) }
-
-  it do
-    expect(smtp_response).to be_success
-    expect(smtp_response).to have_status(expected_response_status)
-    expect(smtp_response).to have_message_context(expected_response_message)
-  end
-end
-```
-
-#### SmtpMock RSpec interface
-
-If you won't use `SmtpMock::TestFramework::RSpec::Helper` you can use `SmtpMock::TestFramework::RSpec::Interface` directly instead:
-
-```ruby
-SmtpMock::TestFramework::RSpec::Interface.start_server  # creates and runs SmtpMock server instance
-SmtpMock::TestFramework::RSpec::Interface.stop_server!  # stops and clears current SmtpMock server instance
-SmtpMock::TestFramework::RSpec::Interface.clear_server! # clears current SmtpMock server instance
-```
-
-## Contributing
-
-Bug reports and pull requests are welcome on GitHub at https://github.com/mocktools/ruby-smtp-mock. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct. Please check the [open tickets](https://github.com/mocktools/ruby-smtp-mock/issues). Be sure to follow Contributor Code of Conduct below and our [Contributing Guidelines](CONTRIBUTING.md).
-
-## License
-
-The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
-
-## Code of Conduct
-
-Everyone interacting in the SmtpMock project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](CODE_OF_CONDUCT.md).
-
-## Credits
-
-- [The Contributors](https://github.com/mocktools/ruby-smtp-mock/graphs/contributors) for code and awesome suggestions
-- [The Stargazers](https://github.com/mocktools/ruby-smtp-mock/stargazers) for showing their support
-
-## Versioning
-
-SmtpMock uses [Semantic Versioning 2.0.0](https://semver.org)

data/Rakefile

@@ -1,8 +0,0 @@
-# frozen_string_literal: true
-
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-
-RSpec::Core::RakeTask.new(:spec)
-
-task default: :spec