Scrollout F1 – The Unofficial Manual
This information which I learned on the forum when I needed it or figured out on my own. It is documented here to make it easier to find next time.
In No Particular Order…
Edit Aggressivity Levels
Need to Allow Blocked File Extensions from a Particular Domain
add the domain to the whitelist under Secure, Senders in the GUI [this doesn’t work]
you’ll have to delete the filetype in question under /var/www/cfg/agresivity/6/filetype
(the 6 corresponds to your setting on the Levels page)
Good Forum Post about Cryptolocker and Security
Edit RBL Domains and IPs
Scrollout is Blocking Emails Based on the Nameservers of the Sending Domain and Nothing Else
You’ll find these rbl servers listed under Secure / Levels / Rate Limits In
You can remove them if you won’t want this feature. Or you can add the nameserver IP in question to the reputation-ns-100 file to unblock it.
How To Block Macro Attachments
In /etc/clamav/clamd.conf change:
Now, any MS Office document having a Macro VBA will be identified as infected.
Change Display Colors To Something Readable
You can adjust color and opacity in styles #text_hron, #text_off and #hron in /var/www/css/style.css
Modify the opacity from 0.5 to 0.8 and increase the font size
Make a copy because updates will overwrite your changes.
If you want to change the SPF policy to allow Softfail:
Change HELO_reject = SPF_Not_Pass into
HELO_reject = Softfail
HELO_reject = Fail
You don’t need to restart any service.
Upgrade from Debian 7 to Debian 8
sed -i “s/wheezy/jessie/g” /etc/apt/sources.list
apt-get dist-upgrade -y
Will take some time: 30 minutes – 1 hour.
When you are asked, answer the default, press enter or “q” when you must read long info pages.
Fix SSL / Cert Issues
Scrollout F1 / Discussion / Get Help:Scrollout postfix/smtpd: SSL_accept error
Try to recreate the certificates by running these 2 commands:
Go to /var/www/cfg/agresivity/custom/ and edit postscreen_access.cidr
Input their IP or IP subnet based on the predefined values there.
Go to GUI, Route or Secure and click Apply.
View Mail In Queue
remove all mail from queue:
postsuper -d ALL
tips on clearing the mail queue
Amavis 100% CPU
problem continues even after a reboot
you probably have some bad messages stuck in the queue – check the queue and then clear it if there is nothing you care about
I usually stop the incoming mail flow (close port 25 on my firewall) and let the machine process the queue until it clears all but the bad messages. Once the queue is clear, reboot again.
Clear Postfix Cache (good for clearing recipient verification cache)
rm -f /var/lib/postfix/verify_cache.db
to reset the score for AM.IP_BAD_<ip-address> run:
redis-cli -n 1 FLUSHDB
Graph Stops Working Every Year on January 1
logrotate -f /etc/logrotate.conf