Status types

In the following, the individual status types are explained by means of examples.

NOTE: This information is for basic understanding and does not necessarily cover every case.

  • Successful The email was successfully transmitted to the recipient.
  • Delivery failed An outbound email was rejected by the receiving system. In the "Delivery" tab, you can track the feedback from the receiving system.
  • Temporarily rejected The delivering email server receives a response and will make another delivery attempt after the configured interval.
    • Greylisting An inbound email has received at least 2 SCL points for violating our filters.
    • Recipient does not match the rule of the first recipient An outbound email is sent to different recipients and a certificate for encryption is not available for each recipient.
    • 32Guards A recently righted host is temporarily rejected for a short period of time to determine its reputation.
    • Service not reachable The Integrated Malware Scanner is usually configured as the only selected Malware scanner but is not reachable.
  • Permanently rejected The email was rated with at least 4 SCL points due to violation of our filters or rejected by Actions in NoSpamProxy.
  • Delivery pending The email is still being delivered and will be noted shortly with a different status depending on the result. Details can be found on the tab Delivery.
  • Multiple delivery states An email was sent to several recipients and noted with different results. Details can be found in the respective entry on the tab Delivery.
  • Accepted but not delivered The email is received but cannot be processed.
    • Outbound content filtering The stored content filter prohibits the attachment of the e-mail.
    • Encryption A rule with mandatory encryption is used; this was not possible for the recipient.
    • The sender has established a connection but has not transmitted an email body In this case, NoSpamProxy only sees the email envelope with sender and recipient, but cannot process the email. Often such a connection is created to validate an email address of a previously outgoing email and is intended to serve as an anti-spam measure. The process is known as callback verification.
    • De-Mail An attempt is made to deliver an email for which there is no configuration in NoSpamProxy to a De-Mail recipient.
  • Duplicate An email was delivered twice to NoSpamProxy. The loop (email loop) is prevented and the email is not delivered.
    • An inbound email is delivered by NoSpamProxy to the configured email server. However, this email does not end up in the recipient's mailbox, but the email server sends it back to NoSpamProxy again a few seconds after receiving the email.
    • An inbound email was sent twice with the same message ID from the same or different submitting systems. Each email must have a unique mail ID.
    • An outbound email to Office 365 is fetched back into the own tenant. In this case, the own Office 365 connector is the problem.

Office 365 operates on the principle that there are multiple access points for emails. If you configure a connector, it is transmitted to the systems responsible for your client.

If a communication partner receives emails via the same system as you, your connector (inbound) naturally also applies.

Please note that Office 365 has two types of connectors: Partner organisation to Office 365 and Organisation email server to Office 365. The crucial difference here is that the partner connector only becomes active if one of your own domains is specified as the email recipient. The connector Organisation email server to Office 365 takes effect when your domain appears as the sender and then retrieves the email back to your tenant.

From NoSpamProxy's point of view, the email is correctly delivered to the system specified in the MX. From Microsoft's side, however, the difference to the expected behaviour is that your client receives the email due to the previously mentioned connector instead of the actual recipient client and then wants to deliver it back to NoSpamProxy according to the rules. The email was then delivered from NoSpamProxy's point of view, but incorrectly classified in Office 365.

There are several solutions here. All of them aim to distinguish between emails from you and emails coming to you. You can achieve this either by re-creating the inbound connector in Office 365 (partner organisation to Office 365) or by switching to different TLS identities for inbound and outbound send connectors in NoSpamProxy.We recommend here not to transmit a TLS identity in the outbound send connector.

  • Put on hold Further actions are necessary for the email to be delivered successfully.
    • Content filter The email is stopped to process the attached files and then delivered with a second message track as a successful email. The action performed can be tracked in the Message Track on the Activities tab. You can track the successor of the email in the Message Track on the tab Relations.
    • PDF mail The outbound email is converted into a PDF document and encrypted because there is no S/MIME certificate for the recipient. The recipient must assign a password on the Web Portal; until then, the email remains in this status.
    • Service not reachable The Integrated Malware Scanner cannot reach files that are to be uploaded to the Web Portal.