[exim] spamassin running, but headers not always added

2011-04-07 Thread Marc Haber
Hi, I am using spamassassin and exiscan integration with the following ACL: | accept |condition = ${if eq{acl_m_spam_no_filter}{1}} | | deny |demime = com:vbs:bat:pif:scr:exe |message = no Windows executeables accepted here |log_message = reject, $found_extension file | |

Re: [exim] spamassin running, but headers not always added

2011-04-07 Thread Graeme Fowler
On Thu, 2011-04-07 at 08:42 +0200, Marc Haber wrote: This works, usually. snip What might be going wrong here, and how can I debug and/or fix it? You might find that Exim has timed out the spamassassin call - this should be logged in your panic log. With the :true on the end of each call (and

Re: [exim] Rejecting RunTogetherSubjects

2011-04-07 Thread Karl Schmidt
On 04/05/2011 10:39 AM, Jeremy wrote: Of course you can! Something along the lines of if match $h_subject /w{25}. You'll need to look up the exact syntax; sorry. I tried in acl_check_data: denycondition = ${if match{$h_subject:}{\w{25}} message = irritating misses other non

[exim] pgsql client encoding issue

2011-04-07 Thread Mark Adams
Hi All, exim 4.72-6, Debian squeeze. I'm having a client encoding issue whilst trying to log headers in to postgres using pgsql if the subject contains the pound sign (£) I fixed other encoding issues I had by adding :rfc2047: in as follows ${quote_pgsql:rfc2047:$h_subject:} However this

Re: [exim] Rejecting RunTogetherSubjects

2011-04-07 Thread John Jetmore
On Thu, Apr 7, 2011 at 5:32 AM, Karl Schmidt k...@xtronics.com wrote: deny    condition = ${if match{$h_subject:}{\S{25}}        message = irritating This should work - but isn't? I tested it with PCRE via: Note that it should be \w not /w and \S is anything non white-space. Am I missing

Re: [exim] pgsql client encoding issue

2011-04-07 Thread W B Hacker
Mark Adams wrote: Hi All, exim 4.72-6, Debian squeeze. I'm having a client encoding issue whilst trying to log headers in to postgres using pgsql if the subject contains the pound sign (£) I fixed other encoding issues I had by adding :rfc2047: in as follows

Re: [exim] spamassin running, but headers not always added

2011-04-07 Thread Marc Haber
On Thu, 07 Apr 2011 09:59:10 +0100, Graeme Fowler gra...@graemef.net wrote: On Thu, 2011-04-07 at 08:42 +0200, Marc Haber wrote: This works, usually. snip What might be going wrong here, and how can I debug and/or fix it? You might find that Exim has timed out the spamassassin call - this

Re: [exim] pgsql client encoding issue

2011-04-07 Thread Phil Pennock
On 2011-04-07 at 12:48 +0100, Mark Adams wrote: I fixed other encoding issues I had by adding :rfc2047: in as follows ${quote_pgsql:rfc2047:$h_subject:} Assuming you mean ${rfc2047:...} then that encodes data. I'd expect you to normally want to decode data. As written though, that does not