Hi Julien
That's too hard to read all chopped up like that - can you send me
examples of the messages that work and didn't work? tar/zip them up.
One thing: I see
--=_NextPart_b0dbc08c64f8063304d986605b1f6e7d
Content-Type: multipart/alternative;
boundary="=_NextPart_b0dbc08c64f8063304d98
Hello,
Qmail scanner seems to detect valid e-mail as broken MIME.
My log shows :
Tue, 27 Sep 2011 18:49:01 CEST:31026: w_c: broken attachment MIME details
(still_attachment=--=_NextPart_b0dbc08c64f8063304d986605b1f6e7d_alt, but
BOUNDARY_REGEX="\-\-\-\-\=_NextPart_b0dbc08c64f8063304d986605b1f6e
On 10/09/11 01:47, Almar van Pel wrote:
> Hi all,
>
> I'm having some issues with one specific mailsource, that seems to be
> delivering some invalid content. I unfortunately cannot understand de
> reason why this is wrong. Could somebody explain this to me?
>
That blocks MIME emails that have inco
Hi all,
I'm having some issues with one specific mailsource, that seems to be
delivering some invalid content. I unfortunately cannot understand de reason
why this is wrong. Could somebody explain this to me?
Below is the logging:
Fri, 09 Sep 2011 14:27:44 CEST:26123: w_c: primary Content-Ty
Hello,
I'm using qmail-scanner 2.01 with the following configure options:
log-details=0
log-crypto=0
fix-mime=2
ignore-eol-check=0
debug=0
notify=none
redundant-scanning=yes
virus-admin=System Anti-Virus Administrator
local-domains='peakpeak.com'
silent-viruses='klez','bugbear','hybris','yaha','b
Hi folks,
i would like to know why the following mail is blocked by
qmail-scanner-1.20rc3 with "Disallowed content found in
MIME attachment". The content is rather harmless.
Received: from pop.gmx.de (HELO mail.gmx.net) (213.165.64.20)
by with SMTP; 16 Sep 2003 11:05:59 -
Rece
