sanitize_email 1.0.6 → 1.0.7

data/CHANGELOG.md

@@ -1,3 +1,9 @@
+Version 1.0.7 - AUG.06.2012
+
+* \[Bug Fix\] Stripping the message headers before appending new headers.
+  - In a scenario where there is a trailing space, adding the newline before we append results in a blank header which throws an error as illegal by Eric Musgrove
+* Minor updates to Gemspec by Peter Boling
+
 Version 1.0.6 - JAN.25.2013
 
 * \[New Feature\] use_actual_environment_prepended_to_subject by [altonymous](https://github.com/Altonymous)

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    sanitize_email (1.0.5)
+    sanitize_email (1.0.6)
 
 GEM
   remote: http://rubygems.org/

data/README.md

@@ -43,22 +43,26 @@ If you install this gem on a production server (which I don't always do), you ca
 
 ## Install Like a Boss
 
-  [sudo] gem install sanitize_email
+```
+[sudo] gem install sanitize_email
+```
 
 ## Setup With An Axe
 
 Customize and add to an initializer:
 
-        SanitizeEmail::Config.configure do |config|
-          config[:sanitized_to] =         'to@sanitize_email.org'
-          config[:sanitized_cc] =         'cc@sanitize_email.org'
-          config[:sanitized_bcc] =        'bcc@sanitize_email.org'
-          # run/call whatever logic should turn sanitize_email on and off in this Proc:
-          config[:activation_proc] =      Proc.new { %w(development test).include?(Rails.env) }
-          config[:use_actual_email_prepended_to_subject] = true         # or false
-          config[:use_actual_environment_prepended_to_subject] = true   # or false
-          config[:use_actual_email_as_sanitized_user_name] = true       # or false
-        end
+```
+SanitizeEmail::Config.configure do |config|
+  config[:sanitized_to] =         'to@sanitize_email.org'
+  config[:sanitized_cc] =         'cc@sanitize_email.org'
+  config[:sanitized_bcc] =        'bcc@sanitize_email.org'
+  # run/call whatever logic should turn sanitize_email on and off in this Proc:
+  config[:activation_proc] =      Proc.new { %w(development test).include?(Rails.env) }
+  config[:use_actual_email_prepended_to_subject] = true         # or false
+  config[:use_actual_environment_prepended_to_subject] = true   # or false
+  config[:use_actual_email_as_sanitized_user_name] = true       # or false
+end
+```
 
 Keep in mind, this is ruby (and possibly rails), so you can add conditionals or utilize different environment.rb files to customize these settings on a per-environment basis.
 
@@ -66,14 +70,17 @@ But wait there's more:
 
 Let's say you have a method in your model that you can call to test the signup email. You want to be able to test sending it to any user at any time... but you don't want the user to ACTUALLY get the email, even in production. A dilemma, yes?  Not anymore!
 
-To override the environment based switch use force_sanitize, which is normally nil, and ignored by default. When set to true or false it will turn sanitization on or off:
+To override the environment based switch use `force_sanitize`, which is normally `nil`, and ignored by default. When set to `true` or `false` it will turn sanitization on or off:
 
+```
   SanitizeEmail.force_sanitize = true
+```
 
 There are also two methods that take a block and turn SanitizeEmail on or off:
 
 Regardless of the Config settings of SanitizeEmail you can do a local override to force unsanitary email in any environment.
 
+```
   SanitizeEmail.unsanitary do
     Mail.deliver do
       from      'from@example.org'
@@ -82,11 +89,13 @@ Regardless of the Config settings of SanitizeEmail you can do a local override t
       subject   'subject'
     end
   end
+```
 
 Regardless of the Config settings of SanitizeEmail you can do a local override to send sanitary email in any environment.
 You have access to all the same configuration options in the parameter hash as you can set in the actual
 SanitizeEmail.configure block.
 
+```
   SanitizeEmail.sanitary({:sanitized_to => 'boo@example.com'}) do # these config options are merged with the globals
     Mail.deliver do
       from      'from@example.org'
@@ -95,12 +104,15 @@ SanitizeEmail.configure block.
       subject   'subject'
     end
   end
+```
 
 ## Deprecations
 
 Sometimes things get deprecated (meaning they still work, but are noisy about it).  If this happens to you, and you like your head in the sand, call this number:
 
+```
   SanitizeEmail::Deprecation.deprecate_in_silence = true
+```
 
 ## Authors
 

data/lib/sanitize_email/bleach.rb

@@ -56,7 +56,7 @@ module SanitizeEmail
           # For each type of address line
           v.each { |a|
             # For each address
-            message.header = message.header.to_s + "\n#{k}: #{a}"
+            message.header = message.header.to_s.strip + "\n#{k}: #{a}"
           } if v
         }
     end

data/lib/sanitize_email/version.rb

@@ -1,5 +1,5 @@
 #Copyright (c) 2008-12 Peter H. Boling of 9thBit LLC
 #Released under the MIT license
 module SanitizeEmail
-  VERSION = '1.0.6'
+  VERSION = '1.0.7'
 end

data/sanitize_email.gemspec

@@ -5,7 +5,6 @@ Gem::Specification.new do |s|
   s.name = "sanitize_email"
   s.version = SanitizeEmail::VERSION
 
-  s.required_rubygems_version = Gem::Requirement.new("> 1.3.1") if s.respond_to? :required_rubygems_version=
   s.authors = ["Peter Boling", "John Trupiano", "George Anderson"]
   s.summary = "Rails/Sinatra/Mail gem: Test email abilities without ever sending a message to actual live addresses"
   s.description = "In Rails, Sinatra, or simply the mail gem: Aids in development, testing, qa, and production troubleshooting of email issues without worrying that emails will get sent to actual live addresses."
@@ -20,8 +19,9 @@ Gem::Specification.new do |s|
   s.test_files    = s.files.grep(%r{^(test|spec|features)/})
   s.homepage = "http://github.com/pboling/sanitize_email"
   s.licenses = ["MIT"]
+  s.email = 'peter.boling@gmail.com'
   s.require_paths = ["lib"]
-  s.rubygems_version = "1.8.24"
+  s.platform = Gem::Platform::RUBY
 
   # Runtime Dependencies
   # to replace the cattr_accessor method we lost when removing rails from run time dependencies

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: sanitize_email
 version: !ruby/object:Gem::Version
-  version: 1.0.6
+  version: 1.0.7
   prerelease: 
 platform: ruby
 authors:
@@ -11,7 +11,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-01-25 00:00:00.000000000 Z
+date: 2013-08-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -192,10 +192,7 @@ dependencies:
 description: ! 'In Rails, Sinatra, or simply the mail gem: Aids in development, testing,
   qa, and production troubleshooting of email issues without worrying that emails
   will get sent to actual live addresses.'
-email:
-- peter.boling@gmail.com
-- jtrupiano@gmail.com
-- george@benevolentcode.com
+email: peter.boling@gmail.com
 executables: []
 extensions: []
 extra_rdoc_files:
@@ -242,12 +239,12 @@ required_ruby_version: !ruby/object:Gem::Requirement
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
-  - - ! '>'
+  - - ! '>='
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.24
+rubygems_version: 1.8.25
 signing_key: 
 specification_version: 3
 summary: ! 'Rails/Sinatra/Mail gem: Test email abilities without ever sending a message