Unisar 1.24.1867 manual What to do with infected emails, This is how the screen should look like

Page 64

10

Using

BitDefender integration

BitDefender

 

cat > $TMPFILE

#Scan it with BitDefender and remember the exitcode

$BDSCAN $TMPFILE EXIT=$?

#Remove the temporary file and return the exitcode rm -f $TMPFILE

exit $EXIT

#End of the script

What to do with infected emails

You will not be able to disinfect the message, the only action that can be done is ignore, therefore it's up to you to delete or move the email if BitDefender has found it infected or, better, instruct the email client to do so.

If you want to be able to scan emails from Pine using BitDefender, you have to change your Pine settings to enable Unix pipe commands. Follow these steps.

Start Pine and type S (for Setup), then C (for Config). Use the down-arrow key to find and highlight enable-unix-pipe-cmd(somewhere under Advanced Command Preferences) and enable this preference by typing X. Type E (for Exit Setup) and Y when asked to Save Changes.

Now, in the Index screen and when displaying the email, there is one more command:

Pipe, ready to be tested.

1.When displaying a message or in the Index screen, press the Pipe key (Shift+\).

2.The entire message has to be sent to the filter, so press Control+W (Raw text). The status line should display the message: Pipe RAW message X to :.

3.Type the full path to the filter, not only the script name, for example

/opt/BitDefender-scanner/bin/bdscanpipe, and press ENTER.

This is how the screen should look like.

Pipe RAW message 299 to : /opt/BitDefender-scanner/bin/bdscanpipe

^G Help^W Shown Text ^R With Delimiter ^C Cancel Ret Accept ^Y Free Output

The full email will be piped to BitDefender filter, which will save it temporary on the filesystem and scan this file with bdscan. After the scan, the output results are

64

Image 64
Contents Users Guide Users Guide As every cat owner knows, nobody owns a cat BitDefender Antivirus Scanner for Unices Table of Contents Uninstall Configuration file Testing BitDefenderReal life usage BitDefender integrationUpdates Frequently Asked Questions SupportProduct registration Best practicesBitDefender Antivirus Scanner for Unices Viii End User Software License Agreement End User Software License Agreement End User Software License Agreement Xii Conventions used in this book PrefaceTypographical conventions Command AdmonitionsBook structure Request for Comments Description and features Description and features Why BitDefender? OverviewData Security Division Softwin Description Product features BitDefender Antivirus Scanner for UnicesKey Features Scanning mechanism More in the manualFeatures Installation Installation System requirements PrerequisitesHardware system requirements Package naming convention Software system requirementsLinux convention Linux requirementsFreeBSD convention Installation Test the package for integrity Package installationTest the rpm and deb packages Test the self-extractable archive Test the FreeBSD tbz packageInstall the package Install the rpm packageInstall the deb package Install the self-extractable archiveAdditional parameters Installer Install the FreeBSD packageConfigures the quarantine directory Uninstall Uninstall the rpm packageUninstall the deb package Uninstall using the self-extractable archiveUninstall a package downloaded locally Uninstall the FreeBSD packageUninstall from the ports collection Using BitDefender Using BitDefender Configuration file System versus User configurationMore about triggered update Key DescriptionUsing07 BitDefender Regular users and quarantineUsing BitDefender Product registrationScan an executable file Testing BitDefenderEicar online resources Command output will be the following Scan an archiveScan a mailbox Tmp/mail.mbox Virus scanning Real life usageScan a regular file Scan a directory Scan the entire system Scan the archives Actions on archivesScan the mailbox Using the log file ReportGet more information Display the virus listVirus submission Display the product versionBitDefender integration Midnight CommanderDesktop integration KDE Konqueror Different installation pathDo not break the last line Krusader Action on file in KonquerorROX-Filer Krusaders User ActionsPine Pine Information CenterWhat to do with infected emails This is how the screen should look likeExit Status Interval 1,254 Evolution BitDefender pipe bdscanpipeKMail Server integration Filter actions in KMailMailScanner installation Qmail-Scanner installationMailScanner Amavisd-new Change it to the following formAmavisd-new installation Using Updates Triggered updateRun the triggered update Regular updatesEdit the cron table Manual update Http proxyOrder to extract the updates Trial License License for home or personal use Product registrationCheck the expiration date License for commercial use Best practices Best practices Getting help Getting help Frequently Asked Questions Getting help Support department SupportBitDefender Knowledge Base Contact information Web addressesAddress Softwin GmbHRomania BitDefender LLCGetting help Manual Pages Manual Pages Description SynopsisOptions Manual Pages Actions Examples FilesBugs See alsoManual Pages Glossary Command line CookieDisk drive DownloadEvents False positiveFilename extension HeuristicMacro virus Mail clientNon-heuristic Packed programsPort Report fileScript Startup itemsUpdate VirusVirus definition Worm