SMTP 554 5.7.1 — message rejected
The mail.logos.net.pl server may return 554 5.7.1 when a message does not satisfy its security or mail relay rules.
The 5.7.1 code alone does not identify a single reason for the rejection. Check the complete SMTP response text.
Relay access denied
Example response:
554 5.7.1 Relay access denied
The server refused to relay the message to an external recipient.
This usually means that a client attempted to send a message through the SMTP server without the required permission.
What should you check?
- Is the client using the correct outgoing mail server?
- Is the message being submitted through port
587? - Is the client authenticating with the correct username and password?
- Are the recipient address and account settings correct?
A public MX server is not intended to relay anonymous messages to arbitrary domains.
Sender authentication failed
Example response:
554 5.7.1 Sender authentication failed
The server rejected the message because it did not pass the required sender identity checks.
The logos.net.pl domain uses SPF, DKIM and DMARC. If a message claims to come from a protected domain but does not pass the required DMARC validation, it may be rejected during the SMTP session.
What should you check?
- Was the message sent from an authorised server?
- Does the domain publish a correct SPF record?
- Does the message contain a valid DKIM signature?
- Does the domain authenticated by SPF or DKIM align with the domain in the
From:header? - Was the message forwarded through a system that modifies its content or headers?
An SPF failure does not necessarily cause DMARC to fail if the message has a valid, aligned DKIM signature.
At what stage is the message rejected?
Relay access denied may be returned during the RCPT TO command.
Sender authentication failed may be returned only after the message content has been transmitted, when the server performs authentication checks after the dot terminating the data sent following the DATA command.
If the server rejected the message with a 5xx response, it did not accept the message for further delivery in that attempt.
Need help?
If messages are rejected despite an apparently correct configuration, the complete SMTP response, event time and information about the sending server will be useful for diagnosis.
Do not send passwords, tokens or other authentication credentials.
If you need help analysing SMTP responses, SPF, DKIM and DMARC configuration or mail server logs, see the business email diagnostics service.
