LISTFREEZE MAILS

Debug output with the REXX flag, running SpamFryer.yam script - Moved from SF. Original author: amigaphil

Nightly build 2009-09-30, OS3

Experimenting with a new SpamFryer.yam (spam filter), I discovered that LISTFREEZE MAILS does work, but some ARexx commands DO resect the frozen status of the mail list. Checking for spam, the mail list remain frozen until a spam is moved to the Trash folder (MAILMOVE). Then, all other mail checked are shown in the mail list, and displayed in the mail preview window.

While in frozen state, it seems that the auto mark-as-read behavior is inhibited as expected (I found no mails with a Read status where the status should have been Unread or New); but it's no more true when a command "unlock" the frozen status.

I think that the commands that "turn off" the LISTFREEZE frozen state of the mail list are: MAILMOVE, MAILSTATUS, and probably MAILCOPY, MAILDELETE.

Moved from SF. Original poster: amigaphil

Nightly build 2009-09-30, OS3

WEIRD...

I just had a YAM session, with SpamFryer.yam as 'After getting mails' event. 64 new mails were downloaded, 13 were spams. After the first moved-to-Trash spam, only the mail list window was unlocked (but that's fine, as it is showing which mail is currently being scanned). The checked mail was not rendered in the mail preview window, and was not loosing its 'New' status (marked as 'Read' while being selected/scanned).

?!? (I'll do some more tests.)

Moved from SF. Original poster: amigaphil

Nightly build 2009-09-30, OS3

Testing again today...

Downloaded 24 mails, 7 were spams.
All went fine until the first spam was moved to Trash (MAILMOVE). Then
each other scanned mail (SETMAIL) were shown in the mail list window,
displayed in the mail preview window, and eventually marked as read (when
it took longer for a mail to be checked).

??

Moved from SF. Original poster: amigaphil

I've uploaded here a new beta version of SpamFryer.yam (originally created by Allan Rasmussen) for testing this issue.

If you are new to SpamFryer, you might want to download the SpamFryer package by Simon N. Goodwin from Aminet first, so that you will have full documentation and a base keepList (white list) and loseList (black list) to work with. You also will need to edit the file to change (at least) the path to the keepList and loseList.

Suggested usage for testing (taken from the .readme):

If you want SpamFryer.yam to automatically check all new mails, then start YAM (this example assumes version 2.5), open the Settings/Configuration menu (or press the Right Amiga key and the asterisk in the top right corner of the numeric pad at the same time), click on 'Scripts' in the left column and select the line marked 'After getting mail' in the 'Action (Name)' column that appears under the heading 'Scripts settings'. Name will then be ghosted; ensure that the cycle gadget alongside says 'ARexx' not 'AmigaDOS' and enter:

YAM:Rexx/SpamFryer.yam Incoming SILENT

on the following line, by the caption 'Script'. Make sure that the two checkboxes below are both ticked:

[v] Open console window [v] Wait for termination

Moved from SF. Original poster: amigaphil

Here is a debug output with the flag set to REXX.

New mails 66 to 61 were checked, mail 64 was a spam and MAILMOVEd to Trash.

I don't see much that talk to me there, except those Timer.c:164:timer[4]: already stopped Timer.c:164:timer[3]: already stopped happening just after the MAILMOVE action and also when the other mail (63 to 61) are being processed.

(Note: I'm using the 'empty' theme, and thus, I removed almost all the imagecache warning messages.)

(Note2: Sorry if multiple post. Seems SourceForge has some problems right now.)

Moved from SF. Original poster: amigaphil

(Removed the SpamFryer.yam file as outdated. A newer version will appear
on Aminet soon.)

Moved from SF. Original poster: amigaphil

Is that problem still valid? If so please provide a step-by-step example on how to reproduce it.

ARexx test script

Attachment (testmove.rexx) added by ticket reporter.

Replying to damato:

Is that problem still valid? If so please provide a step-by-step example on how to reproduce it.

I've uploaded a new script for testing this.
It scans all messages in the current folder, and if one has the string "test" in subject, it is moved to the Trash folder.

The GUI remain quiet (as expected) until there is a match (a message is MAILMOVEd). Then the LISTFREEZE has no more effect (the GUI is refreshed for all other scanned mails).