On Fri, Jul 23, 2010 at 06:57:33PM -0500, Jared Johnson wrote:
> > It seems like
> > all you have to do to get around the etc. problem is to wait a
> > little longer before applying the fixup -- allow the semicolon to match in
> > the hostname search and then strip it out.
>
> My bad.. I guess t
>> It seems like
>> all you have to do to get around the etc. problem is to wait a
>> little longer before applying the fixup -- allow the semicolon to match
>> in
>> the hostname search and then strip it out.
>
> My bad.. I guess the plugin currently only fixes up '&#\d\d\d' encoding,
> not et
> It seems like
> all you have to do to get around the etc. problem is to wait a
> little longer before applying the fixup -- allow the semicolon to match in
> the hostname search and then strip it out.
My bad.. I guess the plugin currently only fixes up '&#\d\d\d' encoding,
not etc. maybe i'
Ah, I tried it in my own FF and the trick still works :) It seems like
all you have to do to get around the etc. problem is to wait a
little longer before applying the fixup -- allow the semicolon to match in
the hostname search and then strip it out. Attached a patch, untested
(though the same
On Wed, Jul 21, 2010 at 07:54:30AM -0500, Jared Johnson wrote:
> Unlike the other bits of "dodge this sort of munging" operations,
> examining my test results and asking uncle google has not made it clear to
> me what "inserted-semicolon munging" really is. Can anyone shed light on
My memory of t
I am trying to install autowhitelist_captcha Version 1.0 by Marc
Sebastian Pelzer, and running into a problem. Hope someone can point me
in the right direction.
When sen...@senderdomain is sending me an email at mydomain, she is
receiving back a "failure notice" : "550 Sorry, you are not allow
