-
-
Notifications
You must be signed in to change notification settings - Fork 658
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- tls_socket: load TLS certs in subdirs (config/tls/sub/*.(key|crt)
- tls_socket: - getSocketOpts is now async - parse_x509 is now async - shed dependency on caolan/async & openssl-wrapper - get_certs_dir is now async - completely refactored. - config/tls loading is now recursive - watches config/tls for changes - tolerate spaces in CN string - outbound: use HarakaMx class for MX objects - line_socket: remove unused callback - outbound/client_pool: don't use line_socket, use tls_socket directly - client_pool: sock.name is now JSON of socket args - client_pool.get_client & release_client: arity of 5 -> 2 - catch ENOENT for config/tls - doc(tls): updated with TLS dir rules - workaround for windows * restriction
- Loading branch information
Showing
14 changed files
with
360 additions
and
372 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -148,28 +148,10 @@ Upon starting delivery the `get_mx` hook is called, with the parameter set to | |
the domain in question (for example a mail to `[email protected]` will call the | ||
`get_mx` hook with `(next, hmail, domain)` as parameters). This is to allow | ||
you to implement a custom handler to find MX records. For most installations | ||
there is no reason to implement this hook - Haraka will find the correct MX | ||
records for you. | ||
|
||
The MX record is sent via next(OK, mx) and can be one of: | ||
|
||
* A string of one of the following formats: | ||
* hostname | ||
* hostname:port | ||
* ipaddress | ||
* ipaddress:port | ||
* An MX object of the form: `{priority: 0, exchange: hostname}` with the | ||
following optional properies: | ||
* `port` to specify an alternate port | ||
* `bind` to specify an outbound IP address to bind to | ||
* `bind_helo` to specify an outbound helo for IP address to bind to | ||
* `using_lmtp` boolean to specify that delivery should be attempted using | ||
LMTP instead of SMTP. | ||
* `auth_user` to specify an AUTH username (required if AUTH is desired) | ||
* `auth_pass` to specify an AUTH password (required if AUTH is desired) | ||
* `auth_type` to specify an AUTH type that should be used with the MX. | ||
If this is not specified then Haraka will pick an appropriate method. | ||
* A list of MX objects in an array, each in the same format as above. | ||
there is no reason to implement this hook - Haraka will find the MX | ||
records via DNS. | ||
|
||
The MX is sent via next(OK, mx). `mx` is a [HarakaMx](https://github.com/haraka/haraka-net-utils?tab=readme-ov-file#harakamx) object, an array of HarakaMx objects, or any suitable HarakaMx input. | ||
|
||
### The deferred hook | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.