Haraka 3.0.1 → 3.0.3

package/docs/plugins/relay_acl.md

@@ -1,29 +0,0 @@
-relay\_acl
-========
-
-This plugin makes it possible to relay outbound mails using IP based ACLs
-and relay inbound mails using destination domains.
-
-Configuration
--------------
-
-* `config/relay_acl_allow`
-    Allowed IP ranges in CIDR notation, one per line.
-    IPs listed in here will be allowed to send mails without any furthur
-    checks.
-
-* `config/relay_dest_domains.ini`
-    Allowed destination domains. The format is in ini file, the domain
-    is the key and the value is in JSON, all under the [domains] section.
-    Currently supported field is "action": where the value can be
-    "accept" (accept the mail without further checks), "continue" (mails
-    are still subjected to further checks) or "deny" (reject the mails).
-
-    An example:
-
-    [domains]  
-    test.com = { "action": "continue" }
-
-    Please note that this config/relay\_dest\_domains.ini is shared with
-    plugins/relay\_force\_routing.js, which uses additional fields.
-

package/docs/plugins/relay_all.md

@@ -1,15 +0,0 @@
-relay\_all
-=========
-
-This plugin is useful in spamtraps to accept mail to any host, and to allow
-any user from anywhere to send email.
-
-Do NOT use this plugin on a real mail server, unless you really know what
-you are doing. If you use this plugin with anything that relays mail (such
-as forwarding to a real mail server, or the `deliver` plugin), your mail
-server is now an open relay.
-
-This is BAD. Hence the big letters. In short: DO NOT USE THIS PLUGIN.
-
-It is useful for testing, hence why it is here. Also I work with spamtraps
-a lot, so it is useful there.

package/docs/plugins/relay_force_routing.md

@@ -1,33 +0,0 @@
-relay\_force\_routing.js
-========
-
-This plugin allows you to force the next hop for the configured domains.
-It works a lot like the transport map of Postfix.
-
-Configuration
--------------
-
-* `config/relay_dest_domains.ini`
-    This config file is shared with relay\_acl.js, for the basics see the
-    documentation provided by plugins/relay\_acl.js.
-
-    relay\_force\_routing.js adds the field "nexthop": in the JSON value
-    of the domain. The value of "nexthop": can be hostname or IP optionally
-    follow by :port.
-
-    Example:
-
-    [domains]  
-    test.com = { "action": "continue", "nexthop": "127.0.0.1:2525" }
-
-    You can also define a default relay using the "any" domain, which will be
-    used if the message's destination domain doesn't match any of the domains
-    already defined.
-
-    Example:
-```
-    [domains]  
-    test.com = { "action": "continue", "nexthop": "127.0.0.1:2525" }
-    my.test.com = { "action": "continue", "nexthop": "127.0.0.1:2527" }
-    any = { "action": "continue", "nexthop": "10.10.10.1:2525"}
-```

package/plugins/data.headers.js

@@ -1,4 +0,0 @@
-
-exports.register = function () {
-    this.logerror(this, "data.headers is deprecated, remove it from config/plugins. See 'haraka -h headers'");
-}

package/plugins/relay_all.js

@@ -1,13 +0,0 @@
-// Just relay everything - could be useful for a spamtrap
-
-exports.register = function () {
-    this.logerror(this, "deprecated. see 'haraka -h relay'");
-    this.register_hook('rcpt', 'confirm_all');
-}
-
-exports.confirm_all = function (next, connection, params) {
-    const recipient = params.shift();
-    connection.loginfo(this, `confirming recipient ${recipient}`);
-    connection.relaying = true;
-    next(OK);
-}