|
|
microsoft.public.windows.vista.mail |
The 'Value' data of rule actions is stored as ASCII while the 'Value' of Since, as you have so eloquently pointed out, the rules were stored as ASCII In any case, as stated, it works. I wouldn't have posted it otherwise. -- Thanks, Jerry S > But if you look at the Value Value (<G>) under Criteria for the rules(eg. > steve > "Frank Saunders, MS-MVP OE/WM" <franksaund...@mvps.org> wrote in message > > "Steve Cochran" <scoch...@oehelp.com> wrote in message > >> Here's what I posted on December 12th: > >> <quote> > >> This is for a single rule at the moment. I'll try and program it so it > >> First export the rule from the machine with OE: > >> HKEY_CURRENT_USER\Identities\{GUID}\Software\Microsoft\Outlook > >> where GUID is the Identity and this is rule 3 > >> Then edit the reg file with Notepad. > >> Do replace for > >> HKEY_CURRENT_USER\Identities\{GUID}\Software\Microsoft\Outlook > >> with > >> HKEY_CURRENT_USER\Software\Microsoft\Windows Mail > >> Then save the file. > >> Then the search strings have been changed to Unicode so set the cursor > >> , > >> replace with > >> ,00, > >> Then in the last line of each criteria add > >> ,00 > >> Then save. > >> Then create a mock rule in the registry with WinMail and close WinMail. > >> Then merge the file into the registry. > >> Open WinMail and go to Tools | Message rules and you see the new message > >> Anyway, that will work, but its a bit involved to do manually. > >> </quote> > >> "Jerry S" <notdisclo...@nada.tld> wrote in message
criteria, while exported as ASCII, is apparently converted into Unicode as
the single byte values from the Regedit file created during the export are
double byte values in the Vista registry.
in OE and I would be surprised if importing the ASCII values in a Regedit
version 4 file would import differently than the ASCII values in a Regedit 5
file. However, I would change my statement that "the registry format for
rules is identical" to "the structure of the rules are the same" as obviously
a string stored as ASCII is not identical to one stored as Unicode.
"Steve Cochran" wrote:
> Oh. I hadn't thought of that. I'll have to look and see how I did it.
> HKEY_CURRENT_USER\Software\Microsoft\Windows
> Mail\Rules\Mail\000\Criteria\000), you'll see in XP (server 2003) that the
> string is not Unicode, but if you look at the same in Vista, you will see
> that it is in Unicode. So I don't know how the export method would be
> involved.
> news:4C7E65F3-C960-411F-BBF6-B9BF059CD853@microsoft.com...
> > It may depend on whether it's exported as a Regedit 4 or Regedit 5
> > (Windows Registry Editor Version 5) file.
> > news:69FF5A7D-9966-473F-B5A8-4783B94CDE57@microsoft.com...
> >> As I indicated a ffew months ago, the actual rule is now a Unicode string
> >> and it wasn't before. So one has to modify that.
> >> Okay there are actually 4 issues, but I figured out two of them.
> >> doesn't have to be done rule by rule.
> >> Express\5.0\Rules\Mail\002
> >> Express\5.0
> >> where
> >> the Rule Criteria start. Then do a second replace until the end of the
> >> file
> >> and search for
> >> Then delete that mock key in the registry. Make sure the rule number in
> >> the
> >> saved reg file matches that that you just deleted.
> >> rule spelled out okay when you click on it, except for the folder name.
> >> You
> >> will still have to specify the folder names again because those are coded
> >> numerically, I think.
> >> news:O9LB0ZkWHHA.1688@TK2MSFTNGP05.phx.gbl...
> >>> That's odd, because in practice it works exactly as described. If
> >>> you're
> >>> referring to the location that the rules are stored, that's covered in
> >>> steps
> >>> 3d - 3f. If you're referring to the pointers within the rules that
> >>> reference the objects within the OE data stores, that is covered in step
> >>> 5.