In an older episode (Sunday 01 May 2005 02:07), Loren Wilton wrote:
Again and again, we receive messages that contain stuff like
a href=3dhttp://advinc-ma=2enetfirms=2ecom/;
instead of
a href=http://advinc-ma.netfirms.com/;
That prevents uri / body rules like e.g.
no/yes
Again and again, we receive messages that contain stuff like
a href=3dhttp://advinc-ma=2enetfirms=2ecom/;
instead of
a href=http://advinc-ma.netfirms.com/;
That prevents uri / body rules like e.g.
/netfirms\.com/
and URIBL rules from being triggered. I wonder if there is some function to
On Sat, Apr 30, 2005 at 01:27:39PM +0200, wolfgang wrote:
Again and again, we receive messages that contain stuff like
a href=3dhttp://advinc-ma=2enetfirms=2ecom/;
instead of
a href=http://advinc-ma.netfirms.com/;
I wonder if there is some function to
automatically de-code such items
In an older episode (Saturday 30 April 2005 14:45), Theo Van Dinter wrote:
=3d is quoted-printable encoding for =, =2e for ., etc...
SA handles proper encoding (it handles a lot of non-proper encoding
as well), but doesn't make guesses if the MIME part says there is no
encoding.
Without
wolfgang wrote:
In an older episode (Saturday 30 April 2005 14:45), Theo Van Dinter
wrote:
=3d is quoted-printable encoding for =, =2e for ., etc...
SA handles proper encoding (it handles a lot of non-proper encoding
as well), but doesn't make guesses if the MIME part says there is no
On Sat, 30 Apr 2005, Theo Van Dinter wrote:
On Sat, Apr 30, 2005 at 01:27:39PM +0200, wolfgang wrote:
Again and again, we receive messages that contain stuff like
a href=3dhttp://advinc-ma=2enetfirms=2ecom/;
instead of
a href=http://advinc-ma.netfirms.com/;
I wonder if there is some
On Sat, Apr 30, 2005 at 02:41:57PM -0500, David B Funk wrote:
We've already gone 'round this issue in past discussions on this list, the
DEVs reply was, maybe 'fixed' in future releases.
Ok, fair enough. Then FYI: 3.1 handles the lowercase version. :)
--
Randomly Generated Tagline:
I was up
