Poi-receivemail

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

- Nothing changed yet.

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

- Create issue with proper id directly.
Renaming can give hard to debug permission problems
in combination with our adopt_user and adopt_roles.
[maurits]

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

- Store attachments as blobs. For example the original email message. [maurits]

- Drop support for Python 2.4, because we use ``plone.api``.
Officially drop support for 2.6 too, and for Plone 4.2 and earlier, but it may still work.
[maurits]

- Use plone.api to adopt a different user and roles.
This is cleaner, and should avoid problems where the faked user did not have a user id.
[maurits]

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

- Log the sender and subject at info level.
[maurits]

- Caught several cases where the created issue was invalid.
This caused a workflow exception, which means the issue was never added.
This could happen when an html mail was received and the mime type was not allowed in the details field.
Now we convert the mail text to the default issue mime type.
If the issue is still invalid, we catch the workflow exception and create the issue anyway,
because there is no easy way of signalling this to the sender.
The issue then has the ``new`` state, which may not be visible in the Poi user interface though.
[maurits]

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

- Check ``NEEDED_PERMISSIONS`` before faking a manager. If a user
already has the needed permissions, there is no need to fake a
manager. [maurits]

- Fake a ``TrackerManager`` instead of ``Manager`` when possible.
This role was introduced in Products.Poi 2.2 (Plone 4). This is
done when ``FAKE_MANAGER`` is true, which is the default. This only
happens for specified IP-addresses. [maurits]

- Fixed issue creation for Plone 4. Posting an issue would fail
because no ``post`` transition was available. This is because in
Plone 4 this happens automatically on the
``IObjectInitializedEvent``. Now we only do the transition if the
review state is still ``new``. [maurits]

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

- Fixed package: don't use symlinks. [maurits]