/ 
Courriel-0.13
River stage zero No dependents

Changes for version 0.13 - 2011-06-20

  • A multipart email build with Courriel::Builder would have a broken Content-Type header, missing the required boundary attribute. Reported by ico. RT #68694.
  • If you explicitly passed unencoded content when creating a part (which happens when using Courriel::Builder), that content would be modified so it had CRLF line endings. Now, such content is left untouched. Reported by ico. RT #68695.
  • When passing encoded content to the Courriel::Part::Single constructor, the constructor used to modify the content so it had CRLF line endings. Now it is left alone.
  • Note that if you're passing raw content to the Single constructor _and_ setting the transfer encoding to 7bit, 8bit, or binary, then you'll end up with a noncomformant email. However, by default all raw content is base64 encoded. It is strongly recommended that you pass raw content and let Courriel take care of the transfer encoding.

Modules

Courriel
High level email parsing and manipulation
Courriel::Builder
Build emails with sugar
Courriel::ContentType
The content type for an email part
Courriel::Disposition
The content disposition for an email part
Courriel::Headers
The headers for an email part
Courriel::Part::Multipart
A part which contains other parts
Courriel::Part::Single
A part which does not contain other parts, only content
Email::Abstract::Courriel
Email::Abstract wrapper for Courriel

Provides

Courriel::Helpers
in lib/Courriel/Helpers.pm
Courriel::Role::HasParts
in lib/Courriel/Role/HasParts.pm
Courriel::Role::Headers
in lib/Courriel/Role/Headers.pm
Courriel::Role::Part
in lib/Courriel/Role/Part.pm
Courriel::Types
in lib/Courriel/Types.pm
Courriel::Types::Internal
in lib/Courriel/Types/Internal.pm

Other files