IFW: Exclude (/exlist) seems to ignore this
Posted: Sun Aug 30, 2015 4:14 pm
I've been using /exlist for years, and it's worked. I'm aware of some of the tricky aspects of it, as explained in the manual.
However, the latest addition to my exclusion text file seems to be ignored. It's no different (except for the directory, which is definitely correct) than any of the others in the file. It looks like the example from the manual:
[k]\Outlook Archives\ >
Yet, when I look in the log file, I see the usual "Warning: Data excluded from files based on list" message followed only by my older five exclusions (they've been there a while), not the new one.
At first, I thought there might be a limit of 5 items in the exclusion file, but that seems not to be the case. Then I thought the file might need (or not want) a blank line at the end to catch the last item in the file, but that doesn't seem to be the case either. And it doesn't have a problem with a two-word folder name, since one of my others has three.
The weirdest thing was when I moved the new entry up in the list, so it was no longer the last item, and it was still ignored.
And it really is ignored, the log is right: I extracted the contents of the excluded folder with TBIView and verified that the files were actual PST files that open in Outlook (plus, the image was MUCH larger than it should have been).
The manual says "Excluded files extracted from the image using TBIView or TBIMount will be full of zeros. An exception to this are very small files on NTFS (the contents of those files will be intact)."
This is NTFS. Is there possibly another exception to this: large Outlook PST files? Or is there some other explanation that I'm missing?
I've been using 2.97 releases (currently "e"). I don't know if the above happens with earlier releases. It's Server 2003R2, and the above is run from a batch.
However, the latest addition to my exclusion text file seems to be ignored. It's no different (except for the directory, which is definitely correct) than any of the others in the file. It looks like the example from the manual:
[k]\Outlook Archives\ >
Yet, when I look in the log file, I see the usual "Warning: Data excluded from files based on list" message followed only by my older five exclusions (they've been there a while), not the new one.
At first, I thought there might be a limit of 5 items in the exclusion file, but that seems not to be the case. Then I thought the file might need (or not want) a blank line at the end to catch the last item in the file, but that doesn't seem to be the case either. And it doesn't have a problem with a two-word folder name, since one of my others has three.
The weirdest thing was when I moved the new entry up in the list, so it was no longer the last item, and it was still ignored.
And it really is ignored, the log is right: I extracted the contents of the excluded folder with TBIView and verified that the files were actual PST files that open in Outlook (plus, the image was MUCH larger than it should have been).
The manual says "Excluded files extracted from the image using TBIView or TBIMount will be full of zeros. An exception to this are very small files on NTFS (the contents of those files will be intact)."
This is NTFS. Is there possibly another exception to this: large Outlook PST files? Or is there some other explanation that I'm missing?
I've been using 2.97 releases (currently "e"). I don't know if the above happens with earlier releases. It's Server 2003R2, and the above is run from a batch.