safety_mailer 0.0.10 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 69e8be8ab3ca951f1e657fc3c35a76e361df35b2
-  data.tar.gz: 58def558830485c7a746b692aa38be37ab9cd67a
+SHA256:
+  metadata.gz: f938efe60a4a91fe62371d6d49ac6d17b30caada23b12dd7ff12e3043a18fc7c
+  data.tar.gz: c28ec8454f91e49e5376bc43c438dafe718cd145789226b915526107811691fa
 SHA512:
-  metadata.gz: 7ced894bcfbcbd623ee3259675c239e8b2b791afa55a0a34cb2fa512e00cc8ab007d5f0b08716eee6bd6ba5fb6ea066af61bb4adee514856d23af3a549e22609
-  data.tar.gz: 1d8764ed50b0a072348a8e1bbcdb45d13a0f1f859ebad87df03b27c626721eb3b3fd581ef1658bc9f29c2132d6c398ad67eeb29d7f2b15884508df161abe5a81
+  metadata.gz: 4a6e8a3831a85672c5f67f6385782361dc6799bec3a8eab18336fef9ff8913a617eab039fb1a30f175078f7930b1c29434eabaf356f20bf00822cd627d8ae109
+  data.tar.gz: 6d61949b2ad02dba4bd4aeb82e05434fb89f1deaab0b7d0e38d0231bc331601006b740649c0ea1079c21103f4fee398d300a395f1d8fbf9881237fb6e1c6cf6e

data/.rubocop.yml

@@ -0,0 +1,12 @@
+plugins:
+  - rubocop-rake
+  - rubocop-minitest
+
+AllCops:
+  NewCops: disable
+
+Metrics/MethodLength:
+  Max: 30
+
+Metrics/AbcSize:
+  Max: 25

data/CHANGELOG.md

@@ -0,0 +1,46 @@
+## [Unreleased]
+
+## [0.1.0] - 2025-09-01
+
+- Rebuilding on a modern gem framework
+- Shiny new logo!
+- Port testing to minitest
+- Fix support for non-rails (Mail gem) usage
+- Add support for custom loggers (e.g., non-rails)
+
+## [0.0.10] - 2014-12-04
+
+- Support use separate from Mail gem
+
+## [0.0.9] - 2014-10-23
+
+- Make `whitelisted?` public
+
+## [0.0.8] - 2014-06-14
+
+- Added support for ActionMailer custom delivery methods
+
+## [0.0.7] - 2013-06-10
+
+- Development enhancements
+
+## [0.0.6] - 2013-06-10
+
+- SendGrid support
+- X-SMTPAPI support
+
+## [0.0.5] - 2013-06-10
+
+- Doc update
+
+## [0.0.4] - 2012-03-13
+
+- Mail gem compatibility fix
+
+## [0.0.3] - 2012-02-12
+
+- Rails 3.1 compatibility
+
+## [0.0.2] - 2012-02-09
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2025 Bill Kirtley
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,147 @@
+# SafetyMailer
+
+![Logo](assets/logo_ruby_hardhat.png)
+
+Restrict email sent by your application to only approved domains or accounts.
+
+Specify a domain (or set of domains, or magic word in email address) email is allowed to go to, and email to all other domains is silently dropped.
+
+This is useful for testing or staging environments where you want to be certain email to real customers doesn't escape the lab.
+
+Layered on the Mail gem, so Rails >= 3.0 applications (as well as plain ruby apps) can use safety_mailer.
+
+## Installation
+
+Add the gem to your +Gemfile+, specifying groups (probably not production) to include it in.
+
+```ruby
+gem "safety_mailer", :group => :development
+```
+
+Don't forget to `bundle install` to install
+
+In your environment file `config/environments/development.rb` configure it, and some regular expressions.
+
+```ruby
+config.action_mailer.delivery_method = :safety_mailer
+config.action_mailer.safety_mailer_settings = {
+  allowed_matchers: [ /mydomain.com/, /mytestacct@gmail.com/, /\+safety_mailer@/ ],
+  delivery_method: :smtp,
+  delivery_method_settings: {
+    address: "smtp.mydomain.com",
+    port: 25,
+    domain: "mydomain.com",
+    authentication: :plain,
+    user_name: "mydomain_mailer@mydomain.com",
+    password: "password"
+  }
+}
+```
+
+## Logging
+
+SafetyMailer supports custom logging to help you monitor email filtering decisions. By default, SafetyMailer will automatically use `Rails.logger` if available, or remain silent if no logger is configured.
+
+### Rails Applications
+
+In Rails applications, SafetyMailer automatically uses `Rails.logger` by default. You'll see log messages like:
+
+```
+SafetyMailer: Processing 3 recipient(s) - 2 allowed, 1 suppressed
+SafetyMailer: Allowed delivery for user@mydomain.com
+SafetyMailer: Suppressed delivery for user@external.com (no matching allowed pattern)
+SafetyMailer: Delivering email to 2 allowed recipient(s)
+```
+
+### Custom Logger Configuration
+
+You can specify a custom logger in your configuration:
+
+```ruby
+require 'logger'
+
+# Create a custom logger
+safety_logger = Logger.new(Rails.root.join('log', 'safety_mailer.log'))
+
+config.action_mailer.delivery_method = :safety_mailer
+config.action_mailer.safety_mailer_settings = {
+  allowed_matchers: [ /mydomain.com/, /mytestacct@gmail.com/ ],
+  logger: safety_logger,  # Custom logger
+  delivery_method: :smtp,
+  # ... other settings
+}
+```
+
+### Disabling Logging
+
+To disable logging entirely, set the logger to `nil`:
+
+```ruby
+config.action_mailer.safety_mailer_settings = {
+  allowed_matchers: [ /mydomain.com/ ],
+  logger: nil,  # Disable all logging
+  delivery_method: :smtp,
+  # ... other settings
+}
+```
+
+### Non-Rails Applications
+
+For non-Rails applications, SafetyMailer remains silent by default. You can enable logging by providing a custom logger:
+
+```ruby
+require "safety_mailer"
+require "logger"
+
+# Configure with custom logger
+custom_logger = Logger.new(STDOUT)
+
+Mail.defaults do
+  delivery_method SafetyMailer::Carrier, {
+    allowed_matchers: [ /mydomain.com/ ],
+    logger: custom_logger,
+    delivery_method: :smtp
+  }
+end
+```
+
+Now, email to `anyone@mydomain.com`, `mytestacct@gmail.com`, `bob+safety_mailer@yahoo.com` all get sent, and email to other recipients (like the real users in the production database you copied to a test server) is suppressed.
+
+## Non-Rails
+
+Any user of the Mail gem can configure safety_mailer:
+
+```ruby
+require "safety_mailer"
+Mail.defaults do
+delivery_method SafetyMailer::Carrier, {
+... same settings as above
+}
+end
+```
+
+## Non-Mail
+
+If you're not using the Mail gem (or use it sometimes but want to use the same logic / configuration in other contexts), you can filter directly:
+
+```
+filtered_array = SafetyMailer::Carrier.new(ActionMailer::Base.safety_mailer_settings).filter(unfiltered_email_addresses)
+```
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/cluesque/safety_mailer. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/cluesque/safety_mailer/blob/main/CODE_OF_CONDUCT.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 SafetyMailer project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/cluesque/safety_mailer/blob/main/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -1,26 +1,16 @@
-#!/usr/bin/env rake
-require "bundler/gem_tasks"
-require 'rspec/core/rake_task'
-Bundler::GemHelper.install_tasks
+# frozen_string_literal: true
 
-task :console do
-  Rake::Task["build"].invoke
-  Rake::Task["install"].invoke
-  puts "Loading development console..."
-  system("irb -r safety_mailer")
-end
+require 'bundler/gem_tasks'
+require 'rake/testtask'
 
-task :help do
-  puts "Available rake tasks: "
-  puts "rake console - Run a IRB console with all enviroment loaded"
-  puts "rake spec - Run specs"
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'test'
+  t.libs << 'lib'
+  t.test_files = FileList['test/**/*_test.rb', 'test/*_test.rb']
 end
 
-task :spec do
-  desc "Run all specs with rcov"
-  RSpec::Core::RakeTask.new(:spec) do |t|
-    t.pattern = "spec/**/*_spec.rb"
-  end
-end
+require 'rubocop/rake_task'
+
+RuboCop::RakeTask.new
 
-task :default => [:spec]
+task default: %i[test rubocop]

data/lib/safety_mailer/railtie.rb

@@ -1,4 +1,7 @@
+# frozen_string_literal: true
+
 module SafetyMailer
+  # Defining a Railtie to hook into Rails initialization process
   class Railtie < Rails::Railtie
     config.before_configuration do
       ActionMailer::Base.add_delivery_method :safety_mailer, SafetyMailer::Carrier

data/lib/safety_mailer/safety_mailer.rb

@@ -1,27 +1,46 @@
+# frozen_string_literal: true
+
+require 'json'
+
 module SafetyMailer
+  # Carrier class implements a delivery method for ActionMailer
   class Carrier
-    attr_accessor :matchers, :settings, :mail
+    attr_accessor :matchers, :settings, :mail, :logger
 
     def initialize(params = {})
       self.matchers = params[:allowed_matchers] || []
       self.settings = params[:delivery_method_settings] || {}
-      delivery_method = params[:delivery_method] || :smtp
-      @delivery_method = ActionMailer::Base.delivery_methods[delivery_method].new(settings)
+      self.logger = determine_logger(params[:logger])
+      delivery_method_name = params[:delivery_method] || :smtp
+      @delivery_method = if defined?(ActionMailer)
+                           ActionMailer::Base.delivery_methods[delivery_method_name].new(settings)
+                         else
+                           Mail::Configuration.instance.lookup_delivery_method(delivery_method_name).new(settings)
+                         end
       @sendgrid_options = {}
     end
 
     def deliver!(mail)
       self.mail = mail
-      allowed = filter(recipients)
+      original_recipients = recipients
+      allowed = filter(original_recipients)
+
+      log_delivery_summary(original_recipients, allowed)
 
       if allowed.empty?
-        log "*** safety_mailer - no allowed recipients ... suppressing delivery altogether"
+        log 'SafetyMailer: No allowed recipients found - suppressing delivery altogether'
         return
       end
 
-      mail['X-SMTPAPI'].value = prepare_sendgrid_delivery(allowed) if sendgrid?
+      if sendgrid?
+        sendgrid_header = prepare_sendgrid_delivery(allowed)
+        mail.header.fields.delete_if { |f| f.name =~ /X-SMTPAPI/i }
+        mail['X-SMTPAPI'] = sendgrid_header
+        log 'SafetyMailer: Updated SendGrid header with filtered recipients'
+      end
       mail.to = allowed
 
+      log "SafetyMailer: Delivering email to #{allowed.size} allowed recipient(s)"
       @delivery_method.deliver!(mail)
     end
 
@@ -30,15 +49,17 @@ module SafetyMailer
     end
 
     def filter(addresses)
+      return [] if addresses.nil? || addresses.empty?
+
       allowed, rejected = addresses.partition { |r| whitelisted?(r) }
 
-      rejected.each { |addr| log "*** safety_mailer delivery suppressed for #{addr}" }
-      allowed.each { |addr| log "*** safety_mailer delivery allowed for #{addr}" }
+      rejected.each { |addr| log "SafetyMailer: Suppressed delivery for #{addr} (no matching allowed pattern)" }
+      allowed.each { |addr| log "SafetyMailer: Allowed delivery for #{addr}" }
 
       allowed
     end
 
-  private
+    private
 
     def recipients
       sendgrid?
@@ -48,10 +69,11 @@ module SafetyMailer
 
     def sendgrid?
       @sendgrid ||= !!if mail['X-SMTPAPI']
-        @sendgrid_options = JSON.parse(mail['X-SMTPAPI'].value)
-      end
+                        @sendgrid_options = JSON.parse(mail['X-SMTPAPI'].value)
+                      end
     rescue JSON::ParserError
-      log "*** safety_mailer was unable to parse the X-SMTPAPI header"
+      log 'SafetyMailer: Unable to parse X-SMTPAPI header - invalid JSON format'
+      false
     end
 
     # Handles clean-up for additional SendGrid features that may be required
@@ -67,12 +89,11 @@ module SafetyMailer
       # whitelisted addresses.
       #
       # @see http://docs.sendgrid.com/documentation/api/smtp-api/developers-guide/substitution-tags/
-      if substitutions = @sendgrid_options['sub']
+      if (substitutions = @sendgrid_options['sub'])
         substitutions.each do |template, values|
           values = recipients.zip(values).map do |addr, value|
             value if addresses.include?(addr)
           end
-
           substitutions[template] = values.compact
         end
 
@@ -83,8 +104,26 @@ module SafetyMailer
     end
 
     def log(msg)
-      Rails.logger.warn(msg) if defined?(Rails)
+      return unless logger
+
+      logger.warn(msg)
+    end
+
+    def determine_logger(custom_logger)
+      return custom_logger if custom_logger
+      return Rails.logger if defined?(Rails) && Rails.respond_to?(:logger) && Rails.logger
+
+      nil
     end
 
+    def log_delivery_summary(original_recipients, allowed_recipients)
+      return unless logger
+
+      total = original_recipients.size
+      allowed = allowed_recipients.size
+      suppressed = total - allowed
+
+      log "SafetyMailer: Processing #{total} recipient(s) - #{allowed} allowed, #{suppressed} suppressed"
+    end
   end
 end

data/lib/safety_mailer/version.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 module SafetyMailer
-  VERSION = '0.0.10'
-end
+  VERSION = '0.1.0'
+end

data/lib/safety_mailer.rb

@@ -1,3 +1,5 @@
-require "safety_mailer/safety_mailer"
-require "safety_mailer/version"
-require "safety_mailer/railtie" if defined? Rails
+# frozen_string_literal: true
+
+require_relative 'safety_mailer/version'
+require_relative 'safety_mailer/safety_mailer'
+require_relative 'safety_mailer/railtie' if defined? Rails

data/sig/safety_mailer.rbs

@@ -0,0 +1,4 @@
+module SafetyMailer
+  VERSION: String
+  # See the writing guide of rbs: https://github.com/ruby/rbs#guides
+end

metadata

@@ -1,108 +1,57 @@
 --- !ruby/object:Gem::Specification
 name: safety_mailer
 version: !ruby/object:Gem::Version
-  version: 0.0.10
+  version: 0.1.0
 platform: ruby
 authors:
 - Bill Kirtley
-autorequire: 
-bindir: bin
+bindir: exe
 cert_chain: []
-date: 2014-12-04 00:00:00.000000000 Z
-dependencies:
-- !ruby/object:Gem::Dependency
-  name: rspec
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ~>
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ~>
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: mail
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ~>
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ~>
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: rake
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ~>
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ~>
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: actionmailer
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ~>
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ~>
-      - !ruby/object:Gem::Version
-        version: '0'
-description: Specify a domain (or set of domains, or magic word in email address)
-  email is allowed to go to, and email to all other domains is silently dropped. Useful
-  for testing and staging environments.
-email: bill.kirtley@gmail.com
+date: 1980-01-02 00:00:00.000000000 Z
+dependencies: []
+description: Restrict email sent by your application. Useful for testing and staging
+  environments.
+email:
+- bill.kirtley@gmail.com
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- Gemfile
-- README.rdoc
+- ".rubocop.yml"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- LICENSE.txt
+- README.md
 - Rakefile
+- assets/logo_ruby_hardhat.png
 - lib/safety_mailer.rb
 - lib/safety_mailer/railtie.rb
 - lib/safety_mailer/safety_mailer.rb
 - lib/safety_mailer/version.rb
+- sig/safety_mailer.rbs
 homepage: http://github.com/cluesque/safety_mailer
 licenses:
 - MIT
-metadata: {}
-post_install_message: 
+metadata:
+  homepage_uri: http://github.com/cluesque/safety_mailer
+  source_code_uri: http://github.com/cluesque/safety_mailer
+  changelog_uri: http://github.com/cluesque/safety_mailer/blob/master/CHANGELOG.md
+  rubygems_mfa_required: 'true'
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 2.7.5
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.4.2
-signing_key: 
+rubygems_version: 3.6.9
 specification_version: 4
 summary: Restrict email sent by your application to only approved domains or accounts.
 test_files: []

data/Gemfile

@@ -1,4 +0,0 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in  safety_mailer.gemspec
-gemspec

data/README.rdoc

@@ -1,60 +0,0 @@
-== safety_mailer
-
-Restrict email sent by your application to only approved domains or accounts.
-
-Specify a domain (or set of domains, or magic word in email address) email is allowed to go to, and email to all other domains is silently dropped.
-
-This is useful for testing or staging environments where you want to be certain email to real customers doesn't escape the lab.
-
-Layered on the Mail gem, so Rails >= 3.0 applications can use safety_mailer.
-
-== Rails >= 3.0
-
-Add the gem to your +Gemfile+, specifying groups (probably not production) to include it in.
-
-  gem "safety_mailer", :group => :development
-
-Don't forget to <tt>bundle install</tt> to install
-
-In your environment file <tt>config/environments/development.rb</tt> configure it, and some regular expressions.
-
-  config.action_mailer.delivery_method = :safety_mailer
-  config.action_mailer.safety_mailer_settings = {
-    allowed_matchers: [ /mydomain.com/, /mytestacct@gmail.com/, /super_secret_test/ ],
-    delivery_method: :smtp,
-    delivery_method_settings: {
-      :address => "smtp.mydomain.com",
-      :port => 25,
-      :domain => "mydomain.com",
-      :authentication => :plain,
-      :user_name => "mydomain_mailer@mydomain.com",
-      :password => "password"
-    }
-  }
-
-... and now, email to anyone@mydomain.com, mytestacct@gmail.com, bob+super_secret_test@yahoo.com all get sent
-and email to other recipients (like the real users in the production database you copied to a test server) is suppressed.
-
-== Non-Rails
-
-Any user of the Mail gem can configure safety_mailer:
-
-  require "safety_mailer"
-  Mail.defaults do
-    delivery_method SafetyMailer::Carrier, {
-      ... same settings as above
-    }
-  end
-
-== Non-Mail
-
-If you're not using the Mail gem (or use it sometimes but want to use the same logic / configuration in other contexts),
-you can filter directly:
-
-  filtered_array = SafetyMailer::Carrier.new(ActionMailer::Base.safety_mailer_settings).filter(unfiltered_email_addresses)
-
-== License
-
-safety_mailer is released under the MIT license:
-
-* http://www.opensource.org/licenses/MIT