Changes between Version 16 and Version 17 of FAQ/Using YAM


Ignore:
Timestamp:
May 11, 2012 3:37:21 PM (2 years ago)
Author:
damato
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQ/Using YAM

    v16 v17  
    277277Even if that seems to be very ugly on a first thought, it is the only logical approach to the problem of having such mail interchangeable between different mailers. In addition, in most cases only single words need to get or should be highlighted in an email so that you will hardly set a whole sentence in bold/underline or such. 
    278278 
    279  
    280  
     279=== Why is the TAB key not advancing to the internal text editor gadget when I finished writing the subject line of a mail? === 
     280This "problem" should only be visible with YAM versions equal or higher than 2.5+ In fact, it isn't really a problem, but a changed behaviour. The point is, that due to the change to TheBar.mcc the toolbar is now also within the normal MUI "CycleChain" for allowing an application to get fully manageable via keyboard. So, if you are now editing the subject line of a mail and you press the TAB (Tabulator) key, the next activated MUI gadget will be the first toolbar button instead of the TextEditor gadget like it was in versions prior to 2.5. 
     281 
     282However, to still being able to switch to the text editor immediately you can use the Return/Enter key instead. That means, if you are finished with editing/writing the subject line and you want to change to the text editor for writing the actual content of the mail, just press the "Return" key instead. 
     283 
     284=== Why doesn't YAM let me choose an address from the popup list when writing a mail? === 
     285When completing a yet known address YAM needs to be able to distinguish one address from another. That means that both, alias and realname, should be "relatively" unique. Example: First address book entry Name: foobar Alias: Address: test1@test.com Second address book entry Name: blafasel Alias: foobar Address: test2@test.com As soon as you enter "foobar" in the "To:" field the address match list will pop up to let you choose a recipient. But selecting either of these two entries will fail, because YAM cannot tell these two entries apart if "foobar" is the only matching criteria. "foobar" can be resolved to the first entry's name AND to the second entry's alias, but not to one single entry. That is why the resolve will fail. The only soltion for this problem is to use unique names and aliases. That means NO real name must exactly match any other alias, and vice versa. 
     286 
     287=== My system hangs when deleting a block of text in the editor while using a key qualifier, why? === 
     288Unfortunately, this is a bug in the Texteditor.mcc <= v15.9 MUI custom class you are using. Please upgrade to the very latest version available at http://www.sf.net/projects/texteditor-mcc 
     289 
     290 
     291== Filtering Mails == 
     292 
     293=== If I search for "[SPAM]" in a filter, mails not containing this string will get hit by the filter as well, why? === 
     294Well the reason is, that you seem to have missed that the string gadget for entering the search string accepts AmigaDOS wildcards. Therefore, the [ is a special reserved character and have to be escaped to match the literal character itself. So if you want to search for a [ character with an AmigaDOS pattern aware method you have to use: 
     295 
     296{{{ 
     297'[SPAM'] 
     298}}} 
     299 
     300where the ' character escapes the reserved state of the [ and ] chars. However, even more precisly would be to use: 
     301 
     302{{{ 
     303'[SPAM']#? 
     304}}} 
     305 
     306instead and turn off the "Substring" option. That would then match only subjects that actually start with [SPAM] as there might even be non-SPAM messages contain that string somewhere. 
     307 
     308__NOTE on searching for [SPAM]:__ 
     309 
     310Matching SPAM messages on the literal [SPAM] marker in a subject line is more or less a bad idea as it would cause (even if correctly escaped) many non-SPAM messages to get filtered incorrectly. Normally SPAM filter add an additional header line like 'X-Spam-Status:' to each checked email. So to reduce the amount of incorrectly matched mails you would be better off searching for that optional header line and search if it starts with "Yes". 
     311 
     312=== How to train YAM's SPAM filter properly? ===  
     313YAM's spam filter is an adaptive filter - a so-called Bayesian spam-filter - which was ported from the well-known mail client Thunderbird and behaves exactly the same. 
     314 
     315__Background:__ 
     316The nature of this kind of spam filtering is an iterative learning process where the content of a mail will be evaluated according to a calculated spam probability. That means, that right from the beginning it is absolutely "stupid" and doesn't know which mails are actually spam or no spam. Hence the filter needs to be trained __manually__ to be able to distinguish between spam and no spam. 
     317 
     318__Usage:__ 
     319After enabling the spam filter all newly received mails will most likely be classified as spam and automatically moved to the spam folder. **This is absolutely normal and intended!** Again, keep in mind that the spam engine is "stupid" and only relies on your user input. 
     320 
     321Now you have to tell YAM which mails are really spam and which are not spam (so-called Ham). Just mark all regular (no spam) mails which were moved to the spam folder as "Not Spam" and move them to another folder (i.e. the incoming folder). This will train the spam engine about how "no spam" mails look like. Such mails are called false negatives because they were automatically flagged as spam but they aren't spam. Continue to do so as more "no spam" mail arrives which will be automatically flagged as spam on accident. 
     322 
     323Of course, the spam procedure applies to spam mail that was not recognized as spam. If new mail arrives and it wasn't properly recognized as spam flag it as spam manually. Continue to do so as new mail arrives. After some time YAM will gradually become better in correctly recognizing spam mails itself and you will have to classify false positive and not recognized spam mails yourself very seldom - However, there will always remain a small probability of false positives and not recognized spam mail, no matter what. 
     324 
     325__WARNING:__ 
     326You should **NOT** "enforce" the learning process by classifying all your previously collected spam mails manually after enabling the spam filter. YAM will learn best by itself with a little help by the user, as described above. **Only newly** received emails should be manually flagged as spam or no spam. Usually about 100 mails (good as well as bad) are enough to let YAM recognize spam mails correctly with a probability of 90% and more. However, if for some reason the spam filter "stops" to work for you no matter how to train it, go to the YAM configuration and reset the SPAM training data and restart flagging spam and no spam manually as new mail arrives. 
     327