So I needed to import a lot of filter

[Ira]

Do not allow these in the name or description (or any conditions): < > & ® © (or any accented letters, like á)

If I knew what to translate those ito, I'd take care of it. Though I think the most recent version handles <, > and &.

I also found that certain specialty characters cause a crash. Once of them is the Registered symbol. I'm fairly certain the a Copyright circle will also crash MWP. I finally learned this the hard way and converted the Registered mark into its numeric equivalent. ISO codes were rejected.

Same question as above, what do I convert them to?

Also, the converted choked on a filter it did not understand and terminated the conversion prematurely. It took me over an hour to figure out what was causing the hiccup and fix it. The problem filter is working just fine under version 6.x, but needed to be expanded for v2010. Here is the bad condition that crashed the converter during importing:

I never imaginde the text of a filter would be less than 3 characters long, my bad!

Ira

[anniebrion]

Do not allow these in the name or description (or any conditions): < > & ® © (or any accented letters, like á)

If I knew what to translate those ito, I'd take care of it. Though I think the most recent version handles <, > and &.

MWP2010 converts < > & to < > &, found if you put them in a regex rule and then edit the filters.xml file with notepad++

[Ira]

There is what might be a slightly improved version uploaded.

Ira

[Ira]

Do not allow these in the name or description (or any conditions): < > & ® © (or any accented letters, like á)

If I knew what to translate those ito, I'd take care of it. Though I think the most recent version handles <, > and &.

MWP2010 converts < > & to < > &, found if you put them in a regex rule and then edit the filters.xml file with notepad++

It's not that I'm lazy, it's just that I'm not using the new version and I don't have a working copy any more. If I get help, I'll improve it, but I can't do the research for a product I no longer use.

Ira

[anniebrion]

It's not that I'm lazy, it's just that I'm not using the new version and I don't have a working copy any more. If I get help, I'll improve it, but I can't do the research for a product I no longer use.

I was not trying to imply you were lazy I was just pointing out how I got the answer, others might find the technique useful.

I think your application is a brilliant solution to the problem of filter import

[paul.mac]

Thanks for the expanded details. Got it to work and have got all my filters installed although they don't seem to work entirely as before. Must be to do with some of the other new settings in MW2010. One point worth mentioning is that the filters.xml file created by this excellent little utility program is placed in the same directory as the program itself. So if you run it from a temp directory ,for example, then that's where it will place the filters.xml file not in the mailwasher directory.

Why didn't firetrust do this - can't have been beyond them surely?

Also doesn't seem to run as fast as the old pre-improved version or is thatmy imagination?

Thanks again

Paul

[Wizcrafts]

Do not allow these in the name or description (or any conditions): < > & ® © (or any accented letters, like á)

If I knew what to translate those ito, I'd take care of it. Though I think the most recent version handles <, > and &.

MWP2010 converts < > & to < > &, found if you put them in a regex rule and then edit the filters.xml file with notepad++

It's not that I'm lazy, it's just that I'm not using the new version and I don't have a working copy any more. If I get help, I'll improve it, but I can't do the research for a product I no longer use.

Ira

Here is what I came up with Ira...

Code: Select all

<Filter Name="Subject contains < * + ' >" Enabled="True">

And this one:

Code: Select all

  <Filter Name="TO: Contains << >>" Enabled="True">
    <Description>TO: Contains << >></Description>

Any filter name that has an & symbol should be changed into: &

Finally, some filters have just one character condition, such as my single "." in the blank subject filter. This rule caused your importer to crash and terminate before finishing its conversions.

Code: Select all

[enabled],"No Subject","No Subject",16711680,AND,Delete,Subject,doesn'tContainRE,.

I had to change the condition in the old rule into the following, to get the converter to continue...

Code: Select all

[enabled],"No Subject","No Subject",16711680,AND,Delete,Subject,doesn'tContainRE,.{1,}

[Ira]

I think I fixed all of those and put up a new version, does it still fail on all of those?

Ira

[Wizcrafts]

I think I fixed all of those and put up a new version, does it still fail on all of those?

Ira

Well done, Grasshopper! It works as it should now, at least with the characters that are in use at this time in the old version filters. Even the single character regular expression now converts as it should.

[gasman]

Just like to say 'Thank You very much' for a very useful utility.

And here is a tool to do that automatically. Probably neeeds .NET 2.0

http://www.extrasensory.com/Downloads/M ... Import.exe

it's crude, but it works. It will replace the current V2010 filters so if you can point the output somewhere else and copy them across in a text editor. if you break it, send me the problem filter and I'll fix it. And check all you filters to make sure they're correct. I don't know if it's perfect, but it sure saves a lot of work.

Ira

[Ira]

Well done, Grasshopper! It works as it should now, at least with the characters that are in use at this time in the old version filters. Even the single character regular expression now converts as it should.

Fixing that stuff was only a couple of minutes, the single character problem was just changing <3 to >0. I just never imagined a 1 character expression.

Be nice if Firetrust said thanks, especially since I don't use the product it's for!

Ira

[Wizcrafts]

Well done, Grasshopper! It works as it should now, at least with the characters that are in use at this time in the old version filters. Even the single character regular expression now converts as it should.

Fixing that stuff was only a couple of minutes, the single character problem was just changing <3 to >0. I just never imagined a 1 character expression.

Be nice if Firetrust said thanks, especially since I don't use the product it's for!

Ira

Thanks Ira. Your converter is much appreciated by us tinkerers. Don't give up so fast MWP 2010. I'm sure your work on the importer was noticed by Firetrust.

[gasman]

Be nice if Firetrust said thanks, especially since I don't use the product it's for!
Ira

I could never work out why they did not do this themselves and asked about this a good while back. Especially as they knew both structures and characters used.?

They might well say the new expressions are better, but it would be a good transition for users to carry over the old filters until they want to experiment further.

Personally while I could get to grips with regex expressions if I so chose, I'd much rather a gui driven approach.

Twonky Media Server has gone the same way. The old product would give you a decent structure using a few list boxes, now you have to be able to create xml.

XML might be the latest craze, but not everyone is a programmer, or even wants to program.

Again well done, this will likely help plenty of users who try MW 2010.

[rusticdog]

Thanks Ira

This utility I am sure will make many folk happy.

[Ira]

Thanks Ira

This utility I am sure will make many folk happy.

Next time you have a beta, invite me. I'm really good at that, I even have references if you want them. You clearly need better beta testers than you have.

Ira