Could you, please, add an option - Automatic blacklisted mail deletion.

So, when this option checked then MailWasher would process automatic deletion of any new mail just recognised as blacklisted mail.

I am just using free MW version and would change to pro one if this nice feature could be integrated into MailWasherPro

Thanks for help

Svata

With MailWasher Pro under <Tools<Spam Tools<My Blacklist>

In the section entitled "Actions" check Mark the email for deletion

and click the Radio Button for Automatically (without notification)

This should do what you want.

I am an age old registered user of Mailwasher and can agree with svata.

There needs to be a slicker method for auto-delete. The filters do a great job and I have many set up to auto-delete for all sorts of things over many email accounts.

However what is missing is a method to be able to select to auto-delete any specific blacklisted emails. I do not want to auto-delete every blacklisted email.

Sometimes my filters are over-zealous and zap/blacklist a friend who has inadvertently put a phrase in his email which my filters pick up as spam/sleeze/etc.... I would not want those blacklisted emails to be auto-deleted.

I wish to select which blacklisted emails (domains) should be be autodeleted.

eg:
For these blacklisted email domains:
1) *@blacklisted_auto_delete_this.com
2) joe_bloggs@in_my_blacklist_so_auto_delete.com

3) *@blacklisted_but_dont_delete_this.com
4) joe_bloggs@in_my_blacklist_but_dont_delete_this.com

I want to be able to specify for (1 & 2) that they should be auto-deleted. But NOT for (3 & 4)

I think what he's trying to say is similar to what I proposed a while ago, namely that MW should have a separate "auto-delete" blacklist.

This isn't really addressed either through filters, or through the Friends list. The Friends list is fine for known legitimate addresses. Not all legitimate addresses are know. Filters are OK for general rules, but very inconvenient for deleting mails from lists of unrelated addresses.

The blacklist doesn't quite cut it either, because it tends to be used as a general sink for suspected spam addresses, but without those addresses always being checked carefully.

Of course, you could change the way you use the regular blacklist to address this, but what I think some people would like is two separate blacklists, one that may occasionally contain legit emails (mark these as spam but let me check) and another which you are sure contains only spam addresses (delete automatically).

Since forged addresses is a common practice of spammers how can you be sure that an address is spam? I.e. how would you establish that for a particular spam the address used is not forged?

I'm not suggesting you can detect forgery. I'm simply suggesting that there are certain addresses that you can be sure are sources of spam (assuming, of course, that your friends don't forge their addresses). If I add julie@sexmailings.com to an auto-delete blacklist, I think I can rest easy at night in the knowledge that I'm not deleting anything legitimate.

Anyway, I don't think we should turn this thread into an argument about our different anti-spam strategies.

OK I see your point. Do you get a lot of such spam? I have to admit I stopped looking for obvious spam addresses.
In any event, you might consider it to be an argument but I consider it to be a learning experience.

It would be really easy to do a filter to deal with these types of addresses. Use "from contains regex" and "or" the various addresses together, if you end up with a bunch of them just add another condition to the filter. If you get a huge number you can expand the filter beyond the basic GUI limit of 10 by manually adding conditions. The limit is set by your screen size and the OK button getting pushed off screen if you wish to use the dialog box to edit them, no limit (that I've found) if you edit filters.txt directly.

Doing this and reporting back on the effectiveness of the filter might sway other users to try it and at some point sway the firetrust developers into adding it.

I actually already have exactly such a filter set up, but you'll have to admit it's much more fiddly, and, more to the point, error-prone, than a built-in "auto-delete blacklist" facility. In particular, you have to be careful of dots in regular expressions, and if you add a large number of addresses you could end up screwing up the regex and catching legit addresses by mistake.

It's clear that you *can*, with patience and care, do what I'm asking in MW right now. I just think the built-in auto-delete blacklist would be easier, that's all.

Incidentally, I don't get a lot of spam (any more) which is as obvious as the example I gave . However, I do get a fair few that I'd be quite confident in automatically sending to spam hell.

lysandra@marsattack.com, abigail@pigpig.net, ralph@accurateloans.com and extension@hornydevil.co.au are just a few recent gems .

I don't use the blacklist at all so for me the addition of a second one would be worthless.

However I recognize that different people use MWP for different reasons and in different ways. I have no problem with that as long as it does not interfere with or slow down my use of the program.

You want it because you would use it, I don't because I wouldn't. Neither is any more right than the other. I am sure if FireTrust gets enough requests they will look into adding a feature. I have no connection with FireTrust other than being a customer and loyal supporter, so be assured that my opinion counts no more than your own.

Spammers never use their own email address and seldom repeat the use of any one address for more than a week or two. Growing your blacklist indefinetly is not likely to provide any more protection than having it self purge addresses not used in 30 days.

I'd agree with most of that with the exception of the purge delay, I think no more than 7 days is desireable. Why keep randomly generated stuff around once they have randomly generated another?

Take a look through your blacklist and check the expire dates on your entries to see just how often they are hitting.