Here is a list of reasons on why a message may end up in this queue.
-
A syntactically incorrect RAW message.
-
An incoming message is from an address on the suppression list.
-
An incoming message to a list is from an address on the list's suppression list.
-
A message was found to be in a forwarding mail loop.
-
A message is destined to an unknown local user.
-
A message to a list that encounters an error during exploding.
-
A message to a list that exceeds the max size allowed by the list.
-
A message explicitly addressed to ''BadMsgQ@domain.com''.
-
A duplicate message determined to have already been sent to a list.
-
A message which fails to be parsed properly.
-
A message in the localq is addressed to an account which is not a local account.
Additional Comments
MDaemon 9.64 added a feature in which messages moved to the Bad Message Queue will have a header inserted called X-MDBadQueue-Reason. The header is added to the message itself and will also be logged in the Routing log. Messages moved by the Content Filter will not include this header.