autowhitelistforcedelivery.txt file weird entries |
Post Reply 
|
| Author | |
Terry 
Senior Member 
Joined: 06 February 2005 Status: Offline Points: 155 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: autowhitelistforcedelivery.txt file weird entriesPosted: 03 November 2015 at 8:09pm |
|
Since I upgraded to the newest release...we have been getting some really bizarre entries in our whitelist delivery file...like this:
昀栀㌀樀猀稀渀猀砀渀渀攀樀氀栀⬀爀攀挀攀椀瀀琀猀㴀洀攀猀猀愀最椀渀最⸀猀焀甀愀爀攀甀瀀⸀挀漀洀䀀戀漀甀渀挀攀猀⸀猀焀甀愀爀攀甀瀀⸀挀漀洀簀猀挀漀琀琀⸀猀椀琀渀攀爀䀀瀀漀爀琀漀昀瀀漀爀琀氀愀渀搀⸀挀漀洀ഀഀ 礀㈀ ㌀㌀䀀猀琀甀⸀栀漀猀攀椀⸀愀挀⸀樀瀀簀樀漀攀⸀洀漀氀氀甀猀欀礀䀀瀀漀爀琀漀昀瀀漀爀琀氀愀渀搀⸀挀漀洀ഀഀ 㤀㐀 ⴀ爀㌀ⴀ㌀㐀㈀㌀䀀爀攀琀甀爀渀⸀猀愀氀攀猀渀攀砀甀猀⸀挀漀洀簀爀椀挀栀愀爀搀⸀眀栀攀攀氀攀爀䀀瀀漀爀琀漀昀瀀漀爀琀氀愀渀搀⸀挀漀洀ഀഀ Now our users are complaining about previously whitelisted entries being blocked...what happened here...and there are lots of lines like this in the file...
|
|
 |
|
|
LogSat
Admin Group 
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 03 November 2015 at 9:08pm |
|
Terry,
The file is probably now encoded in unicode UTF16 instead of 8-bit ascii as before, but SpamFilter should be able to read it. Could you please zip it and email it to us at support at logsat dot com so we can double-check?
|
|
|
|
|
RobStagg
Newbie 
Joined: 05 December 2014 Status: Offline Points: 4 |
Post Options
Thanks(0)
Quote Reply
Posted: 05 November 2015 at 10:41am |
|
Were the log files and\or whitelist converted to Unicode as part of the upgrade? Is there a way to switch it back to ASCII? This has disabled a downstream process.
|
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 05 November 2015 at 2:41pm |
|
Starting from v4.6.1.119, SpamFilter supports the use of Unicode in the various blacklists/whitelists, which is very useful as it allows to specify keywords in foreign languages for searches in the subjects and body. As a consequence, SpamFilter's logfile and the various blacklist/whitelist files are now encoded in 16bit Unicode (specifically in UTF16 Little Endian) instead of UTF8.
There is no way to revert to ASCII other than reverting back to a version of SpamFilter prior to 4.6.1.119, and re-encoding the various config files back to ASCII. As a side-note, we can try to assist with the changes in your coding for the downstream process (to the best of our ability...!). If you want to contact me at support at logsat dot com we can try to help.
|
|
|
|
|
tcig
Newbie
Joined: 30 March 2005 Location: Germany Status: Offline Points: 9 |
Post Options
Thanks(0)
Quote Reply
Posted: 08 November 2015 at 4:00pm |
|
Made a Little script... it works fine.
:: Convert unicode to Ansicode :: was changed without announcement md ANSI for %%a in (*.log *.?log?) do type "%%a">"ANSI\%%a" for %%a in (*.log *.?log?) do attrib -r -h -s "%%a" cd ANSI :: for %%a in (*.txt *.?txt?) do move /y "%%a" ..\ cd.. :: rd ANSI
|
|
|
|
Topic Options|
Post Reply
|
|
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.180 seconds.