Re: built in content filtering

This is a discussion on Re: built in content filtering within the mailing.postfix.users forums, part of the Mail Servers and Related category; --=-XxzVcI2G7+M08vrpHMTM Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2004-10-31 at 19:06, Wietse ...


Go Back   Usenet Forums > Mail Servers and Related > mailing.postfix.users

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 11-01-2004
Robin Lynn Frank
 
Posts: n/a
Default Re: built in content filtering


--=-XxzVcI2G7+M08vrpHMTM
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2004-10-31 at 19:06, Wietse Venema wrote:
> Robin Lynn Frank:
> -- Start of PGP signed section.
> > I checked the docs but did not see (or didn't recognize) the answer to
> > the following:
> >=20
> > 1) What is the order of header and body checks (i.e., header first, bod=

y
> > second)?

>=20
> TABLE SEARCH ORDER
> For each line of message input, the patterns are applied
> in the order as specified in the table. When a pattern is
> found that matches the input line, the corresponding
> action is executed and then the next input line is
> inspected.
>=20
> > 2) If headers are checked first, is it possible to whitelist specific
> > mail to avoid a body check?

>=20
> BUGS
> Many people overlook the main limitations of header and
> body_checks rules. These rules operate on one logical
> message header or one body line at a time, and a decision
> made for one line is not carried over to the next line.
>=20
> I think header_checks(5) says it all (the above text comes with
> Postfix 2.1 and later).
>=20
> Wietse


Thanks, Wietse. As usual, when my ship comes in, I'm at the airport.
:-( Don't know where I was looking, but I missed it.

The good news is that I've found a solution. I'll use REDIRECT to a
user created for the purpose. That way, we don't risk rejecting list
mail, can examine the mail in question and our users are spared the
garbage.
--=20
Robin Lynn Frank
Director of Operations
Paradigm-Omega, LLC
http://www.paradigm-omega.com/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D
Spambots are welcome at http://paradigm-omega.net/cgi-bin/custmail.cgi
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D
No space left in message for a signature.

--=-XxzVcI2G7+M08vrpHMTM
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Sed quis custodiet ipsos custodes?

iD8DBQBBhdico0pgX8xyW4YRApjGAKCJuchXfkQEdGp82Eg4E0 3K2oPrswCfT2fK
kg72w4zJiXM4ZgjWdRGRAyQ=
=m0nW
-----END PGP SIGNATURE-----

--=-XxzVcI2G7+M08vrpHMTM--

Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 05:52 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0