Changes in PCRE handling postfix etch vs lenny?

2010-01-19 Thread Harakiri
Hi, after upgrading a machine from etch to lenny i get the following warning postfix/smtpd[23231]: warning: pcre map /etc/postfix/postfix_rbl_check, line 0: ignoring unrecognized request main.cf: check_client_access pcre:/etc/postfix/postfix_rbl_check file: reject_rbl_client zen.spamhaus.or

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-19 Thread Noel Jones
On 1/19/2010 9:15 AM, Harakiri wrote: Hi, after upgrading a machine from etch to lenny i get the following warning postfix/smtpd[23231]: warning: pcre map /etc/postfix/postfix_rbl_check, line 0: ignoring unrecognized request main.cf: check_client_access pcre:/etc/postfix/postfix_rbl_check f

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-19 Thread Wietse Venema
Harakiri: > Hi, > > after upgrading a machine from etch to lenny i get the following warning > > postfix/smtpd[23231]: warning: pcre map /etc/postfix/postfix_rbl_check, line > 0: ignoring unrecognized request > > main.cf: > > check_client_access pcre:/etc/postfix/postfix_rbl_check > > file:

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-19 Thread Harakiri
--- On Tue, 1/19/10, Wietse Venema wrote: > > That is not a valid PCRE file entry, and it has never been > valid. > > Postfix promises compatibility only for behavior that is > promised > by documentation. Postfix behavior for invalid inputs is > subject > to change without prior warning. ok

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-19 Thread /dev/rob0
On Tue, Jan 19, 2010 at 07:57:02AM -0800, Harakiri wrote: > --- On Tue, 1/19/10, Wietse Venema wrote: > > > postfix/tlsmgr[23233]: warning: request to update > > table btree:/var/spool/postfix/smtpd_scache in non-postfix > > directory /var/spool/postfix > > > > See the RELEASE_NOTES file. Postfix

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-19 Thread Noel Jones
On 1/19/2010 9:57 AM, Harakiri wrote: See the RELEASE_NOTES file. Postfix documentation is created with a great deal of effort. Don't let it go to waste. I dont agree on this one (and this list is maybe not the right place for this) - i expect the debian package maintainer to take care of any

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-19 Thread Harakiri
--- On Tue, 1/19/10, Noel Jones wrote: > From: Noel Jones > Subject: Re: Changes in PCRE handling postfix etch vs lenny? > To: postfix-users@postfix.org > Date: Tuesday, January 19, 2010, 11:42 AM > On 1/19/2010 9:57 AM, Harakiri > wrote: > >> See the RELEASE_NOTES

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-19 Thread Noel Jones
On 1/19/2010 10:51 AM, Harakiri wrote: --- On Tue, 1/19/10, Noel Jones wrote: From: Noel Jones Subject: Re: Changes in PCRE handling postfix etch vs lenny? To: postfix-users@postfix.org Date: Tuesday, January 19, 2010, 11:42 AM On 1/19/2010 9:57 AM, Harakiri wrote: See the RELEASE_NOTES

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-19 Thread Stan Hoeppner
Well, there's one positive side to this thread Noel. Your reply to "undisclosed recipients" instead of the list address broke my postfix-users sort filter. I just spent 20 minutes trying to figure it out. I tried "received" and "return-path" and all kinds of header checks in the T-Bird message

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-19 Thread John Peach
On Tue, 19 Jan 2010 17:15:59 -0600 Stan Hoeppner wrote: > > Well, there's one positive side to this thread Noel. Your reply to > "undisclosed > recipients" instead of the list address broke my postfix-users sort filter. I > just spent 20 minutes trying to figure it out. I tried "received" an

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-19 Thread Stan Hoeppner
/dev/rob0 put forth on 1/19/2010 10:41 AM: >> I have to manually install postfix-doc to find a >> /usr/share/doc/postfix/RELEASE_NOTES.gz file. > > This is worth complaining about, IMO. If a user should make the > conscious decision to not install the documentation with a given > package, that's

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-20 Thread mouss
Stan Hoeppner a écrit : > Well, there's one positive side to this thread Noel. Your reply to > "undisclosed > recipients" instead of the list address broke my postfix-users sort filter. I > just spent 20 minutes trying to figure it out. I tried "received" and > "return-path" and all kinds of he

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-20 Thread Stan Hoeppner
mouss put forth on 1/20/2010 2:26 PM: >> That's just plain silly. > > Keep calm Stan! I was calm. I had no exclamation point there. ;) > Consider this to be a good lesson: your filtering approach is > suboptimal. For most mailing lists, you can use one of: It _was_ less than optimal. > List-

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-21 Thread Charles Marcus
On 2010-01-19, Stan Hoeppner (s...@hardwarefreak.com) wrote: > So now I get to file a bug report on T-Bird as it's clearly not processing the > headers correctly or obeying "custom" headers I plug in. Hell, it won't even > filter on Sender: owner-postfix-us...@postfix.org for Pete's sake and Sende

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-21 Thread Stan Hoeppner
Charles Marcus put forth on 1/21/2010 6:05 AM: > On 2010-01-19, Stan Hoeppner (s...@hardwarefreak.com) wrote: >> So now I get to file a bug report on T-Bird as it's clearly not processing >> the >> headers correctly or obeying "custom" headers I plug in. Hell, it won't even >> filter on Sender: o

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-22 Thread Charles Marcus
On 2010-01-21 8:23 PM, Stan Hoeppner wrote: > Thanks for the heads up. Yes, I'm using IMAP and TB3. So I'm sure > this is the same bug. Interestingly, like I said, the filter on > Sender works fine for newly arriving messages. It just doesn't work > on messages already in the inbox when running

Re: Changes in PCRE handling postfix etch vs lenny?

2010-01-22 Thread Charles Marcus
On 2010-01-22 5:36 PM, Charles Marcus wrote: > Here's the bug: Sorry, meant to send that direct to Stan...