Re: Correction

2014-11-04 Thread J.
I don't think my assumption is completely unwarranted. I created a header_checks rule and then sent a message from outside our system and this shows up in the log: Nov 4 12:09:24 kest postfix/cleanup[13287]: 375FR2F2491F: reject: header Subject: VvVvV test message...[etc] Then when I do a tes

Re: Corrupted messages...

2014-11-04 Thread SH Development
Problem solved. Turns out, we were using a DNS provider that was having issues. Changed to another DNS provider primary and secondary, and slowness issues stopped. As for the corrupted messages showing up, I will let you know. Jeff > On Nov 4, 2014, at 12:45 PM, Wietse Venema wrote: > > S

Re: Correction

2014-11-04 Thread Wietse Venema
J.: > Apologies. I'm not sure why "[BODY]" is showing up after the > rejection line from header_checks and body_checks, but I was > mistaken about it disclosing exactly why the message was rejected. > Regardless of whether it's a body_check or header_check that is > matched, the failure message say

Correction

2014-11-04 Thread J.
Apologies. I'm not sure why "[BODY]" is showing up after the rejection line from header_checks and body_checks, but I was mistaken about it disclosing exactly why the message was rejected. Regardless of whether it's a body_check or header_check that is matched, the failure message says "[BODY]"

Re: header checks/body checks

2014-11-04 Thread J.
Maybe I don't know the name of notification where this message comes from, but it is certainly postfix. I admin the "remote host" that "said" that. I entered the text "Spam not accepted" in my body_checks file, and the next line I don't know how to control. I would like to not show the sender wh

Re: header checks/body checks

2014-11-04 Thread Wietse Venema
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

2014-11-04 Thread J.
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 J.: > I'm usi

Re: header checks/body checks

2014-11-04 Thread J.
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. [BODY] From: "l

Re: header checks/body checks

2014-11-04 Thread Wietse Venema
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

2014-11-04 Thread li...@rhsoft.net
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

2014-11-04 Thread 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 matches a header_check rule). Is there a

Re: Corrupted messages...

2014-11-04 Thread Robert Schetterer
Am 04.11.2014 um 19:18 schrieb SH Development: > File system has been checked with no errors presenting. did you checked memory too, last time i saw corrupted messages at my setup, broken ram memory was the reason, worked fine again after changing it Best Regards MfG Robert Schetterer -- [*] s

Re: Corrupted messages...

2014-11-04 Thread SH Development
> On Nov 4, 2014, at 11:50 AM, Wietse Venema wrote: > > SH Development: >> I am getting these messages: >> >> Nov 4 11:16:46 mail2 postfix/postfix-script: warning: damaged message: >> corrupt/AE7E42857D76 >> Nov 4 11:16:46 mail2 postfix/postfix-script: warning: damaged message: >> corrupt/B

Re: log length in header_checks

2014-11-04 Thread Markus Benning
On Tue, Nov 04, 2014 at 02:59:21PM +0200, Konstantin wrote: > Now postfix log only first 3 records. Current limit is about 200 > characters. You may want to patch the following line: https://github.com/vdukhovni/postfix/blob/master/postfix/src/global/header_body_checks.c#L457 Markus

Re: Corrupted messages...

2014-11-04 Thread Wietse Venema
SH Development: > I am getting these messages: > > Nov 4 11:16:46 mail2 postfix/postfix-script: warning: damaged message: > corrupt/AE7E42857D76 > Nov 4 11:16:46 mail2 postfix/postfix-script: warning: damaged message: > corrupt/B4D472857D77 > Nov 4 11:16:46 mail2 postfix/postfix-script: warni

Re: Corrupted messages...

2014-11-04 Thread D'Arcy J.M. Cain
On Tue, 4 Nov 2014 11:19:33 -0600 SH Development wrote: > Nov 4 11:16:46 mail2 postfix/postfix-script: warning: damaged > message: corrupt/AE7E42857D76 Nov 4 11:16:46 mail2 > postfix/postfix-script: warning: damaged message: > corrupt/B4D472857D77 Nov 4 11:16:46 mail2 postfix/postfix-script: >

Corrupted messages...

2014-11-04 Thread SH Development
I am getting these messages: Nov 4 11:16:46 mail2 postfix/postfix-script: warning: damaged message: corrupt/AE7E42857D76 Nov 4 11:16:46 mail2 postfix/postfix-script: warning: damaged message: corrupt/B4D472857D77 Nov 4 11:16:46 mail2 postfix/postfix-script: warning: damaged message: corrupt/

log length in header_checks

2014-11-04 Thread Konstantin
Hi I need to log all records of header References. My header_checks content: /^References:/ INFO I found that if message has more than 4 records in References then log record is truncated. Now postfix log only first 3 records. Current limit is about 200 characters. Nov 4 12:43:34 server postf