#80 ✓fixreleased
Alexander Kucera

Junk handling with SpamSieve

Reported by Alexander Kucera | March 3rd, 2011 @ 07:32 PM

Hi Benny, I was wondering if you could elaborate on the way to deal with spam mails in general and in combination with SpamSieve in specific.

I do have SpamSieve installed and it is well trained from my previous use with Mail.app. However I don't really see that enabling SpamSieve is doing anything other then showing an additional column with the SpamSieve score.

My system: MailMate/1934 MacBookPro5,3/i386/2/10.6.6

Comments and changes to this ticket

  • benny

    benny March 4th, 2011 @ 12:39 PM

    • Assigned user set to “benny”

    The support is fairly simply, but also adequate in my opinion.

    Anything arriving in your Inbox will be given to SpamSieve. If the score is high then it is automatically moved to Junk. You can see that it has been checked by looking for a value in the SpamSieve column.

    If you mark something as Junk or Not Junk then SpamSieve is also informed so that it can update its “corpus”.

    So, you should not really doing anything different than normally other than to continue marking/moving junk messages if they appear in your Inbox (⇧⌘J), Maybe also review you Junk mailbox once in a while to look for false positives.

    Let me know if you think something is not working as described above.

    In the next update, you can specify the mailbox checked for spam. The default is still Inbox (the unified Inbox), but you may want to limit or extend this, e.g., I only have 1 account where spam occurs and I therefore only let SpamSieve check messages arriving in that account.

  • Alexander Kucera

    Alexander Kucera March 5th, 2011 @ 04:48 PM

    Ok, then I guess it works as expected.

    Then I maybe have a feature request. Can you skip showing me the "Load once, Not Junk, Junk" bar when my SpamSieve score is really low (say below 35 or so). I feel it is quite unnecessary to tell my mail application that something is secure to load if my spam filter already told it that it is no spam. Tends to increase the work I have to do and I am as lazy as hey get. ;)

    And in case SpamSieve missclassified something as ham that should be spam, I can always tell it otherwise via the buttons or the menu.

    Or maybe have something similar to Mail.app that blocks image loading at all times untIl told otherwise?

    I just find that this is a confusing mix between implicit HTML content loading and spam coutnermeasure behaviour. Or is that just me?

  • benny

    benny March 5th, 2011 @ 05:15 PM

    • State changed from “new” to “accepted”

    Better control of image blocking is on my list. The default should be to never trust external references, but I do understand that not everybody would prefer that.

    I'll mark this ticket as “accepted” until a solution for controlling image blocking is implemented.

  • Alexander Kucera

    Alexander Kucera March 5th, 2011 @ 05:56 PM

    Well, I do agree that external references should never be trusted, but I think that way it is handled now is not quite right.

    Personally I have disabled the loading of external images in Mail.app and would enable such an option again in MailMate. But I think it is the wrong behavior to label an e-mail junk or not junk in such a case, since that is what I do have SpamSieve for. It should be an additional toggle to load external content that is independent of the junk status. At least in my mind. Since at the moment the metaphor is that I have to tell MailMate if an e-mail is junk or not even though that classification has already been done.

  • benny

    benny March 23rd, 2011 @ 01:36 PM

    • State changed from “accepted” to “fixcommitted”

    Identifying junk and blocking images are now separated in the preferences.

    It is still possible for users to not block images for Not Junk marked messages, but the solution is much more flexible now. More about this in the release notes (when it is released).

  • Alexander Kucera

    Alexander Kucera March 24th, 2011 @ 07:00 PM

    Cheers Benny,

    I just updated to the newest bleeding edge and I like the new behavior much better. More intuitive. Thanks for taking care of this.

    My system: MailMate/1999 MacBookPro5,3/i386/2/10.6.6

  • benny

    benny March 25th, 2011 @ 10:47 PM

    • State changed from “fixcommitted” to “fixreleased”
  • Alex Veer
  • Alex Veer

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Mac OS X email client.

Shared Ticket Bins

People watching this ticket

Pages