7 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] mailfilter finds matc...
FromSent OnAttachments
Michael McNeilMay 7, 2004 12:18 pm 
Robbie ScottMay 11, 2004 3:08 pm 
Sam VarshavchikMay 11, 2004 3:55 pm 
Martin List-PetersenMay 12, 2004 3:31 am 
Ron JohnsonMay 12, 2004 5:53 pm 
"Roger B.A. Klorese "May 12, 2004 6:04 pm 
Tony EarnshawMay 13, 2004 4:40 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] mailfilter finds matches in mime boundariesActions...
From:Tony Earnshaw (ton@billy.demon.nl)
Date:May 13, 2004 4:40:43 pm
List:net.sourceforge.lists.courier-maildrop

ons, 12.05.2004 kl. 00.08 skrev Robbie Scott:

When you do pattern matching on the body, you can match on any part of the body, even parts of the body that the user doesn't realize exists, like part separators (if that's what you call them). For example, a filter like this:

if ( ( /codin/:b )){ to $THE_FOLDER }

Catches things in the body like:

------=xxxxxxxxxxxxxxxxxxxxxxx Content-Type: text/plain; charset=u Content-Transfer-Encoding: 7bit

Is there a way to get body searches to avoid this? (I'm not sure I'm using the right vocabulary, but you get the idea.)

Yes, if you use Postfix 2.x (I use 2.1 stable ATM) and POSIX or PCRE (I use PCRE) body_checks. They will not catch header_checks or mime_header_checks (Postfix definitions as such) like those you quote. Moreover with PF, this is system-wide and not configurable per user. On the other hand, what you quote would include body text in PF, such as "coding", "(de|en)coding", "codine", etc and is /not/ a good filter ;)

--Tonni

--Tonni

--

We make out of the quarrel with others rhetoric but out of the quarrel with ourselves, poetry.

mail: billy - at - billy.demon.nl http://www.billy.demon.nl