[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4692: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4694: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4695: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4696: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
Spamihilator • Thema anzeigen - New plugin: Misnamed Filter
Seite 2 von 4

Misnamed Filter v0.2

BeitragVerfasst: 27. Feb 2007, 14:43
von AlexV

BeitragVerfasst: 27. Feb 2007, 15:36
von anbuva
Hallo AlexV!

Unfortunately, a fault has crept in in your Posting; the correct address should be well:


Thanks a lot, for this good PlugIn! :D

Regards
anbuva

BeitragVerfasst: 27. Feb 2007, 16:22
von AlexV
Hello anbuva,

How careless of me, thank you for pointing it out. I have corrected it in the post.

Alex

Misnamed Filter v0.3

BeitragVerfasst: 11. Apr 2007, 21:01
von AlexV
As requested, here is an updated version of Misnamed Filter for compatibility with Spamihilator v0.9.9.25. I will leave it available here for a few days, then if it looks stable I'll update the entry in the plugins database to point to it too.



The only change to this version is that it will now check the Spamihilator setting (in the registry) for whether to store settings in the per-user folder or the program folder, and save its configuration xml file to the appropriate place.

If you install it over an existing installation of 0.2 the installer should move the existing config file (if necessary) so that you don't lose your settings.

BeitragVerfasst: 12. Apr 2007, 12:17
von Chactory

BeitragVerfasst: 12. Apr 2007, 21:06
von anbuva

BeitragVerfasst: 22. Apr 2007, 00:43
von Chactory

BeitragVerfasst: 22. Apr 2007, 08:09
von AlexV
Hello,

I'm sorry, I'm not sure I understand. This filter applies the regexes in a case-insensitive way, so "Chactory Miller-Smith" and "Chactory Miller-smith" should both be matched by the same regex.

Burkart has suggested that regexes should be case-sensitive, so that those two names would count as different and need different regexes to match them (or one regex specially designed to match both). My argument was that email addresses and names should be insensitive; your post serves as an example of why.

If you are getting false positive matches, then please try using the Test button in the configuration window. If it gives the correct result there, then it is a bug with the filter, and I will try and fix it. If it says it is spam in the test window, then there is some problem with the regexes for your name and email address.

In either case, if you send me the "Misnamed Filter.settings.xml" file, I can try and figure out what the problem is.

Regards,

Alex Vallat

BeitragVerfasst: 22. Apr 2007, 13:27
von Chactory

Re: New plugin: Misnamed Filter

BeitragVerfasst: 4. Mai 2008, 11:40
von Mugros
I noticed that the filter doesn't deal with encoded names.
It is a little bit ironic, but the Spamihilator forum sent me a notification with my name in encoded form:
To: "=?UTF-8?B?TXVncm9z?="
I added this string to the known names, but it would be better if the filter could deal with different encodings.

Re: New plugin: Misnamed Filter

BeitragVerfasst: 4. Mai 2008, 19:32
von AlexV
Thank you for the suggestion. If I can find any sample code on how to decode headers in that form, I'll add the functionality. Otherwise, I might get round to writing some myself, but given that which defines the encoding looks like a complete mess and a nightmare to implement, that may not happen so soon.

Alex

Re: New plugin: Misnamed Filter

BeitragVerfasst: 4. Mai 2008, 19:38
von Mugros
I found some code in javascript here:
http://www.webtoolkit.info/javascript-base64.html
seems to work (encoded name in the demo is the same).
Maybe the code helps

Re: New plugin: Misnamed Filter

BeitragVerfasst: 4. Mai 2008, 20:12
von AlexV
Thank you for that, but it isn't the actual base 64 encoding that is the problem. Encoded headers like this can be byte-encoded in either base 64 or quoted printable, then further encoded in any named text encoding (in your example it happens to be utf-8).

What I have found is that there is an internal .net function which can decode these, but it is not made publicly accessible. I can put code in to force it to be called anyway, but as it is non-public it could easily stop working when the .net framework is updated. I'm considering using it anyway, but having it fall back to simply not decoding it if the function can't be found.

Alex

Experimental version 0.4

BeitragVerfasst: 5. Mai 2008, 10:41
von AlexV
Here is a new experimental version which adds support for encoded display names:



I'm not sure how reliable this is, but it should work. If it doesn't, it should fall back to the old behaviour of just using the raw encoded display name anyway.

Checks are made against both the raw encoded and the decoded display name, so if you already have rules which check against encoded names, they don't need updating. If you have the time, it might be worth updating them anyway, though, that way the display name will match however it is encoded. For example, a rule of "=?UTF-8?B?QWxleFY=?=" would only match if the incoming email had exactly that as the display name. A rule of "AlexV" would match against "=?UTF-8?B?QWxleFY=?=", and "=?iso-8859-1?Q?Al=65xV?=", and "AlexV".

To test this functionality, run the configurator (you can reach this by clicking the Configure button in the Spamihilator plugins page with Misnamed Filter selected). Click the Test button, and in the "Name" box, enter or paste an encoded value. If a tooltip appears below it showing the decoded value for it, then it should be working properly.

Please let me know if you have any issues with this new version!

Regards,

Alex

Re: Experimental version 0.4

BeitragVerfasst: 6. Mai 2008, 09:11
von anbuva
Hallo AlexV!

Thank you :D

Kind Regards
anbuva