If you see this page, the nginx web server is successfully installed and working. Further configuration is required.
For online documentation and support please refer to
nginx.org.
Commercial support is available at
nginx.com.
This host (mx-relay-7.northwave.example) is part of an outbound mail relay tier. The HTTP service on port 80 is provided only for monitoring probes and protocol negotiation. There is no website hosted on this address. If you reached this page from a search engine result or a bookmark, the link is incorrect and should be updated.
For questions regarding mail delivery, bounce processing, or list-unsubscribe behaviour, please contact the network administrator at postmaster@northwave.example. We respond to abuse reports within one business day. Submitting reports through other channels generally delays resolution because the abuse desk is the only team with direct access to delivery logs and is responsible for classifying incidents and forwarding follow-up correspondence to the relevant sender system. A short summary of the reported message, including the message identifier when available, helps us locate the relevant queue entry quickly without requiring a deeper trace.
The relay software runs in a chrooted environment with strict outbound connection limits, and only authenticated senders may queue messages. Public HTTP traffic is rate-limited and logged. Repeated probes from the same source range may be temporarily blocked at the firewall, especially when the request pattern looks like an automated scanner. The block is reviewed automatically after a quiet period and lifted without intervention if the activity stops.
The relay accepts mail from sender systems that authenticate via SMTP-AUTH and pass DKIM signing. DMARC alignment is enforced for outbound traffic in accordance with the published policy of the originating domain. Bounce processing follows the conventions described in RFC 3464 and our handler will provide a final-recipient identifier for every reported delivery status. Soft bounces are retried with an exponential backoff for up to five days, after which the message is returned to the sender with a permanent status.
Operators on call can find the runbook for this tier in the internal wiki under mail/relay-7. The runbook covers queue inspection, manual flush procedures, and the steps required to escalate a delivery problem to the upstream peer. Changes to relay configuration are recorded in the deployment journal and require a peer review before they are applied. Emergency fixes are permitted but must be backfilled into the journal within twenty-four hours.
Message bodies are not stored on the relay. Header lines are recorded in the delivery log for diagnostic purposes and retained for thirty days. The delivery log is available only to authorised members of the operations team and is not shared with senders or recipients.
Thank you for using nginx.
nginx/1.24.0 — mx-relay-7.northwave.example