Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix accidental misspellings #348

Merged
merged 1 commit into from
Feb 28, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/faq/non_relay_hosts.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ log_oob = true
log_arf = true
{% endcall %}

As you operate your server, you may be concerned to discover in your logs that messages are bring accepted from hosts not listed in your `relay_hosts` list.
As you operate your server, you may be concerned to discover in your logs that messages are being accepted from hosts not listed in your `relay_hosts` list.

```json
{
Expand Down Expand Up @@ -60,4 +60,4 @@ This occurs because of the `log_oob` and `log_arf` options being enabled for `*`

Whenever any of the `relay_to`, `log_oob`, or `log_arf` options are set to `true`, KumoMTA cannot immediately reject connections from hosts not listed in `relay_hosts` because it needs to see whether the remote host is sending messages to one of the domains listed in the `listener_domains` helper configuration.

After a `RCPT TO` command is received, KumoMTA will check whether the destination domain is listed in the `listener_domain` config and if so, will receive the message and act accordingly. This can result is messages being received that may or may not be queued after being processed as an OOB and/or ARF message, depending on whether `relay_to` is set to `true`.
After a `RCPT TO` command is received, KumoMTA will check whether the destination domain is listed in the `listener_domain` config and if so, will receive the message and act accordingly. This can result in messages being received that may or may not be queued after being processed as an OOB and/or ARF message, depending on whether `relay_to` is set to `true`.