<https://forum.spamcop.net/topic/1473-global-mailhosts-an-user-review-call-for-change/#comment-9329>
<http://schema.org/text>
"So was the header prior to the one \"incorrectly\" on your list a good enough forgery to send the report to an incorrect ISP? Did the parse simply fail because it did not know where this host received the message?  Did you report this failure to the duputies with enough supporting data to show the error?  That is one of the reasons for this beta test. \n\n \n\n\nYou could set up auto-reporting before just like now.  It is not and will not be 100% accurate.  You are still supposed to be checking that reports are going to the proper places, not just that they are not going to your ISP. Auto-reporting is still not going to be supported and will be discouraged at every step.  Quality over quantity has been a mantra around here for the last year or so.  If you don't have time to report, DON'T.  If you only have time for a few, do that, but do them correctly. \n\n \n\n\nIf you individually submitted and completed each email account in the correct order, receiving waivers when necessary, then your mailhost are configured correctly.  See example at the bottom if this is your question, I don't think so, however. \n\nI don't think your mailhosts are setup incorrectly.  I think you don't like the extra entries in the mailhost configs you are a part of.  This is where the lack of data comes in. \n\n \n\n\nIf the hostname domain is already listed, this does not seem to be necessary.  I have a domain A and 2 mail servers b.A and c.A.  c.A was not actively accepting outside messages (it is the backup) when I first configured mailhosts.  so only domain A and host b.A are listed.  I tried reconfiguring so c.A was accepting messages and resubmitting a mailhost but c.A was not added.  However, it does not affect the parsing as it sees the A domain and accepts it. \n\n \n\n\nThen you would be messing up someone elses mailhost configuration.  Again, as long as there is not a believable forgery prior to the incorrect mailhost on a spam message, it makes no difference. \n\n \n\n\nThe only way a false report would be sent is if there was a believable forgery directly prior to the incorrect entry. \n\nI still say, if you see email parsing through a host you don't think should be in your mailhost configuration, you should contact the deputies with the tracking URL and explain the problem.  I have not seen that yet. \n\nExample: \n\nYou have 1 account (a[at]A) that forwards to another account (b[at] that forwards to a third account (c[at]C).  To confuse things, the b[at]B account uses a \"complex configuration\" and will require a waiver. \n\nPer the directions, you register the c[at]C account first and the probe will go directly to that account.  Then register the b[at]B account and the probe will go to the b[at]B address and forward to c[at]C.  Follow the directions to request the waiver and wait to receive that.  Then you register the a[at]A account and the probe will follow your entire path.  Your mailhost configuration is complete and correct. \n"
<https://forum.spamcop.net/topic/1473-global-mailhosts-an-user-review-call-for-change/>