O suporte técnico está disponível a partir de qualquer uma das opções abaixo. Todos os pedidos de apoio devem ser feitos em Inglês. Você deve ser conectado à nossa área de clientes para abrir um bilhete com os departamentos de suporte, faturamento e licenciamento.

O suporte prioritário está disponível de segunda a sexta-feira das 8h às 17h MDT.
A data e a hora locais atuais são Thursday - 2021-04-15 01:35 am MDT.




Instruções de instalação

Saiba como instalar o produto.

Começando

Saiba como configurar o produto.

Solucionando problemas

Tendo problemas? Aprenda a diagnosticar e depurar problemas.

Base de Conhecimento

Perguntas e respostas de auto-ajuda para suporte ao produto, incluindo perguntas de pré-vendas.


How to test SpamAssassin To test the spam filter, it is necessary to send a Gtube test spam email using the command below (Replacing emailonserver@example.com with a real email account on the server). If the Anti-spam is working correctly you will see it listed in the maillog and in Warden log under Warden -> Logs -> Message Log. While testing, note that Gtube test email gives +1000 scores to spam. So, even if a mailbox is in the whitelist, mail still be detected as spam because whitelisted email gets -100 scores. Disable Greylisting: If greylisting is enabled then you must disable it on the recipient domain before running these tests. /usr/local/psa/bin/grey_listing --update-domain example.com -status off Centos / RHEL / CloudLinux: echo "XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X" | mail -S smtp=localhost -r sender@example.com -s "Spam test example" emailonserver@example.com Debian / Ubuntu: apt-get install s-nail echo "XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X" | s-nail -S smtp=localhost -r sender@example.com -s "Spam test example" emailonserver@example.com How to test ClamAV
To test the virus filter, it is necessary to download the eicar test virus email and send it using the command below (Replacing emailonserver@example.com with a real email account on the server). If the Anti-virus is working correctly you will see it get blocked and it will be listed in the maillog and in Warden -> Logs -> Message Log. Disable Greylisting: If greylisting is enabled then you must disable it on the recipient domain before running these tests. /usr/local/psa/bin/grey_listing --update-domain example.com -status off Centos / RHEL / CloudLinux: wget http://www.eicar.org/download/eicar.com.txt echo "TEST MESSAGE w/ ATTACHMENT" | mail -S smtp=localhost -r sender@example.com -s "A/V test example" -a eicar.com.txt emailonserver@example.com Debian / Ubuntu: apt-get install s-nail wget http://www.eicar.org/download/eicar.com.txt echo "TEST MESSAGE w/ ATTACHMENT" | s-nail -S smtp=localhost -r sender@example.com -s "A/V test example" -a eicar.com.txt emailonserver@example.com
Veja o artigo completo...

1. Make sure that you are not blocking the licensing server IP addresses on the servers firewall. Imunify360 is known to block our server IPs for some reason. Our licensing server IP addresses are: IPv4: 198.27.80.6 IPv6: 2607:5300:60:2106:: You can run the following command to see if your server can connect to the licensing server. You should get a response of Verify return code: 0 (ok) if the connection was successful. openssl s_client -connect www.danami.com:443 If you get the error below that means that your server cannot connect to our licensing server (usually that means there is a firewall or connection problem): openssl s_client -connect www.danami.com:443 - returns: socket: Bad file descriptor connect:errno=9 2. Make sure that the date and time on the server is correct (The wrong time will cause the SSL certificate connection to fail). Install a NTP time sync daemon on your server like Chrony or if ntpdate is installed on the server you can sync your server time using the command: /usr/sbin/ntpdate -b -s time.nist.gov 3. Many times this error can be fixed by restarting the Plesk panel: /etc/init.d/psa restart 4. Lastly make sure your openssl and curl packages are up to date: // Centos / RHEL yum update openssl curl // Debian / Ubuntu apt-get update openssl curl 5. If you have tried all of the above steps and you are still not able to connect to the licensing server please open a support ticket and include your servers IP address. The tech will run some additional tests on our side to see what the problem is.
Veja o artigo completo...

Lots of people seem to be confused by the "autolearn=no" statement in the default X-Spam-Status header. There are usually questions regarding whether or not "no" means SpamAssassin is not autolearning at all. What it actually means is that the specific message which includes the "autolearn=no" part was not autolearned, not that autolearning is disabled or somehow broken.

The three values that can be displayed are "no" (autolearning did not occur), "ham" (the message was learned as ham), and "spam" (the message was learned as spam).

If a message has already been learned by SpamAssassin, then that message will not be learned again. Therefore, if you run a message through SpamAssassin to see why it was classified as spam or ham, and it has already been learned, you will always get the result "autolearn=no". (To see this more clearly, use the "-D" flag, and you will see debug output explaining that the message has already been learned.)

Furthermore, the score used to trigger autolearning is somewhat different than the one reported in the final score; therefore a score displayed in the headers that ostensibly should trigger autolearning will not do so. Again, use the "-D" flag to SpamAssassin, and you will see the score that is used to determine whether or not autolearning will be triggered.

Finally, SpamAssassin requires at least 3 points from the header and 3 points from the body, to auto-learn as spam. If either section contributes fewer points, the message will not be auto-learned.

Possible Autolearn States

ham: the message was learned as ham (non-spam)
spam: the message was learned as spam
no: the specific message didn't achieve the proper threshold values and requirements to be learned
disabled: the configuration specifies bayes_auto_learn 0 or use_bayes 0 and so no autolearning is attempted
failed: autolearning was attempted, but couldn't complete. This happens if SpamAssassin can't gain a lock on the Bayes database files, etc.
unavailable: autolearning not completed for any reason not covered above. It could be the message was already learned. Reasons why Autolearn isn't Working 1. In order for autolearn to work you need at least 200 trained messages in the ham and spam category.
2. If using Redis Bayes storage your Bayes Token TTL might be too low so the spam entries expire before they reach the 200 trained messages threshhold. Try raising the Bayes Token TTL to 180d
Veja o artigo completo...

Amavis with ClamAV will scan inside zip files by default. You can also extend the protection by using the sanesecurity foxhole databases.

The sanesecurity free ClamAV rules will cover this. Take a look at the Foxhole databases specifically

http://sanesecurity.com/foxhole-databases/

How to enable free ClamAV Third Party Signatures

https://www.danami.com/clients/knowledgebase/137/How-can-I-install-third-party-unofficial-signatures-for-ClamAV.html
Veja o artigo completo...

Uninstalling Warden is as easy as going to Extensions -> My Extensions -> Warden Anti-spam and Virus Protection -> Press the remove button. You can also uninstall the extension on the command line with: /usr/local/psa/bin/extension --uninstall warden
Veja o artigo completo...

Amavis will prepend to Subject (for local recipients only) if mail could not be decoded or checked entirely, e.g. due to password-protected archives. To disable this on Centos/RHEL edit the file /etc/amavisd/amavisd.conf or on Debian/Ubuntu edit the file /etc/amavis/conf.d/99-warden and add the line (before the last line 1;): $undecipherable_subject_tag = undef; After making the changes restart Amavis: // Centos/RHEL/Cloudlinux systemctl restart amavisd // Debian/Ubuntu systemctl restart amavis
Veja o artigo completo...

By default mail with bad headers is quarantined for review but are still delivered to the users mailbox. If you would like to change this to discard mail with bad headers you can change the setting under Warden -> Settings -> Filter Settings -> Final bad header destiny from pass to discard. To disable all bad header tests: To disable all bad header tests on Centos/RHEL edit the file /etc/amavisd/warden.conf or on Debian/Ubuntu edit the file /etc/amavis/conf.d/99-warden and search for the @bypass_header_checks_maps option. Change from: @bypass_header_checks_maps = (\%bypass_header_checks, \@bypass_header_checks_acl, \$bypass_header_checks_re); Change to: @bypass_header_checks_maps = [1]; After making these changes restart Amavis: // Centos/RHEL/Cloudlinux systemctl restart amavisd // Debian/Ubuntu systemctl restart amavis To disable all bad header tests for a specific policy bank: If we want to keep bad header tests enabled for incoming email but disable them for our own users. Edit the file /etc/amavisd/warden.conf or on Debian/Ubuntu edit the file /etc/amavis/conf.d/99-warden and add the bypass_header_checks_maps => [1] line to the SUBMISSION and SENDMAIL policy banks: ## POLICY BANKS # submission, SMTPS services $policy_bank{'SUBMISSION'} = { originating => 1, warnbadhsender => 0, terminate_dsn_on_notify_success => 0, bypass_header_checks_maps => [1], }; # sendmail, pickup services $interface_policy{'10027'} = 'SENDMAIL'; $policy_bank{'SENDMAIL'} = { originating => 1, warnbadhsender => 0, terminate_dsn_on_notify_success => 0, bypass_header_checks_maps => [1], }; After making these changes restart Amavis: // Centos/RHEL/Cloudlinux systemctl restart amavisd // Debian/Ubuntu systemctl restart amavis To disable specific bad header tests: There is an $allowed_header_tests option by which you can define what should be looked up during the bad-header checks, and the list is as follows: other catchall for everything else - normally not used mime Bad MIME (sub)headers or bad MIME structure 8bit Invalid non-encoded 8-bit characters in header control Invalid control characters in header (CR or NUL) empty Folded header field made up entirely of whitespace long Header line longer than RFC 2822 limit of 998 characters syntax Header field syntax error missing Missing required header field multiple Duplicate or multiple occurrence of a header field To disable certain tests on Centos/RHEL edit the file /etc/amavisd/warden.conf or on Debian/Ubuntu edit the file /etc/amavis/conf.d/99-warden and search for the $allowed_header_tests option. Setting a test to 0 will disable that test: $allowed_header_tests{'multiple'} = 0; $allowed_header_tests{'missing'} = 0; After making these changes restart Amavis: // Centos/RHEL/Cloudlinux systemctl restart amavisd // Debian/Ubuntu systemctl restart amavis  
Veja o artigo completo...

Cloudlinux / Imunify360 added their own version of ClamAV to their repo which accidentally replaces the EPEL version of ClamAV required by Warden. To Fix: Remove the Imunify360 ClamAV rpm -e --nodeps clamav clamav-data clamav-filesystem clamav-lib clamav-update clamav-server Exclude their ClamAV packages from Yum Add the line exclude=clam* to the [imunify360] repo section in the file /etc/yum.repos.d/imunify360.repo or /etc/yum.repos.d/cloudlinux-imunify360.repo (if they exist). After it should look something like this (do not use our example as it will vary from system to system): [imunify360] name=EL-7 - Imunify360 baseurl=https://repo.imunify360.cloudlinux.com/defense360/el/7/updates/x86_64/ username=defense360 password=XXX enabled=1 gpgcheck=1 gpgkey=https://repo.imunify360.cloudlinux.com/defense360/RPM-GPG-KEY-CloudLinux exclude=clam* In Warden go to Settings -> Application setup and go though the Warden Setup Wizard again to re-run the product installer (applying the default settings to the Antivirus pages) to re-apply the correct settings that were replaced by the Immunify360 ClamAV. If you still have trouble don't hesitate to open a ticket to have a support technician fix this for you.
Veja o artigo completo...

Veja tudo...


Instruções de instalação

Saiba como instalar o produto.

Começando

Saiba como configurar o produto.

Solucionando problemas

Tendo problemas? Aprenda a diagnosticar e depurar problemas.

Base de Conhecimento

Perguntas e respostas de auto-ajuda para suporte ao produto, incluindo perguntas de pré-vendas.


To permanently disable all low level kernel messages (iptables etc) from flooding the console do the following changes (as root):

Edit the file /etc/sysctl.conf Add the following line: kernel.printk = 4 1 1 7 The above changes will be effective at reboot or immediately using the following command: /sbin/sysctl -p /etc/sysctl.conf To make the changes only temporarily: echo "4 1 1 7" > /proc/sys/kernel/printk You can check the current setting with: cat /proc/sys/kernel/printk
Veja o artigo completo...

1. Make sure that you are not blocking the licensing server IP addresses on the servers firewall. Imunify360 is known to block our server IPs for some reason. Our licensing server IP addresses are: IPv4: 198.27.80.6 IPv6: 2607:5300:60:2106:: You can run the following command to see if your server can connect to the licensing server. You should get a response of Verify return code: 0 (ok) if the connection was successful. openssl s_client -connect www.danami.com:443 If you get the error below that means that your server cannot connect to our licensing server (usually that means there is a firewall or connection problem): openssl s_client -connect www.danami.com:443 - returns: socket: Bad file descriptor connect:errno=9 2. Make sure that the date and time on the server is correct (The wrong time will cause the SSL certificate connection to fail). Install a NTP time sync daemon on your server like Chrony or if ntpdate is installed on the server you can sync your server time using the command: /usr/sbin/ntpdate -b -s time.nist.gov 3. Many times this error can be fixed by restarting the Plesk panel: /etc/init.d/psa restart 4. Lastly make sure your openssl and curl packages are up to date: // Centos / RHEL yum update openssl curl // Debian / Ubuntu apt-get update openssl curl 5. If you have tried all of the above steps and you are still not able to connect to the licensing server please open a support ticket and include your servers IP address. The tech will run some additional tests on our side to see what the problem is.
Veja o artigo completo...

Yes we support blocking attacks like these very easily. See the howto for how to enable a custom login failure trigger:
https://docs.danami.com/juggernaut/how-tos/enable-login-failure-triggers
Veja o artigo completo...

This error means that your service provider is limiting the amount if iptables rules (numiptent)  that your VPS is allowed to create. Your provider can easily raise this limit using the command below on the hardware note (it can't be run inside your VPS). If your provider refuses to raise this limit then it's time to look for a new service provider as they do not really care about your security. vzctl set CID --numiptent 10000 --save Users using Virtuozzo with a limit set will not be able to use the country or blocklists as they will usually put them over their limit. Users can limit the amount of rules that Juggernaut will create by setting the deny permanently limit and deny temporarily limit under Juggernaut -> Settings -> General Settings. Juggernaut will rotate out older entries to stay under the limit set unless the entry is marked with "do not delete". You can also try to limit the number of iptables rules used for country block lists under Juggernaut -> Settings -> Country Settings -> Ignore CIDR blocks smaller than (set it to something like /24). This will allow you to still block the majority of the country while ignoring the smaller networks. Note
Virtuozzo 6 and below is not the ideal VPS because it does not support ipset for high performance firewall blocking. Most of the larger VPS providers like OVH, Digital Ocean, and Linode have long switched away from using Virtuozzo and now use KVM which fully supports ipset. Even Virtuozzo themselves have switched over to using KVM in Virtuozzo 7.

Veja o artigo completo...

Maxmind pulled public access to the GeoLite2 databases as of Dec 30/2019. You now need a free license key before you can download them. You can read about the changes here:

https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/ Instructions for how to sign up for the free license key can be found below: Warden Anti-spam and Virus Protection
https://docs.danami.com/warden/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key Juggernaut Firewall
https://docs.danami.com/juggernaut/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key Sentinel Anti-malware
https://docs.danami.com/sentinel/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key
Veja o artigo completo...

You can disable and enable the firewall from the command line using the following commands:

To disable the firewall: csf -x To re-enable the firewall: csf -e To get the list of all command line options: csf --help
Veja o artigo completo...

The login failure daemon can crash if you are monitoring a lot of domains in Plesk and are reaching the open file limit for your server. To raise the limit: Edit the login failure daemon systemd service: systemctl edit lfd.service Add the following to the override.conf file: [Service] LimitNOFILE=65536 Reload  systemd: systemctl daemon-reload Restart the LFD service: systemctl restart lfd.service
Veja o artigo completo...

You can change the interface language under Settings -> Application Settings -> Locale   We are looking for volunteers to fix any errors with the machine translations in our Plesk extensions for the following languages: Español (Spain)
Français (France)
Português (Brazil)
Magyar (Hungary)
Русский (Russia)
Türkçe (Turkey)
Svenska (Sweden)
中文 (China)
中文 (Taiwan/Hong Kong)
日本語 (Japan) Volunteers will get a free license for every Plesk extension that they help translate. The translator must be a native speaker of the language they are translating. The license will remain free as long as they want to remain the translator for that language. Open a support ticket though our client area if you are interested.  
Veja o artigo completo...

Veja tudo...


Instruções de instalação

Saiba como instalar o produto.

Começando

Saiba como configurar o produto.

Solucionando problemas

Tendo problemas? Aprenda a diagnosticar e depurar problemas.

Base de Conhecimento

Perguntas e respostas de auto-ajuda para suporte ao produto, incluindo perguntas de pré-vendas.


1. Make sure that you are not blocking the licensing server IP addresses on the servers firewall. Imunify360 is known to block our server IPs for some reason. Our licensing server IP addresses are: IPv4: 198.27.80.6 IPv6: 2607:5300:60:2106:: You can run the following command to see if your server can connect to the licensing server. You should get a response of Verify return code: 0 (ok) if the connection was successful. openssl s_client -connect www.danami.com:443 If you get the error below that means that your server cannot connect to our licensing server (usually that means there is a firewall or connection problem): openssl s_client -connect www.danami.com:443 - returns: socket: Bad file descriptor connect:errno=9 2. Make sure that the date and time on the server is correct (The wrong time will cause the SSL certificate connection to fail). Install a NTP time sync daemon on your server like Chrony or if ntpdate is installed on the server you can sync your server time using the command: /usr/sbin/ntpdate -b -s time.nist.gov 3. Many times this error can be fixed by restarting the Plesk panel: /etc/init.d/psa restart 4. Lastly make sure your openssl and curl packages are up to date: // Centos / RHEL yum update openssl curl // Debian / Ubuntu apt-get update openssl curl 5. If you have tried all of the above steps and you are still not able to connect to the licensing server please open a support ticket and include your servers IP address. The tech will run some additional tests on our side to see what the problem is.
Veja o artigo completo...

1. Double check that the default_monitor_mode is set: Edit /usr/local/maldetect/conf.maldet and find and set: default_monitor_mode="users" 2. Some users may also need to increase their inotify file watch limit on their systems before the maldet monitoring daemon will start. To view your current limit: cat /proc/sys/fs/inotify/max_user_watches To raise your limit: echo fs.inotify.max_user_watches=1048576 > /etc/sysctl.d/sentinel.conf sysctl -p /etc/sysctl.d/sentinel.conf Start the service: systemctl restart maldet Check the logs for any errors: tail -f /usr/local/maldetect/logs/event_log Example error of when max_user_watches is too low: Please increase the amount of inotify watches allowed per user via `/proc/sys/fs/inotify/max_user_watches'.
Veja o artigo completo...

Maxmind pulled public access to the GeoLite2 databases as of Dec 30/2019. You now need a free license key before you can download them. You can read about the changes here:

https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/ Instructions for how to sign up for the free license key can be found below: Warden Anti-spam and Virus Protection
https://docs.danami.com/warden/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key Juggernaut Firewall
https://docs.danami.com/juggernaut/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key Sentinel Anti-malware
https://docs.danami.com/sentinel/settings/panel-application/geolocation-settings#how-to-get-a-maxmind-license-key
Veja o artigo completo...

There is a bug in the Linux Malware Detect v1.6.4 daily cron script. You can fix the error by changing line 69 in /etc/cron.daily/maldet From: elif [ $cron_daily_scan == "1" ]; then To: elif [ "$cron_daily_scan" == "1" ]; then
Veja o artigo completo...

Warden requires that you use the ClamAV packages from the EPEL repository. In order to prevent the wrong packages from being installed you must add the line exclude=clam* to any conflicting repositories.
For example if you have the imunify360 repo installed edit the file /etc/yum.repos.d/imunify360.repo Before: [imunify360] name=EL-7 - Imunify360 baseurl=https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/ username=defense360 password=nraW!F@$x4Xd6HHQ enabled=1 gpgcheck=1 gpgkey=https://repo.imunify360.cloudlinux.com/defense360//RPM-GPG-KEY-CloudLinux After: [imunify360] name=EL-7 - Imunify360 baseurl=https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/ username=defense360 password=nraW!F@$x4Xd6HHQ enabled=1 gpgcheck=1 gpgkey=https://repo.imunify360.cloudlinux.com/defense360//RPM-GPG-KEY-CloudLinux exclude=clam* After this is done the extension installer will be able to complete successfully.
Veja o artigo completo...

Enabling ClamAV Third Party Signatures The clamav-unofficial-sigs script provides a simple way to download, test, and update third-party signature databases provided by Sanesecurity, FOXHOLE, OITC, Scamnailer, BOFHLAND, CRDF, Porcupine, Yara-Rules Project, etc. The clamav-unofficial-sigs script will also generate and install cron, logrotate, and man files. See: clamav-unofficial-sigs for more information. Important
• Rysnc requires that port 873 TCP OUT be opened if you are using a firewall. It must be opened in order to use the script.
• The ClamAV daemon will use over 1GB RAM when enabling the all the signatures together.
• The new signatures will be downloaded to the /var/lib/clamav directory. Centos/RHEL/Cloudlinux There are packages in the EPEL repo that make it easy to install the third party signatures. Signatures will be updated automatically using a cron that the package installs. yum install rsync wget unzip bind-utils clamav-unofficial-sigs // the config file is located at /etc/clamav-unofficial-sigs/user.conf // run the command once to test (run as root) /usr/sbin/clamav-unofficial-sigs.sh // you can view the log using the command tail -f /var/log/clamav-unofficial-sigs/clamav-unofficial-sigs.log You should see the new signatures downloaded to the /var/lib/clamav directory. Debian/Ubuntu There are no up-to-date packages for Debian/Ubuntu so we must install it manually. apt-get install rsync wget unzip dnsutils wget https://github.com/extremeshok/clamav-unofficial-sigs/archive/master.zip unzip master.zip cd clamav-unofficial-sigs-master/ cp -f clamav-unofficial-sigs.sh /usr/local/bin/ chmod 755 /usr/local/bin/clamav-unofficial-sigs.sh mkdir /etc/clamav-unofficial-sigs/ cp -r config/* /etc/clamav-unofficial-sigs/ cd /etc/clamav-unofficial-sigs/ // Copy /etc/clamav-unofficial-sigs/os/os.your-distro.conf to the parent directory as /etc/clamav-unofficial-sigs/os.conf where your-distro is your distribution and version e.g. cp /etc/clamav-unofficial-sigs/os/os.ubuntu.conf /etc/clamav-unofficial-sigs/os.conf Edit the file /etc/clamav-unofficial-sigs/user.conf and uncomment your user config options making sure to set default_dbs_rating to LOW, MEDIUM, or HIGH and uncomment the user_configuration_complete
option after you are done. # Default dbs rating # valid rating: LOW, MEDIUM, HIGH default_dbs_rating="MEDIUM" # Uncomment the following line to enable the script user_configuration_complete="yes" Run the script once as your superuser to set all the permissions and create the relevant directories: /usr/local/bin/clamav-unofficial-sigs.sh --force Install the cron, log rotate and man pages: /usr/local/bin/clamav-unofficial-sigs.sh --install-cron /usr/local/bin/clamav-unofficial-sigs.sh --install-logrotate /usr/local/bin/clamav-unofficial-sigs.sh --install-man You should see the new signatures downloaded to the /var/lib/clamav directory. Signatures Requiring Registration: MalwarePatrol Free
- We do not recommend using MalwarePatrol due to the high number of false positives from that signature provider.  
Veja o artigo completo...

You can change the interface language under Settings -> Application Settings -> Locale   We are looking for volunteers to fix any errors with the machine translations in our Plesk extensions for the following languages: Español (Spain)
Français (France)
Português (Brazil)
Magyar (Hungary)
Русский (Russia)
Türkçe (Turkey)
Svenska (Sweden)
中文 (China)
中文 (Taiwan/Hong Kong)
日本語 (Japan) Volunteers will get a free license for every Plesk extension that they help translate. The translator must be a native speaker of the language they are translating. The license will remain free as long as they want to remain the translator for that language. Open a support ticket though our client area if you are interested.  
Veja o artigo completo...

To run a Malware Scan Navigate to Sentinel Anti-malware -> Scan Select the specific domains you want to scan or choose All domains to scan all of them. Click the Scan button to start the scan. After the scans are complete the scan report will be listed under the Reports tab. To View a Scan Report
Navigate to Sentinel Anti-malware -> Reports Click on a Scan ID entry in the grid for the report you want to view. Any detected malware will be listed under the Malware Hits section. To Perform an Action on the Malware hits Click on the Actions tab for the scan report. Choose an operation to perform from the select list (Quarantine, Restore, Clean, Email). Press the Run button to perform the selected action.
Veja o artigo completo...

Veja tudo...