| 1 |
Mailsave for Drupal 6.x
|
| 2 |
-----------------------
|
| 3 |
This is the first official release of mailsave for Drupal 6. At this time
|
| 4 |
only the main mailsave module and the clean up filters are ready for use.
|
| 5 |
The mailsave_to_image module isn't available as the image module itself
|
| 6 |
hasn't been officially released.
|
| 7 |
|
| 8 |
Mailsave version 2 for Drupal 5.x
|
| 9 |
---------------------------------
|
| 10 |
If you have used a previous version of mailsave please make sure to read
|
| 11 |
this file as there are some important changes!
|
| 12 |
|
| 13 |
mailsave is an extension that works in conjunction with mailhandler.
|
| 14 |
mailsave without mailhandler does not do anything!
|
| 15 |
|
| 16 |
When installed mailsave will collect attachments from incoming mail messages
|
| 17 |
and save them with the nodes that are created, if the user has the appropriate
|
| 18 |
permissions.
|
| 19 |
|
| 20 |
To save attachments you must enable upload.module and give the user both
|
| 21 |
the upload permission "upload files" and the mailsave permission "save
|
| 22 |
attachments".
|
| 23 |
|
| 24 |
The module uses the same rules as upload to determine what files the user is
|
| 25 |
allowed to save (maximum sizes, extensions etc). Attached files are saved
|
| 26 |
in to your Drupal files directory, just like upload does.
|
| 27 |
|
| 28 |
You can enhance mailsave by using additional modules that can alter the
|
| 29 |
created nodes in some way, depending on what attachments they find.
|
| 30 |
|
| 31 |
For example, mailsave_to_image works with mailsave and image such that if the
|
| 32 |
incoming message contains a jpeg then the node will automatically be
|
| 33 |
converted to an image node, using the first jpeg it finds. Any additional files
|
| 34 |
or jpegs will be attached.
|
| 35 |
|
| 36 |
You can achieve a similar effect by using the inline module if you prefer or
|
| 37 |
if you want to use multiple images in your post. In this case you simply use
|
| 38 |
regular inline syntax in your message, i.e. [inline|nn]. Refer to inline's
|
| 39 |
help for details.
|
| 40 |
|
| 41 |
The package also includes mailsave_to_image_attach and mailsave_to_imagefield
|
| 42 |
which allows mailsave to work with other modules that handle image formats.
|
| 43 |
There is also a beta version of mailsave_to_audio which has only had limited
|
| 44 |
testing.
|
| 45 |
|
| 46 |
If you want you can enable a mailsave extension, but disable the ability to
|
| 47 |
save attachments, so that you can limit what users are able to do.
|
| 48 |
|
| 49 |
You can also extend mailsave by using modules that interact with mailsave's
|
| 50 |
"clean up" hook. If you have a mobile phone that can send picture messages
|
| 51 |
via e-mail then you might find that the finished message contains additional
|
| 52 |
logos and text. If there is a clean up module for your service provider then
|
| 53 |
you can enable it to have additional images and text discarded, leaving you
|
| 54 |
with just the message and the actual attachments. You can find the plug-ins
|
| 55 |
at Administer > Mailsave. By default they are all turned off.
|
| 56 |
|
| 57 |
If you find mailsave and its related modules aren't saving attachments or
|
| 58 |
doing conversions that you expect always double check your user access and node
|
| 59 |
settings first. The most common error is that the user doesn't have permission
|
| 60 |
to use the conversion feature you want. This is often true if you are allowing
|
| 61 |
anonymous users to post via email. To allow this you must let anonymous users
|
| 62 |
have permission to create the appropriate content types.
|
| 63 |
|
| 64 |
You might also find the mailalias module (drupal.org/project/mailalias) useful
|
| 65 |
to allow users to associate other email address (e.g. their mobile MMS address)
|
| 66 |
with their account.
|
| 67 |
|
| 68 |
Key changes from mailsave version 1
|
| 69 |
-----------------------------------
|
| 70 |
The original mailsave module did both the attachment extraction and the
|
| 71 |
image conversion itself. To make the module more flexible and allow other
|
| 72 |
developers to interact with it the code has been separated in to mailsave,
|
| 73 |
the engine that does the ground work of retrieving attachments, and then
|
| 74 |
additional functions are implemented in separate modules via hook_mailsave.
|
| 75 |
|
| 76 |
MMS clean up functions are achived by using hook_mailsave_clean.
|
| 77 |
|
| 78 |
|
| 79 |
Key changes from mailsave for Drupal 4.6
|
| 80 |
----------------------------------------
|
| 81 |
administer > settings > mailsave no longer exists. Everything is now controlled
|
| 82 |
from Administer > User management > Access control.
|
| 83 |
|
| 84 |
Users need TWO permissions to allow saving of attachments, and TWO permissions
|
| 85 |
to allow creation of image nodes. This allows you to fine tune who can do what.
|
| 86 |
|
| 87 |
Files are now saved in the regular drupal files directory.
|
| 88 |
|
| 89 |
; $Id: README.txt,v 1.8 2007/12/05 22:59:29 stuartgreenfield Exp $
|
Parent Directory
| 
Revision Log
| 
Revision Graph