Re: [Qmail-scanner-general]Badtrans go thru!

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Hi,

Today I had two events of badtrans passing the scanner without a problem.
But strangly enough it seems that these emails had bad newlines,
In vi it just showed me ^M on the place of a newline, wich normally happe=
ns
if it is a dos file.

Just pasting the first part of the email here :
-----
MIME-Version: 1.0^MContent-Type: multipart/related;^M
type=3D"multipart/alternative";^M         boundary=3D"=3D=3D=3D=3D_ABC123=
4567890DEF_=3D=3D=3D
=3D"^MX-Priority: 3^MX-MSMail-Priority: Normal^MX-Unsent: 1
--=3D=3D=3D=3D_ABC1234567890DEF_=3D=3D=3D=3D^MContent-Type: multipart/alt=
ernative;^M
boundary=3D"=3D=3D=3D=3D_ABC0987654321DEF_=3D=3D=3D=3D"
--=3D=3D=3D=3D_ABC0987654321DEF_=3D=3D=3D=3D^MContent-Type: text/html;^M
charset=3D"iso-8859-1"^MContent-Transfer-Encoding: quoted-printable
^M<HTML><HEAD></HEAD><BODY bgColor=3D3D#ffffff>^M<iframe src=3D3Dcid:EA4D=
MGBP9p
height=3D3D0 width=3D3D0>^M</iframe></BODY></HTML>^M--=3D=3D=3D=3D_A
BC0987654321DEF_=3D=3D=3D=3D--
--=3D=3D=3D=3D_ABC1234567890DEF_=3D=3D=3D=3D^MContent-Type: audio/x-wav;^=
M
name=3D"Sorry_about_yesterday.MP3.pif"^MContent-Transfer-Encoding: ba
se64^MContent-ID: <EA4DMGBP9p>

----

Maybe the same happened on your side?

Seems that some MUA's cant handle this anyways, at least I had one custom=
er
bugging me all morning
about mail server problems, wich was all caused by this email.....
My local Outlook + norton av 2002 did catch this one btw.

Best wishes for 2002,

Jean-Paul van de Plasse

----- Original Message -----
From: "CertaintyTech - Ed Henderson" <ed....@ce...>
To: "Andrei Gologan" <ago...@gm...>;
<qma...@li...>
Sent: Wednesday, December 26, 2001 11:05 PM
Subject: RE: [Qmail-scanner-general]Badtrans go thru!

> I am using Q-S v1.03, TNEF v1.1.1, and maildrop/reformime v1.3.6.  I
> believe these are the latest.  Like I may have said before I have
> blocked the Badtrans many times before and since.  For some reason this
> one message made it thru.  For whatever reason Q-S did not see that it
> had an attachment otherwise it would have been blocked by perl-scanner
> (set to block all .SCR attachments) and by Sophos (was updated with the
> latest vdefs).  The other puzzling part is that If I send the original
> missed message back thru it will get blocked everytime.  Since I didn't
> have logging turned on at the time I may never know why or how it got
> thru.
>
> Thanks for your input,
> ---
> Ed.
>
> > -----Original Message-----
> > From: Andrei Gologan [mailto:ago...@gm...]
> > Sent: Wednesday, December 26, 2001 4:28 PM
> > To: CertaintyTech - Ed Henderson;
> > qma...@li...
> > Subject: *****SPAM***** Re: [Qmail-scanner-general]Badtrans go thru!
> >
> >
> > Hi
> >
> > well I had the same problem with Badtrans and since we use
> > exchange, notes,
> > qmail  and a lot of e-mail clients it didn=B4t showed up all
> > the time. Most of
> > them where catched but the ones sent by outlook express were
> > not. The clue was
> > to use the newest Q-S AND the TNEF unpacker.
> >
> > Reformime/maildrop was fine but without tnef unpacher mails
> > went thru. The
> > desktop client showed up "VIRUS"  the Q-S did not "get it" on
> > one mail Server
> > but did it on all the others. But now everything is fine :-))
> >
> > Grettings
> > Andrei
> >
>
>
> _______________________________________________
> Qmail-scanner-general mailing list
> Qma...@li...
> https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
>

Re: [Qmail-scanner-general]Badtrans go thru!

AV/content filter for Qmail

Re: [Qmail-scanner-general]Badtrans go thru!