mime 0.4.0 → 0.4.1

data/README.rdoc

@@ -6,7 +6,7 @@ in client/server communications, such as Internet mail or HTTP
 multipart/form-data transactions.
 
 
-== See
+== See Also
 
 * MIME for RFCs used to implement the library (other RFCs scattered throughout)
 * MIME::CompositeMedia for a description of composite media types
@@ -306,12 +306,13 @@ For many more examples, check the test class MIMETest.
 
 == Links
 
+Homepage      :: http://ecentryx.com/gems/mime
 Ruby Gem      :: https://rubygems.org/gems/mime
 Source Code   :: https://bitbucket.org/pachl/mime/src
-Documentation :: http://ecentryx.com/gems/mime
+Bug Tracker   :: https://bitbucket.org/pachl/mime/issues
 Validators    :: Please check *all* of your messages using the following lint 
-                 tools and report errors to pachl@ecentryx.com with "Ruby MIME" 
-                 in the subject.
+                 tools and report errors to the bug tracker or directly to 
+                 pachl@ecentryx.com with "Ruby MIME" in the subject.
 
                  - http://www.apps.ietf.org/content/message-lint
                  - http://tools.ietf.org/tools/msglint
@@ -337,7 +338,9 @@ Validators    :: Please check *all* of your messages using the following lint
      * Rename classes:
        - HeaderContainter => Header
        - remove "Media" suffix from the 5 DiscreteMedia and 2 CompositeMedia 
-         subclasses. See revision 4876b1390624 for details.
+         subclasses.
+         See {commit}[https://bitbucket.org/pachl/mime/commits/4876b1390624a1c07682d2a11fd90296a83c002d]
+         for details.
        - MIME::Message => MIME::Mail
      * Rename methods:
        - remove "_entity" suffix from add, inline, and attach in CompositeMedia.
@@ -351,7 +354,8 @@ Validators    :: Please check *all* of your messages using the following lint
        - Header#delete
      * Reverse order of entities in CompositeMedia::Body, which most likely
        reverses all CompositeMedia #add, #inline, and #attach method calls.
-       See revision a51745f346b5 for details.
+       See {commit}[https://bitbucket.org/pachl/mime/commits/a51745f346b517929383bdb6e60301c385ffab49]
+       for details.
    * Other changes
      * Use From header field domain in the Message-ID header.
      * Add more randomness when generating header IDs.
@@ -365,6 +369,9 @@ Validators    :: Please check *all* of your messages using the following lint
      * Comply with RFC regarding parameter quoting in header field bodies.
        I.e., do not quote atom/dot-atom parameter values.
      * Many fixes and improvements in code, tests, documentation, and examples.
+5. 2014-04-20, v0.4.1
+   * Add bug tracker URL.
+   * Link to referenced commit messages.
 
 
 == License

data/lib/mime.rb

@@ -18,7 +18,7 @@
 #
 module MIME
 
-  VERSION = '0.4.0'
+  VERSION = '0.4.1'
 
   # Defined in RFC: https://tools.ietf.org/html/rfc5322#section-2.1.1
   MAX_LINE_LENGTH = 998

data/lib/mime/mail.rb

@@ -27,6 +27,7 @@ module MIME
     def to_s
       self.message_id   ||= ID.generate_gid(domain)
       body.mime_version ||= "1.0 (Ruby MIME v#{VERSION})"
+      # TODO if From contains multiple mailboxes Sender must be present
 
       #--
       # In an RFC 2822 message, the header and body sections must be separated

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: mime
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.4.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-04-18 00:00:00.000000000 Z
+date: 2014-04-21 00:00:00.000000000 Z
 dependencies: []
 description: ! 'A library for building RFC compliant Multipurpose Internet Mail Extensions