I am personally getting fed up with those 'you have a virus' mails. Not only is this absolutely not true. I am also getting complaints from users who actually think they do have a virus because they received mails claiming so. I am now starting to block those warnings.=20
> -----Oorspronkelijk bericht----- > Van: Jason Badry [mailto:[EMAIL PROTECTED] > Verzonden: donderdag 11 maart 2004 1:32 > Aan: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Onderwerp: [xmail] Re: AV Filtering Paths >=20 > That is a good point and I have changed the '6' to a '4'. It=20 > would be nice though to notify whoever is sending these=20 > viruses so they can get their system cleaned up, but I do see=20 > the logistical problems with that. I am somewhat concerned=20 > about sending email to the 'bit bucket' with no sort of=20 > review, but without being able to identify the sender=20 > accurately, I guess this is best. >=20 > ... Jason Badry >=20 > At 06:12 PM 3/10/2004 -0500, Tracy wrote: > >May I *strongly* recommend that you do not send bounce notices for=20 > >virus emails? A large percentage of the virus emails these days are=20 > >from forged senders, so by producing and sending a bounce=20 > notice, you=20 > >are - in effect - notifying an innocent party that they=20 > "have a virus", when they don't. > >If you feel you *must* notify someone, you should write some custom=20 > >code to take the connection IP address (which delivered the mail to=20 > >you) and work out the appropriate abuse mailbox for that=20 > domain. That=20 > >would at least get it to the ISP of the machine which=20 > delivered the email to you. > > > >A lot of the spam activists out there are also blocking based on=20 > >bounces to forged senders, so if you proceed you may find your mail=20 > >delivery blocked at various locations. > > > >Just a thought... > > > >At 17:59 3/10/2004, Jason Badry wrote: > > > > >I was just going to send a followup email, as this was indeed my=20 > > >problem (I changed the "RetCode" in filter.tab to a "6"). =20 > I've added=20 > > >quite a bit more logging and a configurable logging path to XAV so=20 > > >now it logs into my \Mailroot\Logs directory with the same=20 > filename as the other logs. > > > > > >I currently have the return code set to 6, but then this was=20 > > >notifying the postmaster of the errors, so I have for now turned=20 > > >postmaster error notification in the system.tab. Is there=20 > a return=20 > > >code that would notify the sender, but not notify the postmaster? =20 > > >I'd like to leave postmaster error notification on, but I=20 > don't want to know about every virus file. > > > > > >Thanks, > > > > > >... Jason Badry > > > > > >At 10:56 PM 3/10/2004 +0100, you wrote: > > > >Are you using the correct returncode in the filter.tab? > > > > > > > >-----Oorspronkelijk bericht----- > > > >Van: Shiloh Jennings [mailto:[EMAIL PROTECTED] > > > >Verzonden: woensdag 10 maart 2004 22:33 > > > >Aan: [EMAIL PROTECTED] > > > >Onderwerp: [xmail] Re: AV Filtering Paths > > > > > > > > > > > >I am having the same problem. I am using XAV, ripmime,=20 > and f-prot=20 > > > >for dos. According to the XAV.log file it appears to be catching=20 > > > >the virus attachments, but the virus messages are still passing=20 > > > >through to the mailboxes. I am not really sure how to=20 > debug this=20 > > > >problem. Anybody have any ideas? > > > > > > > > > > > >----- Original Message -----=3D20 > > > >From: "Jason Badry" <[EMAIL PROTECTED]> > > > >To: <[EMAIL PROTECTED]> > > > >Sent: Wednesday, March 10, 2004 2:19 PM > > > >Subject: [xmail] Re: AV Filtering Paths > > > > > > > > > > > > > Thanks for ripMIME. It got me one more step forward. I now=20 > > > > > have > > XAV=3D20 > > > > > detecting the virus (reporting so in the log file),=20 > but XMail is=20 > > > > > still > > > > > > > > > letting the file continue on its way. I'm wondering if my XAV > > script=3D20 > > > > > is the newest available. The one I have was last updated on=20 > > > > > 16Oct2003 > > > > > > > > > by D. Olivier. I've added several debug statements to capture > > system=3D20 > > > > > calls and errorlevel return codes, but nothing=20 > besides that so far. > > > > > > > > > > What AV scanners are people typically using? Is the=20 > ClamAV one=20 > > > > > fairly > > > > > > > > > robust / workable for Win32 (XMail 1.17 / Windows 2000). > > > > > > > > > > Thanks, > > > > > > > > > > ... Jason Badry > > > > > > > > > > At 08:37 PM 3/10/2004 +0200, you wrote: > > > > > >Arrrr, I forgot to mention that there's a new version of=20 > > > > > >ripMIME > > but=3D20 > > > > > >the Windows port seems to be causing some trouble so I=20 > > > > > >recommend=3D20 sticking to 1.3.0.5 for now (If anyone = *really*=20 > > > > > >wants > > 1.3.1.0/Win32,=3D20 > > > > > >e-mail me off the list). > > > > > > > > > > > >Liron Newman wrote: > > > > > > > > > > > > >Try using ripMIME from pldaniels.com. The main=20 > stable source=20 > > > > > > >tree=3D20 doesn't compile on Windows but I made a=20 > modified version that does. > > > >I've > > > > > > >worked with it for about a month and it stopped=20 > thousands of > > virus=3D20 > > > > > > >messages.. So you can say it's working well. :) > > > > > > > > > > > > > >Grab my build from > > > > > > > > > >=20 > ><http://eesh.net/ripmime-1.3.0.5.Modified_for_Win32_[plastish_at_ > > > > >ulti > > ne>t_ > > > > > > dot_org].zip>, > > > > > > >the EXE is under RipMime\Release in the ZIP. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >- > > > > > >To unsubscribe from this list: send the line "unsubscribe=20 > > > > > >xmail" in=3D20 the body of a message to=20 > [EMAIL PROTECTED] > > > > > >For general help:=3D20 send the line "help" in the body of a=20 > > > > > >message to=3D20 [EMAIL PROTECTED] > > > > > > > > > > - > > > > > To unsubscribe from this list: send the line=20 > "unsubscribe xmail"=20 > > > > > in=3D20 the body of a message to [EMAIL PROTECTED] For=20 > > > > > general help:=3D20 send the line "help" in the body of=20 > a message=20 > > > > > to=3D20 [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > >- > > > >To unsubscribe from this list: send the line=20 > "unsubscribe xmail" in=20 > > > >the body of a message to [EMAIL PROTECTED] For=20 > general help:=20 > > > >send the line "help" in the body of a message to=20 > > > >[EMAIL PROTECTED] > > > > > > > > > > > > > > > >- > > > >To unsubscribe from this list: send the line=20 > "unsubscribe xmail" in=20 > > > >the body of a message to [EMAIL PROTECTED] For=20 > general help:=20 > > > >send the line "help" in the body of a message to=20 > > > >[EMAIL PROTECTED] > > > > > >- > > >To unsubscribe from this list: send the line "unsubscribe=20 > xmail" in=20 > > >the body of a message to [EMAIL PROTECTED] For general help:=20 > > >send the line "help" in the body of a message to=20 > > >[EMAIL PROTECTED] > > > > > >- > >To unsubscribe from this list: send the line "unsubscribe=20 > xmail" in the=20 > >body of a message to [EMAIL PROTECTED] For general=20 > help: send the=20 > >line "help" in the body of a message to [EMAIL PROTECTED] >=20 > - > To unsubscribe from this list: send the line "unsubscribe=20 > xmail" in the body of a message to [EMAIL PROTECTED] > For general help: send the line "help" in the body of a=20 > message to [EMAIL PROTECTED] >=20 >=20 >=20 >=20 >=20 - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
