Non-accepted domain report polluted with other entries

%3CLINGO-SUB%20id%3D%22lingo-sub-1073769%22%20slang%3D%22en-US%22%3ENon-accepted%20domain%20report%20polluted%20with%20other%20entries%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1073769%22%20slang%3D%22en-US%22%3E%3CP%3EUntil%20recently%2C%20the%20non-accepted%20domain%20report%20(available%20from%20the%20Mail%20Flow%20dashboard)%2C%20correctly%20reported%20only%20non-accepted%20domains.%26nbsp%3B%20For%20example%2C%20a%20misconfigured%20scanner%20trying%20to%20send%20from%20an%20email%20address%20that%20a%20copier%20engineer%20thought%20up%20on%20the%20fly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20it%20also%20appears%20to%20include%20non%20delivery%20reports%2C%20with%20a%20hop%20count%20exceeded%20message.%26nbsp%3B%20This%20appear%20to%20always%20be%20for%20when%20a%20user%20exists%20but%20does%20not%20have%20a%20mail%20box.%26nbsp%3B%20This%20is%20making%20the%20report%20much%20more%20difficult%20and%20time%20consuming%20to%20interpret%2C%20reducing%20its%20effectiveness.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Regular Contributor

Until recently, the non-accepted domain report (available from the Mail Flow dashboard), correctly reported only non-accepted domains.  For example, a misconfigured scanner trying to send from an email address that a copier engineer thought up on the fly.

 

Now it also appears to include non delivery reports, with a hop count exceeded message.  This appear to always be for when a user exists but does not have a mail box.  This is making the report much more difficult and time consuming to interpret, reducing its effectiveness.

0 Replies