aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVsevolod Stakhov <vsevolod@highsecure.ru>2016-06-28 17:29:37 +0100
committerVsevolod Stakhov <vsevolod@highsecure.ru>2016-06-28 17:29:37 +0100
commitbfc724c71bd89a99ee3270cbd9bde6ae259fa532 (patch)
treeab0a793c303c76b2ff1fd613190ee714c57a1740
parent6883aef21422cc208d2b990d42a910bc76e6db24 (diff)
downloadrspamd-bfc724c71bd89a99ee3270cbd9bde6ae259fa532.tar.gz
rspamd-bfc724c71bd89a99ee3270cbd9bde6ae259fa532.zip
[Doc] Document how to use phishtank feed
-rw-r--r--doc/markdown/modules/phishing.md28
1 files changed, 28 insertions, 0 deletions
diff --git a/doc/markdown/modules/phishing.md b/doc/markdown/modules/phishing.md
index 98f688837..5218cc908 100644
--- a/doc/markdown/modules/phishing.md
+++ b/doc/markdown/modules/phishing.md
@@ -81,3 +81,31 @@ phishing {
openphish_premium = false;
}
~~~
+
+## Phishtank support
+
+There is also [phishtank](https://phishtank.com) support in rspamd since 1.3. Unlike
+openphish feed, phishtank's one is not enabled by default since it has quite a big size (about 50Mb) so
+you might want to setup some reverse proxy (e.g. nginx) to cache that data among rspamd instances:
+
+~~~nginx
+proxy_cache_path /data/nginx/cache levels=1:2 keys_zone=phish:10m;
+
+server {
+ listen 8080;
+ location / {
+ proxy_pass http://data.phishtank.com:80;
+ proxy_cache phish;
+ proxy_cache_lock on;
+ }
+}
+~~~
+
+
+To enable phishtank feed, you can edit `local.d/phishing.conf` file and add the following lines there:
+
+~~~ucl
+phishtank_enabled = true;
+# Where nginx is installed
+phishtank_map = "http://localhost:8080/data/online-valid.json";
+~~~ \ No newline at end of file