Re: Error: queue file write error
On Oct 11, 2015, at 8:55 AM, Dan Lists wrote:
> %https?://[0-9]*\.[0-9]*\.[0-9]*\.[0-9]*/public/% REJECT
[0-9]* means “Zero or more of 1-9”
And you have 4 of those.
[0-9]{1,3}\.){3}[0-9]{1,3}
Would be much safer.
Or even
[1-2]?[0-9]?[0-9]\.[1-2]?[0-9]?[0-9]\.[1-2]?[0-9]?[0-9]\.[1-2]?[0-9]?[0-9]
--
I gotta straighten my face This mellow-thighed chick just put my spine
out of place
Re: Error: queue file write error
On Sat, Oct 10, 2015 at 2:23 PM, Wietse Venema wrote: > Dan Lists: > > > > Out: 451 4.3.0 Error: queue file write error > > Oct 10 09:13:39 nook postfix/cleanup[18080]: fatal: pcre map > > /usr/local/etc/postfix/body_checks, line 17: matched text exceeds buffer > > limit > > Yes, in case of trouble, look for panic or fatal messages first. > Especially when the SMTP transcript tells you to look in the log > for details. > > The PCRE client does not know the queue ID, and the SMTP daemon > does not know that the PCRE client aborted (nor does the SMTP daemon > know why). This will not change. Logging the full execution context > for every possible error comes with a significant cost. > cleanup knows the queue id, it logged: Oct 10 09:13:37 myserver postfix/cleanup[18080]: 89C476DF8C3: warning: header Subject: CONFIDENTAIL: CLAIM YOUR PRIZE from avas10tiga.indosat.net.id[219.83.54.103]; from=<2...@heathfield.co.nz> to=< u...@myserver.net> proto=ESMTP helo= Couldn't the cleanup fatal log entry be changed to add the queue id? So like this: Oct 10 09:13:39 myserver postfix/cleanup[18080]: 89C476DF8C3: fatal: pcre map /usr/local/etc/postfix/body_checks, line 17: matched text exceeds buffer limit > Why didn't smtpd log the 451 error? This is the first time I have ever > > seen smtpd not log the final outcome. > > Postfix will not log all [45]xx replies. That would make it way > too easy to flood the file system. However, every panic or fatal > error should be investigated whether it happened during an SMTP > session or otherwise. > > Is there a way to increase the buffer limit? > > Maybe this helps: > > https://groups.google.com/forum/#!topic/mailing.postfix.users/14GV4g4kNyk > My expression does not have any .* in it. Here it is: %https?://[0-9]*\.[0-9]*\.[0-9]*\.[0-9]*/public/% REJECT I would like to reject this message so they stop trying to send it. I could modify the expression but then it wold not match and the message would not be rejected. What is the buffer size for pcre? The machine has a lot of resources, can I bump the limit? Wietse >
Re: Error: queue file write error
Dan Lists: > > > Out: 451 4.3.0 Error: queue file write error > Oct 10 09:13:39 nook postfix/cleanup[18080]: fatal: pcre map > /usr/local/etc/postfix/body_checks, line 17: matched text exceeds buffer > limit Yes, in case of trouble, look for panic or fatal messages first. Especially when the SMTP transcript tells you to look in the log for details. The PCRE client does not know the queue ID, and the SMTP daemon does not know that the PCRE client aborted (nor does the SMTP daemon know why). This will not change. Logging the full execution context for every possible error comes with a significant cost. > Why didn't smtpd log the 451 error? This is the first time I have ever > seen smtpd not log the final outcome. Postfix will not log all [45]xx replies. That would make it way too easy to flood the file system. However, every panic or fatal error should be investigated whether it happened during an SMTP session or otherwise. > Is there a way to increase the buffer limit? Maybe this helps: https://groups.google.com/forum/#!topic/mailing.postfix.users/14GV4g4kNyk Wietse
Re: Error: queue file write error
On Sat, Oct 10, 2015 at 11:30 AM, Viktor Dukhovni < postfix-us...@dukhovni.org> wrote: > On Sat, Oct 10, 2015 at 10:53:12AM -0500, Dan Lists wrote: > > > Out: 451 4.3.0 Error: queue file write error > > > > And here are the log entries: > > > > Oct 10 09:13:26 myserver postfix/smtpd[18826]: connect from > > avas10tiga.indosat.net.id[219.83.54.103] > > Oct 10 09:13:34 myserver policyd: rcpt=18817141, greylist=update, > > host=219.83.54.103 (avas10tiga.indosat.net.id), from= > 2...@heathfield.co.nz, > > to=u...@myserver.net, size=2873224 > > Oct 10 09:13:34 myserver postfix/smtpd[18826]: 89C476DF8C3: client= > > avas10tiga.indosat.net.id[219.83.54.103] > > Oct 10 09:13:37 myserver postfix/cleanup[18080]: 89C476DF8C3: > > message-id=<32609497.108184811317.JavaMail.defaultUser@defaultHost> > > Oct 10 09:13:37 myserver postfix/cleanup[18080]: 89C476DF8C3: warning: > > header Subject: CONFIDENTAIL: CLAIM YOUR PRIZE from > > avas10tiga.indosat.net.id[219.83.54.103]; from=<2...@heathfield.co.nz> > to=< > > u...@myserver.net> proto=ESMTP helo= > > Oct 10 09:23:10 myserver postfix/smtpd[18826]: disconnect from > > avas10tiga.indosat.net.id[219.83.54.103] > > Sorry that can't be all that's in the logs, look at your syslog > configuration and check any additional log files. > > -- > Viktor. > I did eventually manage to find something in the logs: Oct 10 09:13:39 nook postfix/cleanup[18080]: fatal: pcre map /usr/local/etc/postfix/body_checks, line 17: matched text exceeds buffer limit We handle around 1 million messages per day, so it can be hard to find an entry that is not associated with the client IP, queue id, message id, sender, or recipient. Why didn't smtpd log the 451 error? This is the first time I have ever seen smtpd not log the final outcome. Is there a way to increase the buffer limit? Is there a way to get postfix to reject these in a way that generates a log entry associated with the queue id? Thanks, Dan
Re: Error: queue file write error
On Sat, Oct 10, 2015 at 10:53:12AM -0500, Dan Lists wrote: > Out: 451 4.3.0 Error: queue file write error > > And here are the log entries: > > Oct 10 09:13:26 myserver postfix/smtpd[18826]: connect from > avas10tiga.indosat.net.id[219.83.54.103] > Oct 10 09:13:34 myserver policyd: rcpt=18817141, greylist=update, > host=219.83.54.103 (avas10tiga.indosat.net.id), from=2...@heathfield.co.nz, > to=u...@myserver.net, size=2873224 > Oct 10 09:13:34 myserver postfix/smtpd[18826]: 89C476DF8C3: client= > avas10tiga.indosat.net.id[219.83.54.103] > Oct 10 09:13:37 myserver postfix/cleanup[18080]: 89C476DF8C3: > message-id=<32609497.108184811317.JavaMail.defaultUser@defaultHost> > Oct 10 09:13:37 myserver postfix/cleanup[18080]: 89C476DF8C3: warning: > header Subject: CONFIDENTAIL: CLAIM YOUR PRIZE from > avas10tiga.indosat.net.id[219.83.54.103]; from=<2...@heathfield.co.nz> to=< > u...@myserver.net> proto=ESMTP helo= > Oct 10 09:23:10 myserver postfix/smtpd[18826]: disconnect from > avas10tiga.indosat.net.id[219.83.54.103] Sorry that can't be all that's in the logs, look at your syslog configuration and check any additional log files. -- Viktor.
Re: Error: queue file write error
Am 10. Oktober 2015 17:53:12 MESZ, schrieb Dan Lists : >I am receiving the transcript file with the error "Error: queue file >write >error." It appears that postfix is timing out the connection after 10 >minutes. The thing that disturbs me is that nothing is logged. Is >there >a way to get postfix to put something in the logs? How mich space is reported to be free in the filesystem? - Christian
Re: Error: queue file write error
On Sat Oct 10 2015 09:53:12 Dan Listssaid: > > I am receiving the transcript file with the error "Error: queue file write > error." It appears that postfix is timing out the connection after 10 > minutes. The thing that disturbs me is that nothing is logged. Is there a > way to get postfix to put something in the logs? Postfix DOES put something in the logs. Oct 10 09:23:10 myserver postfix/smtpd[18826]: disconnect from avas10tiga.indosat.net.id[219.83.54.103] -- Lisa Bonet ate no Basil
