Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Oct 2006 00:23:15 -0800
From:      Beech Rintoul <freebsd@alaskaparadise.com>
To:        "Ted Mittelstaedt" <tedm@toybox.placo.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Non English Spam
Message-ID:  <200610150023.38794.freebsd@alaskaparadise.com>
In-Reply-To: <001c01c6eff4$f77cd590$3c01a8c0@coolf89ea26645>
References:  <200610131712.46822.freebsd@alaskaparadise.com> <4530DA30.7060004@locolomo.org> <001c01c6eff4$f77cd590$3c01a8c0@coolf89ea26645>

next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1948279.keFqu9YnZE
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Saturday 14 October 2006 16:58, Ted Mittelstaedt wrote:
> ----- Original Message -----
> From: "Erik Norgaard" <norgaard@locolomo.org>
> To: "Beech Rintoul" <freebsd@alaskaparadise.com>
> Cc: <freebsd-questions@freebsd.org>
> Sent: Saturday, October 14, 2006 5:38 AM
> Subject: Re: Non English Spam
>
> > I have noted however, that some subscribers to this list write english
> > encoded in one of the above character sets, I don't know enough about
> > the character set definition, but it seems that English characters are a
> > subset of any character set?
> >
> > What is the recommended policy here? Should subscribers be advised to
> > change character set when posting to the list?
>
> No.  It's the responsibility of the person doing the filtering - in this
> case you -
> to exempt any known good e-mail sender from your filters.
>
> You know damn well that legitimate mailing list mail comes from
>
> mx2.freebsd.org (mx2.freebsd.org [216.136.204.119])
>
> it's right in the headers of the messages on the list.  You have no right
> to force other people to conform to what you feel is acceptable formatting
> of their message as long as they meet the SMTP rfc standards.  That's why
> we have RFC's.
>
> If everyone did what your proposing then senders would have hundreds
> of different rules they would have to follow, over and above the normal
> RFCs.

Ted, thank you for the bit of sanity.=20

As for me, Dr. Seaman's suggestions (earlier in this thread) have  brought=
=20
things back to tolerable levels. I have had many responses and most probabl=
y=20
work. But, I need a solution I can install on client machines (and my own)=
=20
that doesn't require exotic scripts.

I thoroughly parsed my maillog and so far nothing important has landed
in /dev/null.=20

Once again, thanks to everyone who responded.

Beech


=2D-=20

=2D------------------------------------------------------------------------=
=2D-------------
Beech Rintoul - Sys. Administrator - beech@alaskaparadise.com
/"\   ASCII Ribbon Campaign  | Alaska Paradise
\ / - NO HTML/RTF in e-mail  | 201 East 9Th Avenue Ste.310
 X  - NO Word docs in e-mail | Anchorage, AK 99501
/ \  - Please visit Alaska Paradise - http://www.alaskaparadise.com
=2D------------------------------------------------------------------------=
=2D-------------












--nextPart1948279.keFqu9YnZE
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQBFMfAKR5sEeCt9j00RAqa/AJwNHuSJrY/OmkpJiPjkp2sNxvqUdACgmi3N
dLikg/xhsybTqOzXQEboVuY=
=F7B9
-----END PGP SIGNATURE-----

--nextPart1948279.keFqu9YnZE--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610150023.38794.freebsd>