This script will prepare the selected emails for spam reports to SpamCop
or a similar service.
Before you can use it, you must enter your personal SpamCop email address
for spam reports in the "configuration block" at the top of the script.
You get a personal SpamCop report address by signing up for an account at
Optional, you can also enter any email addresses you would like to get
automatically munged. You can enter any and as many words you would like,
separated by spaces.
Please be adviced though, that SpamCop only allow munging of YOUR OWN EMAIL
ADDRESSES and nothing else! Please DO read the FAQ at the SpamCop site.
It is a good idea to remove or replace the supplied example munge search
patterns in any case, as they otherwise only will slow down the process.
The search is case insensitive, but the script expects you to write search
patterns in lower case. Quotation marks are not allowed as part of search
patterns or recipient addresses.
The script will not munge anything in the email header, except possible in
the subject, because SpamCop is supposed to munge the addresses in the
header for us.
When you have configured the script, you can use it by starting YAM, then
select the emails you want to report and choose SpamReport.yam from the
menu item "Scripts/Execute script..." or from CLI using the Rx command.
Spam reports will then be created in the 'Outgoing' folder.
It is possible to enter more than one recipient, separated by commas. It is
hardly recommendable though.
If you have entered the report address in your addressbook, you can use
the name or alias instead of the actual address.
If you use it often, you might want to put the script in one of YAM's menu
item slots, using "Configuration/ARexx".
The script accepts the following arguments, which if used, will supersede
the settings in the "configuration block".
Example:> Rx SpamReport.yam SILENT RECIPIENT="xxxspamcop.net" MUNGE=""
The example will create reports of the selected emails with nothing munged,
to the address xxxspamcop.net.
The TOGGLE switch can be used to force the other switches to toggle the
values in the 'configuration block'. If the TOGGLE switch is not used, an
argument can only make the corresponding option TRUE.
If you start the script from YAM and nothing happens, it might be because
the script needs an output window. In that case, please try starting it
from CLI, using the Rx command, before sending me a bug report.