Re: International Domain Characters and Header Checks

On Thu, May 26, 2022 at 11:35:05PM +0200, Benny Pedersen wrote: > > SMTPUTF8 is enabled. > > so there is dns servers with domains in utf8 existing ? > > all my known dns servers uses idn, not eai, postfix imho need to convert > eai to idn dns to know if domain exists on dns > > to block domain

Re: International Domain Characters and Header Checks

quot;. All you > > need to do for that is edit the regexp/pcre table with a UTF-8 > > enabled editor, and type a literal "ĕ" into the pattern. > > > > $ echo ĕĕ | (LANG=C LC_CTYPE=C LC_ALL=C egrep ĕĕ) > > ĕĕ > > Sorry, I'm not underst

Re: International Domain Characters and Header Checks

On 2022-05-26 22:39, Bryan K. Walton wrote: On Sat, May 21, 2022 at 08:37:06AM -0400, Viktor Dukhovni wrote: On Fri, May 20, 2022 at 03:54:36PM -0500, Bryan K. Walton wrote: SMTPUTF8 is enabled. so there is dns servers with domains in utf8 existing ? all my known dns servers uses idn, not

Re: International Domain Characters and Header Checks

nt at the > SMTP stage. Any header checks on "Return-Path" are pointless. > > Instead, use "check_sender_access", since the content of the > Return-Path header added during final delivery is the envelope > sender address. Thanks for the reply, Viktor.

Re: International Domain Characters and Header Checks

On Fri, May 20, 2022 at 03:54:36PM -0500, Bryan K. Walton wrote: > We are trying to do some header checks that block on both the From and > Return Path header, but that also block some addresses with > international characters in them. Characters like: The "Return-Path" hea

International Domain Characters and Header Checks

We are trying to do some header checks that block on both the From and Return Path header, but that also block some addresses with international characters in them. Characters like: ù, ǔ, ɫ, ɇ, etc. I've read this page: https://www.postfix.org/SMTPUTF8_README.html and I understand that h

Re: Setting Up Header Checks

Austin Witmer: > Hello all! > > I managed to get milter-regex installed on my ubuntu server now by > converting an rpm package to deb. My next question is how to I > incorporate milter-regex into postfix? Postfix configuration: https://www.postfix.org/MILTER_README.html To keep it simple I sug

Re: Setting Up Header Checks

Hello all! I managed to get milter-regex installed on my ubuntu server now by converting an rpm package to deb. My next question is how to I incorporate milter-regex into postfix? Many thanks, On 3/5/22 8:05 AM, Benny Pedersen wrote: On 2022-03-05 15:01, Ralph Seichter wrote: * Austin Witm

Re: Setting Up Header Checks

On 2022-03-05 15:01, Ralph Seichter wrote: * Austin Witmer: What do I need to modify in the Makefile.linux file for my Ubuntu system? Who knows. You did not provide logs or error messages. Also, nobody but yourself knows the specifics of your platform. In any case, this is not a Postfix issu

Re: Setting Up Header Checks

* Austin Witmer: > What do I need to modify in the Makefile.linux file for my Ubuntu > system? Who knows. You did not provide logs or error messages. Also, nobody but yourself knows the specifics of your platform. In any case, this is not a Postfix issue. Daniel Hartmeier, the author of milter-r

Re: Setting Up Header Checks

[ Written in the professional reading direction. ] Le (on) 04/03/2022, Austin Witmer a écrit (wrote): | For some reason I can’t make Milter-regex install on ubuntu? The “make” command gives me an error when I try to run it. Does it have to run on a BSD based server? Hello Austin, A basic copy

Re: Setting Up Header Checks

To be honest, this is the first install from source that I’ve attempted. I’m a total noob at this, so if someone wishes to help me out further with getting milter-regex installed on Ubuntu, I wouldn’t mind. Maybe I will end up trying one of the other options that were suggested . . . Thanks for

Re: Setting Up Header Checks

What do I need to modify in the Makefile.linux file for my Ubuntu system? short answer: to whatever YOUR system, and your interests, need i don't use ubuntu, so can't help you specifically i strongly suggest you look at the defaults, and modify path accordingly for your ubu sys; if you're buil

Re: Setting Up Header Checks

See my question below. > On Mar 4, 2022, at 3:08 PM, PGNet Dev wrote: > > On 3/4/22 4:46 PM, Wietse Venema wrote: >> Austin Witmer: >>> For some reason I can't make Milter-regex install on ubuntu? The >>> "make" command gives me an error when I try to run it. Does it >>> have to run on a BSD bas

Re: Setting Up Header Checks

On 3/4/22 4:46 PM, Wietse Venema wrote: Austin Witmer: For some reason I can't make Milter-regex install on ubuntu? The "make" command gives me an error when I try to run it. Does it have to run on a BSD based server? Did you try apt-get? Wietse sigh. https://packages.ubuntu.com/

Re: Setting Up Header Checks

Dnia 4.03.2022 o godz. 16:46:53 Wietse Venema pisze: > Austin Witmer: > > For some reason I can't make Milter-regex install on ubuntu? The > > "make" command gives me an error when I try to run it. Does it > > have to run on a BSD based server? > > Did you try apt-get? milter-regex is not in th

Re: Setting Up Header Checks

Austin Witmer: > For some reason I can't make Milter-regex install on ubuntu? The > "make" command gives me an error when I try to run it. Does it > have to run on a BSD based server? Did you try apt-get? Wietse

Re: Setting Up Header Checks

For some reason I can’t make Milter-regex install on ubuntu? The “make” command gives me an error when I try to run it. Does it have to run on a BSD based server? > On Feb 26, 2022, at 3:37 PM, Wietse Venema wrote: > > nt to make tests indpendent of

Re: Setting Up Header Checks

Wietse Venema: > Austin Witmer: > > So, I am needing some help with some headers checks I am doing on my > > postfix mail server . . . > > > > It is my understanding that header checks are processed line by line, > > No. The manpage says: > >Each

Re: Setting Up Header Checks

Thanks for all the replies! I appreciate it. > On Feb 26, 2022, at 2:52 PM, Viktor Dukhovni > wrote: > > On Sat, Feb 26, 2022 at 02:14:42PM -0700, Austin Witmer wrote: > >> It is my understanding that header checks are processed line by line, > > That understanding

Re: Setting Up Header Checks

On Sat, Feb 26, 2022 at 02:14:42PM -0700, Austin Witmer wrote: > It is my understanding that header checks are processed line by line, That understanding is correct. > but I am seeing some behavior that makes me question that. You've confused yourself by misinterpreting what yo

Re: Setting Up Header Checks

Austin Witmer: > So, I am needing some help with some headers checks I am doing on my postfix > mail server . . . > > It is my understanding that header checks are processed line by line, No. The manpage says: Each message header or message body line is compared agains

Re: Setting Up Header Checks

* Austin Witmer: > It is my understanding that header checks are processed line by line If you want to enforce rules based on a combination of message headers, you should use a milter which can operate at the beginning of the SMTP DATA phase. At that time, all headers are available. I

Setting Up Header Checks

So, I am needing some help with some headers checks I am doing on my postfix mail server . . . It is my understanding that header checks are processed line by line, but I am seeing some behavior that makes me question that. I am wanting postfix to allow a message to be delivered if it is sent

Re: Problems with header checks

On Fr, Nov 08, 2019 at 03:31:05 +0100, Jaroslaw Rafa wrote: But in that case probably LDA is the best place to do such change. Some time ago I was doing something similar via procmail. I found a great program for procmail: https://fex.belwue.de/fstools/#aw2re It fixes the subject and can remov

Re: Problems with header checks

Stephan Seitz: > On Fr, Nov 08, 2019 at 03:31:05 +0100, Jaroslaw Rafa wrote: > >But in that case probably LDA is the best place to do such change. Some > >time ago I was doing something similar via procmail. > > Yes, I could do the same with procmail. But procmail will probably like > postfix us

Re: Problems with header checks

On Fr, Nov 08, 2019 at 03:31:05 +0100, Jaroslaw Rafa wrote: But in that case probably LDA is the best place to do such change. Some time ago I was doing something similar via procmail. Yes, I could do the same with procmail. But procmail will probably like postfix use the encoded subject, so I

Re: Problems with header checks

On 11/8/19 6:31 AM, Jaroslaw Rafa wrote: > If you do it on incoming mail only, and after DKIM signature has already > been verified, then I think there's no problem. Am I right? Not always, because some people use tools that verify the signature later on, such as this one: https://github.com/li

Re: Problems with header checks

Dnia 8.11.2019 o godz. 15:23:52 Stephan Seitz pisze: > > But the warning about breaking DKIM signatures if I change the > subject line is of course a valid one. If you do it on incoming mail only, and after DKIM signature has already been verified, then I think there's no problem. Am I right? B

Re: Problems with header checks

On Fr, Nov 08, 2019 at 03:11:34 +0100, Jaroslaw Rafa wrote: If I understand the OP correctly, he is trying to solve the problem of e-mail clients using other prefixes instead of "Re:" for replies (for example "AW:" or "Odp:" - these are among a few I encountered myself). When you exchange emails

Re: Problems with header checks

Dnia 8.11.2019 o godz. 14:27:18 Christian Kivalo pisze: > > I don't think that postfix is the right tool for this job, on the other > hand I don't really see the problem you're trying to solve. If I understand the OP correctly, he is trying to solve the problem of e-mail clients using other pref

Re: Problems with header checks

On November 8, 2019 1:53:13 PM GMT+01:00, Stephan Seitz wrote: >On Fr, Nov 08, 2019 at 01:44:53 +0100, Stephan Seitz wrote: >>Has anyone an idea how I can debug this further? Or why it is only >>sometimes working? > >I think I’ve found the problem. It happens if the subject has non-ASCII > >c

Re: Problems with header checks

On Fr, Nov 08, 2019 at 01:44:53 +0100, Stephan Seitz wrote: Has anyone an idea how I can debug this further? Or why it is only sometimes working? I think I’ve found the problem. It happens if the subject has non-ASCII characters to the line looks like: =?UTF-8?Q?Aw=3A_Weinprobe_gut_=C3=BCber

Problems with header checks

Hi! I’m using Debian 10 with postfix 3.4.5. Trying to solve the problem with non-Re subjects I have found a regex for header checks. So I have a „/etc/postfix/header_check.pcre” with: /eSubject:\s*((RE|AW|Aw|Antw|Antwort|RES|SV):\s*)+(.*)$/ REPLACE Subject: Re: $3 In main.cf: header_checks

Re: Is it possible to use header checks on multiple headers

* Noel Jones: > If you need arbitrary header checks, milter-regex can do complex > regular expression matching on multiple headers or the body of the > message. I can recommend milter-regex. It is small, effective, and easy to configure. Also, the author added a useful feature after I

Re: Is it possible to use header checks on multiple headers

at writing milters and that one is beyond me for the moment. Look at postfwd milter (http://postfwd.org/), where a single rule can combine tests on different headers. postfwd is a policy service (not a milter), and doesn't see headers. It *can* combine tests on multiple envelope

Re: Is it possible to use header checks on multiple headers

On Tue, 16 Apr 2019 at 10:25, Nick Howitt wrote: > > > On 13/04/2019 09:26, Andrey Repin wrote: > > Greetings, Nick Howitt! > > > >> I am receiving some not very nice spam and I was wondering if I could > >> use as a single filter: > >> To: contains mydomain > >> From: is the same as To: (inside

Re: Is it possible to use header checks on multiple headers

On 13/04/2019 09:26, Andrey Repin wrote: Greetings, Nick Howitt! I am receiving some not very nice spam and I was wondering if I could use as a single filter: To: contains mydomain From: is the same as To: (inside < and >) Return-Path: is not from my domain Or am I using completely the wrong

Re: Is it possible to use header checks on multiple headers

Greetings, Nick Howitt! > I am receiving some not very nice spam and I was wondering if I could > use as a single filter: > To: contains mydomain > From: is the same as To: (inside < and >) > Return-Path: is not from my domain > Or am I using completely the wrong tool for this? If you search l

Is it possible to use header checks on multiple headers

I am receiving some not very nice spam and I was wondering if I could use as a single filter: To: contains mydomain From: is the same as To: (inside < and >) Return-Path: is not from my domain Or am I using completely the wrong tool for this? Thanks, Nick

Adding BCC in sender/header checks

I am wondering if there is an easy way to add a BCC to an email in the sender/header checks, similar to REDIRECT but to send it to my redirect email and to the original recipient. I'm aware of recipient_bcc_maps but if I understand it correctly, that adds BCC to all emails of a parti

Re: Prioritize header checks

ntent filter. > and content filter it this case means post-queue filter? Background is that my header checks should match headers (ex marked already as spam by sending server) of messages which I do not want to feed to my proxy filter. As processing msg via my proxy filter invokes 3 av-scanners,

Re: Prioritize header checks

> On Nov 9, 2017, at 12:53 PM, Tobi wrote: > > I have a content filter running in prequeue mode to which postfix talks > via smtpd_proxy_filter. Best to call that a "proxy filter" to avoid confusion. > Runs fine, but ;-) it seems to me that postfix header checks are

Prioritize header checks

Hi list I have a content filter running in prequeue mode to which postfix talks via smtpd_proxy_filter. Runs fine, but ;-) it seems to me that postfix header checks are evaluated after the msg has been processed by the content filter. Is it somehow possible to tell postfix to run those checks

Re: MIME header checks matching

Hi, On Wed, Jun 14, 2017 at 2:41 PM, Andreas Schamanek wrote: > > On Wed, 14 Jun 2017, at 12:34, Noel Jones wrote: > >> > I have a series of mime patterns to automatically reject file types >> > including com, bat, exe, etc. It appears one pattern is matching >> > incorrectly, ... >> >> Rather th

Re: MIME header checks matching

On Wed, 14 Jun 2017, at 12:34, Noel Jones wrote: > > I have a series of mime patterns to automatically reject file types > > including com, bat, exe, etc. It appears one pattern is matching > > incorrectly, ... > > Rather than try to debug your expression, I'll refer you to the nice > example o

Re: MIME header checks matching

On 6/14/2017 7:16 AM, Alex wrote: > Hi, > > I have a series of mime patterns to automatically reject file types > including com, bat, exe, etc. It appears one pattern is matching > incorrectly, and I could use some help making it more accurate. I > don't know if it's something yahoo is doing to th

MIME header checks matching

Hi, I have a series of mime patterns to automatically reject file types including com, bat, exe, etc. It appears one pattern is matching incorrectly, and I could use some help making it more accurate. I don't know if it's something yahoo is doing to their outgoing mail or the result of this user's

Re: Antispamming with header checks and regexp

On 2017-02-07 10:12, Ralph Corderoy wrote: Hi Istvan, Noel Jones wrote: > Remember that header_checks won't match encoded subjects We need to see the raw Subject header from the email that failed to match. It was probably encoded. $ scan -forma '%{subject}' . =?UTF-8?B?VGhpcyBpcyBzc

Re: Antispamming with header checks and regexp

Hi Istvan, > Noel Jones wrote: > > Remember that header_checks won't match encoded subjects We need to see the raw Subject header from the email that failed to match. It was probably encoded. $ scan -forma '%{subject}' . =?UTF-8?B?VGhpcyBpcyBzcGFtLgo=?= $ scan -forma '%(decode{subje

Re: Antispamming with header checks and regexp

On 2017-02-06 23:19, Noel Jones wrote: On 2/6/2017 3:23 PM, Istvan Prosinger wrote: Hi All, and Happy New Year with a little delay :) Comming to spam, header checks are one tool that I use frequently to prevent it. So, amongst all, I have this: if !/^Subject: (.*)[Aa]liexpress/ /^Subject

Re: Antispamming with header checks and regexp

On 2017-02-06 22:56, Dominic Raferd wrote: On 6 February 2017 at 21:23, Istvan Prosinger wrote: Hi All, and Happy New Year with a little delay :) Comming to spam, header checks are one tool that I use frequently to prevent it. So, amongst all, I have this: if !/^Subject: (.*)[Aa]liexpress

Re: Antispamming with header checks and regexp

On 2/6/2017 3:23 PM, Istvan Prosinger wrote: > Hi All, and Happy New Year with a little delay :) > > Comming to spam, header checks are one tool that I use frequently to > prevent it. > > So, amongst all, I have this: > > if !/^Subject: (.*)[Aa]liexpress/ > /^Subject

Re: Antispamming with header checks and regexp

On 6 February 2017 at 21:23, Istvan Prosinger wrote: > Hi All, and Happy New Year with a little delay :) > > Comming to spam, header checks are one tool that I use frequently to > prevent it. > > So, amongst all, I have this: > > if !/^Subject: (.*)[Aa]liexpress/ >

Antispamming with header checks and regexp

Hi All, and Happy New Year with a little delay :) Comming to spam, header checks are one tool that I use frequently to prevent it. So, amongst all, I have this: if !/^Subject: (.*)[Aa]liexpress/ /^Subject:(.*)% [Oo][Ff][Ff]/ REJECT Go away spammer endif And this worked fine until _today_

Re: header checks and regex issues

Alex wrote: > Okay, thanks. I'm doing this already on the pcre header_checks file, > and have added it on the mime_types file, but noticed a problem with > the pattern matching: > > /^Content-(Disposition|Type):\s+.+?(file)?name="?.+?\.com(\.\S{2,4})?(\?=)?"?(;|$)/ > REJECT ".com" file attachm

Re: header checks and regex issues

On 9/28/2016 7:04 PM, Alex wrote: > Hi, > > On Wed, Sep 28, 2016 at 5:46 PM, Noel Jones wrote: >> On 9/28/2016 4:15 PM, Alex wrote: >> >>> How can I modify the lines in my header_checks.pcre file to provide >>> more info on the specific pattern that's causing the problem instead >>> of just "mess

Re: header checks and regex issues

Hi, On Wed, Sep 28, 2016 at 5:46 PM, Noel Jones wrote: > On 9/28/2016 4:15 PM, Alex wrote: > >> How can I modify the lines in my header_checks.pcre file to provide >> more info on the specific pattern that's causing the problem instead >> of just "message content rejected" the next time the email

Re: header checks and regex issues

On 9/28/2016 4:15 PM, Alex wrote: > How can I modify the lines in my header_checks.pcre file to provide > more info on the specific pattern that's causing the problem instead > of just "message content rejected" the next time the email is > received? Note the log entry may not be the complete unm

header checks and regex issues

Hi, I'm having a problem with a few different emails with attachments being rejected due to some pattern in my header checks that I can't figure out: Sep 28 09:34:11 mail03 postfix/cleanup[24507]: 31926209EDF9: reject: header Content-Type: application/vnd.ms-excel;??name="Copy of

Re: header checks/body checks

On 11/4/2014 6:38 PM, J. wrote: > > No, the "[BODY]" line is sent to the connecting server with the > error that I write. I didn't write it. Here's a sample rejected > message when I sent a test message from my web-mail to my postfix > server: > > Remote host said: > 550 Spam not accepted. > [BOD

Re: header checks/body checks

hat sort of admins making my life harder by parse logs in context of a sane bounce management stop that behavior! *From:* Wietse Venema *To:* J. *Cc:* Wietse Venema ; "postfix-us...@cloud9.net" *Sent

Re: header checks/body checks

hat sort of admins making my life harder by parse logs in context of a sane bounce management stop that behavior! *From:* Wietse Venema *To:* J. *Cc:* Wietse Venema ; "postfix-us...@cloud9.net" *Sent

Re: header checks/body checks

rol. I would like to not show the sender which part of the message is triggering the rejection. From: Wietse Venema To: J. Cc: Wietse Venema ; "postfix-us...@cloud9.net" Sent: Tuesday, November 4, 2014 5:35 PM Subject: Re: header checks/body check

Re: header checks/body checks

J.: > Returned in a non-delivery notification. Like this: > > Remote host said: > > 550 Spam not accepted. > [BODY] That is not a Postfix non-delivery notification. Please do not blame the messenger of the bad news. Wietse

Re: header checks/body checks

Returned in a non-delivery notification. Like this: Remote host said: 550 Spam not accepted. [BODY] From: Wietse Venema To: J. Cc: "postfix-us...@cloud9.net" Sent: Tuesday, November 4, 2014 12:19 PM Subject: Re: header checks/body checks

Re: header checks/body checks

__ From: "li...@rhsoft.net" To: postfix-users@postfix.org Sent: Tuesday, November 4, 2014 12:16 PM Subject: Re: header checks/body checks Am 04.11.2014 um 21:12 schrieb J.: > I'm using header_checks and body_checks to block certain classes of spam > that amav

Re: header checks/body checks

J.: > I'm using header_checks and body_checks to block certain classes > of spam that amavis/sa don't seem to be able to catch. The trouble > is that when it rejects the message, the message failure text is > sent followed by: Sent as in: [ ] Returned to the SMTP client? [ ] Returned in a non-del

Re: header checks/body checks

Am 04.11.2014 um 21:12 schrieb J.: I'm using header_checks and body_checks to block certain classes of spam that amavis/sa don't seem to be able to catch. The trouble is that when it rejects the message, the message failure text is sent followed by: [BODY] (and presumably [HEADER] if it matche

header checks/body checks

I'm using header_checks and body_checks to block certain classes of spam that amavis/sa don't seem to be able to catch. The trouble is that when it rejects the message, the message failure text is sent followed by: [BODY] (and presumably [HEADER] if it matches a header_check rule). Is there a

RE: header checks for a relay client

Thanks much. > That looks about right. > > Good Practice Note: anchor/narrow your expressions to make them as > specific as possible to prevent unexpected behavior. This is > especially important if you intend to discard mail: > /@client[1-6]\.domain2\.com$/ > /@yahoogroups\.com$/ > > > -- No

Re: header checks for a relay client

On 9/24/2014 12:49 PM, Michael Fox wrote: >> -Original Message- >> From: owner-postfix-us...@postfix.org [mailto:owner-postfix- >> us...@postfix.org] On Behalf Of Michael Fox >> Sent: Wednesday, September 24, 2014 10:24 AM >> To: 'postfix users' &

RE: header checks for a relay client

> -Original Message- > From: owner-postfix-us...@postfix.org [mailto:owner-postfix- > us...@postfix.org] On Behalf Of Michael Fox > Sent: Wednesday, September 24, 2014 10:24 AM > To: 'postfix users' > Subject: RE: header checks for a relay client > &g

RE: header checks for a relay client

> > What you can do is create a restriction class to check the sender > > and the recipient, and reject the message if both match. The > > general procedure is outlined here, with some examples similar to > > what you're asking: > > http://www.postfix.org/RESTRICTION_CLASS_README.html I don't see

Re: header checks not working

On September 24, 2014 6:49:22 AM Webmaster wrote: The requsted information simply does not exit. Then the problem does not exit

Re: header checks not working

The requsted information simply does not exit. 3. Any text. 4. No commands run, just emails are sent / received. 5. Commands typed: the word spam in the subject field. No commands from any scripts are run. 6. No datafiles used. Original message Subject: Re: header checks

RE: header checks for a relay client

> What you can do is create a restriction class to check the sender > and the recipient, and reject the message if both match. The > general procedure is outlined here, with some examples similar to > what you're asking: > http://www.postfix.org/RESTRICTION_CLASS_README.html > > Alternately, you

Re: header checks not working

> Wietse: > If you still want help, post actual technical details: > > 1) non-verbose logging, > 2) the "postconf -n" for the configuration that produced that logging, > 3) the content of the email message that produced that logging, > 3) any commands that you type in order to produce that logging

Re: header checks for a relay client

On 9/23/2014 2:31 PM, Michael Fox wrote: > Sanity check please: > > > > I have a relay machine: relay.domain1.com > > And a client: client.domain2.com > > > > I’d like to filter (silently discard) messages at the relay machine > from going to any account on the client machine if the From

Re: header checks not working

/etc/postfix/virtual_alias_maps virtual_gid_maps = static:1000 virtual_mailbox_base = /home/mail virtual_mailbox_domains = example.com virtual_mailbox_maps = hash:/etc/postfix/virtual_boxes virtual_minimum_uid = 100 virtual_transport = dovecot-spamass virtual_uid_maps = static:1000 -- View this message in c

header checks for a relay client

Sanity check please: I have a relay machine: relay.domain1.com And a client: client.domain2.com I'd like to filter (silently discard) messages at the relay machine from going to any account on the client machine if the From: address is: groupsupda...@yahoogroups.com

Re: header checks not working

on what else might be going wrong would be also > extremely highly appreciated. Many thanks! > > > > > -- > View this message in context: > http://postfix.1071664.n5.nabble.com/header-checks-not-working-tp36845p71004.html > Sent from the Postfix Users mailing list archive at Nabble.com. >

Re: header checks not working

e SA "exits" somehow inside Postfix? Any other suppositions / hypothesis on what else might be going wrong would be also extremely highly appreciated. Many thanks! -- View this message in context: http://postfix.1071664.n5.nabble.com/header-checks-not-working-tp36845p71004.html S

Re: header checks not working

Am 12.09.2014 um 11:29 schrieb Den: >> run the spamfilter after queue >> http://www.postfix.org/MILTER_README.html > > Thanks. Will double-check on that. Chances also are that I missed something > too or I might as well have to try to switch to these milters as running SA > daemonized doesn't wor

Re: header checks not working

On Fri, Sep 12, 2014 at 10:12:38PM -0700, Den wrote: > I was just wondering what exactly does the line below do? Could anybody > comment / advise, please? It does not actually check and *confirm* that the > code, syntax, etc. of any regexp present in /filter/ (example) is 100% > correct does it? >

Re: header checks not working

*\*{5}SPAM\*{5}/" regexp:/etc/postfix//filter/ Many thanks! -- View this message in context: http://postfix.1071664.n5.nabble.com/header-checks-not-working-tp36845p70666.html Sent from the Postfix Users mailing list archive at Nabble.com.

Re: header checks not working

efaults. On the other hand there is nothing out there that could possibly stop me from giving your options a shoot and try them out. Will literally take just a minute. -- View this message in context: http://postfix.1071664.n5.nabble.com/header-checks-not-working-tp36845p70657.html Sent fr

Re: header checks not working

Am 12.09.2014 um 14:53 schrieb Den: >> "li...@rhsoft.net" >> no but the regexp is entirely wrong >> >> the subject starts with [SPAM] so no need for .* >> {5} - what is that supposed to do? >> avoid a * in the action for safety >> >> /^Subject: \[SPAM.*/ DISCARD SPAM > > Strongly disagree. Regex

Re: header checks not working

cter that goes in front, like your mentioned [, my *, or + and so on. Thus I do not have to explicitly mention each character separately including [ * + and so on. -- View this message in context: http://postfix.1071664.n5.nabble.com/header-checks-not-working-tp36845p70643.html Sent fr

Re: header checks not working

Den: > Does it work successively as PHP does? Postfix works as documented in regexp_table(5) and pcre_table(5), i.e. each query stops at the first matching rule. Postfix also works as documented in header_checks(5), i.e. DISCARD causes Postfix to ignore the remainder of the message. > Then my be

Re: header checks not working

Am 12.09.2014 um 14:23 schrieb Den: > /^Subject:.*\*{5}SPAM\*{5}/DISCARD *SPAM* > /^Subject:/WARN > > that is without having anything before discard*spam*. Is that correct? > > I also begin to think that there is a regexp issue somewhere. Is it actually > poss

Re: header checks not working

iew this message in context: http://postfix.1071664.n5.nabble.com/header-checks-not-working-tp36845p70638.html Sent from the Postfix Users mailing list archive at Nabble.com.

Re: header checks not working

Den: > /^Subject:.*\*{5}SPAM\*{5}/DISCARD *SPAM* PLease look for warnings like the following in your maillog file: postfix/cleanup[2632]: warning: regexp map /etc/postfix/header_checks, line 1: unknown regexp option "D": skipping this rule Wietse

Re: header checks not working

ope with it. It's not a concern of mine in any way. I simply expressed my personal view because it did not sound logical to me. -- View this message in context: http://postfix.1071664.n5.nabble.com/header-checks-not-working-tp36845p70634.html Sent from the Postfix Users mailing list archive at Nabble.com.

Re: header checks not working

Am 12.09.2014 um 11:29 schrieb Den: >> run the spamfilter after queue >> http://www.postfix.org/MILTER_README.html > > Thanks. Will double-check on that. Chances also are that I missed something > too or I might as well have to try to switch to these milters as running SA > daemonized doesn't wor

Re: header checks not working

ive person, it would NOT hold enough testimony that a live person was involved at all. It would definitely not be the case in our country and by no means would ever be regarded as the only truth averment. -- View this message in context: http://postfix.1071664.n5.nabble.com/header-checks-not-working-tp36845p70628.html Sent from the Postfix Users mailing list archive at Nabble.com.

Re: header checks not working

hat goes after /^Subject:/ WARN gets to be "warned" and ignored. Many thanks! -- View this message in context: http://postfix.1071664.n5.nabble.com/header-checks-not-working-tp36845p70620.html Sent from the Postfix Users mailing list archive at Nabble.com.

Re: header checks not working

that - depending on... > > I am not sure I follow. Don't do what? run the spamfilter after queue http://www.postfix.org/MILTER_README.html > I am saying here that my header checks do not work i miss a complete log of such a message in that thread > and all the spam is coming i

Re: header checks not working

>in context of "the spam detector" you need to name it >"GTUBE not supported by postfix filters" makes no sense without naming the filter Right. It's spamassassin. Thanks. >don't do that - depending on... I am not sure I follow. Don't do what? I

Re: header checks not working

point and > where to look to have it fixed? Is this GTUBE not supported by postfix > filters and may that be the reason for my other messages not being rejected > via header checks in postfix? Would highly appreciate any further guidance > from any postfix experts out there. Many th

  1   2   3   >