Avoid warning: is_writable(): open_basedir restriction in effect.
merged branch petajaros/patch-1 (PR #270)

This PR was merged into the master branch.

Commits
-------

34358cd Avoid warning: is_writable(): open_basedir restriction in effect.

Discussion
----------

Avoid warning: "is_writable(): open_basedir restriction in effect."

When the parameter provided for is_writable function is a path restricted by setting open_basedir configuration (http://php.net/manual/en/ini.core.php#ini.open-basedir), it throws warning instead of simply returning false. @ operator suppress the warning. Warning unnecessarily breaks the flow of the program - returned value 'false' is sufficient.

---------------------------------------------------------------------------

by fabpot at 2013-01-02T10:03:53Z

Can you add a comment above to indicate why we need to use the `@` operator?

---------------------------------------------------------------------------

by petajaros at 2013-01-02T14:19:27Z

I'm sorry. I have already written short description.

---------------------------------------------------------------------------

by fabpot at 2013-01-02T15:38:14Z

I mean, add a comment in the PHP file.
added a comment
fixed license issues (all authors ackowledged the change -- see https://github.com/swiftmailer/swiftmailer/pull/227)
fixed some unit tests
prepared the 4.3.0 release
bumped version to 4.3.1-DEV
fixed years in the CHANGELOG
fixed some CS
fixed usage of the PHP native QP encoder on PHP >= 5.4.7 (closes #277)
replace array_merge with manual iteration for performance
merged branch jimbojsb/master (PR #280)

This PR was merged into the master branch.

Commits
-------

37372cd replace array_merge with manual iteration for performance

Discussion
----------

Fix performance when tokenizing massive headers

I made this update to fix a performance issue when using very large headers. The use case is SendGrid's bulk messaging API in which there can be many thousands of lines of JSON in one  X-SMTPAPI header. array_merge() is known to be slow when dealing with arrays over about 100 items and being called repeatedly, because it's doing a key re-sort operation every time.

This change, in my 1000 item example, made the processing that happens inside ->send() go from 2 minutes to 2 seconds.
updated CHANGES
Fix set body length in DKIM
merged branch Scimon/master (PR #281)

This PR was merged into the master branch.

Commits
-------

ebc6bd8 Fix set body length in DKIM

Discussion
----------

Small fix

Hi, I've been using Swiftmailer recently for DKIM signing and noticed the setBodyLength function in the DKIM signer was incorrectly referencing $this->len not the $len argument.

Cheers.

Simon