Re: encoding issue with header_checks Windows-1252

2019-07-20 Thread Wietse Venema
Stefan Bauer: > So you are saying that the client probably decoded the subject. I am saying that the subject differs from what you have. There can be any number of reasons including encoding, and incuding the possibility that someone gave you text that was not part of the message. Wietse

Re: encoding issue with header_checks Windows-1252

2019-07-20 Thread Stefan Bauer
So you are saying that the client probably decoded the subject. Thank you Wietse! What might be the best way, to capture all kind of encodings for a specific string in subject? We let our users choose mail routing path, if string is part of subject. Works with all clients, just not with some

Re: encoding issue with header_checks Windows-1252

2019-07-20 Thread Wietse Venema
Stefan Bauer: > I dont get it. Testing the above correctly shows > > Subject: > =?Windows-1252?Q?[Cleartext]_Webinar_=84Noch_keine_55_und_ab_in_die_GKV=93?= > FILTER cleartext: > > But the e-mail itself was not passed to the FILTER cleartext. Consider the possibiliy that the message subject is

Re: encoding issue with header_checks Windows-1252

2019-07-18 Thread Stefan Bauer
I dont get it. Testing the above correctly shows Subject: =?Windows-1252?Q?[Cleartext]_Webinar_=84Noch_keine_55_und_ab_in_die_GKV=93?= FILTER cleartext: But the e-mail itself was not passed to the FILTER cleartext. Above subject was extracted from mail client. I believe, there is something going

Re: encoding issue with header_checks Windows-1252

2019-07-18 Thread Wietse Venema
Stefan Bauer: > Hi, > > header_checks = regexp:/etc/postfix/headerstring > /^Subject: .*\[cleartext\].*/ FILTER cleartext: > > And now, there is the following mail-Subject, that did not trigger the > above FILTER and i dont see why: > > Subject: >

Re: encoding issue with header_checks Windows-1252

2019-07-18 Thread Stefan Bauer
only this single filter is present - no other filters. Unfortunately thats not enough to trigger the filter. Am Do., 18. Juli 2019 um 14:00 Uhr schrieb pasvon : > What does the complete file /etc/postfix/headerstring look like? > Does another line match a filter action and override the desired

Re: encoding issue with header_checks Windows-1252

2019-07-18 Thread Matus UHLAR - fantomas
On 18.07.19 13:42, Stefan Bauer wrote: man 5 header_checks By default, regexp : and pcre : patterns are case *insensitive*. sorry, misread. Should be more careful.. Am Do., 18. Juli 2019 um 13:40

Re: encoding issue with header_checks Windows-1252

2019-07-18 Thread pasvon
What does the complete file /etc/postfix/headerstring look like? Does another line match a filter action and override the desired result? Have you defined any other header_checks (body for example)? That should be enough, too: /^Subject: .*\[cleartext\]/ FILTER cleartext: -- Sent from:

Re: encoding issue with header_checks Windows-1252

2019-07-18 Thread Stefan Bauer
man 5 header_checks By default, regexp : and pcre : patterns are case *insensitive*. Am Do., 18. Juli 2019 um 13:40 Uhr schrieb Matus UHLAR - fantomas < uh...@fantomas.sk>: > On 18.07.19 13:35, Stefan

Re: encoding issue with header_checks Windows-1252

2019-07-18 Thread Matus UHLAR - fantomas
On 18.07.19 13:35, Stefan Bauer wrote: header_checks = regexp:/etc/postfix/headerstring /^Subject: .*\[cleartext\].*/ FILTER cleartext: And now, there is the following mail-Subject, that did not trigger the above FILTER and i dont see why: Subject:

encoding issue with header_checks Windows-1252

2019-07-18 Thread Stefan Bauer
Hi, header_checks = regexp:/etc/postfix/headerstring /^Subject: .*\[cleartext\].*/ FILTER cleartext: And now, there is the following mail-Subject, that did not trigger the above FILTER and i dont see why: Subject: =?Windows-1252?Q?[Cleartext]_Webinar_=84Noch_keine_55_und_ab_in_die_GKV=93?= Any