Kai Schaetzl wrote:
Philip Prindeville wrote on Thu, 18 May 2006 08:47:48 -0600:
How legitimate is email sent as
windows-1252?
Very, because broken Windows clients use it.
Kai
Ah, the "Strong Arm school of standards enforcement." ;-)
-Philip
Philip Prindeville wrote on Thu, 18 May 2006 08:47:48 -0600:
> How legitimate is email sent as
> windows-1252?
Very, because broken Windows clients use it.
Kai
--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philip Prindeville wrote:
> Jonathan Armitage wrote:
>
>> I see some spam with "windows-1252" or other unwanted character sets at
>> the start of the subject. I reject them via an Exim ACL, so SA doesn't
>> even have to scan them.
>>
>>
>
> Which
> Which brings up the subject... How legitimate is email sent as
> windows-1252?
>
> I see absolutely no reason to send it, since it offers no
> advantage over
> iso-8859-1
> or utf-8, and the RFC's are pretty clear about using the "smallest"
> encoding that
> will fit a message, i.e. usascii => i
Jonathan Armitage wrote:
>I see some spam with "windows-1252" or other unwanted character sets at
>the start of the subject. I reject them via an Exim ACL, so SA doesn't
>even have to scan them.
>
>
Which brings up the subject... How legitimate is email sent as
windows-1252?
I see absolutel
If anyone would like to make use of it, I ended up using:
# for mime headers...
mimeheader __CTYPE_MH_TEXT_PLAIN Content-Type =~ /text\/plain/i
mimeheader __CTYPE_MH_HTML Content-Type =~ /text\/html/i
# don't allow windows-1252 text attachments...
mimeheader __CTYPE_MH_WIN1252 Content-Type
Theo Van Dinter wrote:
On Mon, Apr 03, 2006 at 12:07:00PM -0600, Philip Prindeville wrote:
--=_NextPart_000_0016=_NextPart_000_0016
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
Using:
# don't allow windows-1252 text attachments...
header __CT
Theo Van Dinter wrote:
>On Mon, Apr 03, 2006 at 12:07:00PM -0600, Philip Prindeville wrote:
>
>
>>>--=_NextPart_000_0016=_NextPart_000_0016
>>>Content-Type: text/plain;
>>>charset="Windows-1252"
>>>Content-Transfer-Encoding: 7bit
>>>
>>>
>>>
>>Using:
>># don't allow windows
On Mon, Apr 03, 2006 at 12:07:00PM -0600, Philip Prindeville wrote:
> > --=_NextPart_000_0016=_NextPart_000_0016
> > Content-Type: text/plain;
> > charset="Windows-1252"
> > Content-Transfer-Encoding: 7bit
> >
> Using:
> # don't allow windows-1252 text attachments...
> header __CTYP
I was trying to filter messages like:
> Return-Path: <[EMAIL PROTECTED]>
> Received: from redfish-solutions.com (ppp125-53.dsl-coc.eth.net
> [61.11.125.53] (may be forged))
> by mail.redfish-solutions.com (8.13.1/8.13.1) with ESMTP id
> k1SGqvTs021448
> for <[EMAIL PROTECTED]>; Tue
10 matches
Mail list logo
