https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8041
--- Comment #6 from Sidney Markowitz <sid...@sidney.com> --- I noticed that our dcc test actually does report a test spam message to dcc and then checks that it is found. And dcc doesn't itself recognize the GTUBE string, so the dcc test just uses test spam that happen to be GTUBE test messages and lets dcc process the report and check as it does with any other message. The same approach will work for pyzor testing without having to worry about finding real spam on the server, and without relying on infrastructure outside of the test itself. Compared to all the wild spam being reported to the pyzor server, people running the SpamAssassin tests with network tests enabled reporting one small unique test message won't be a noticeable load on their server. Since the pyzor digest algorithm ignores lines with no whitespace, I have modified t/data/spam/pyzor to be a gtube test email with the addition of some text that does have whitespace in it. I also added a step to the test to report the spam message before checking it, like dcc.t does, which makes the test now self-contained with no worry about pyzor recognizing GTUBE or about its server expiring our test spam. I'll decommission my personal GitHub action cron reporting of the original t/data/pyzor as no longer necessary. trunk % svn ci -m "Bug 8041 - Add a report step to pyzor test and use a GTUBE test case with lines that pyzor uses in digest" t/data/spam/pyzor t/pyzor.t Sending t/data/spam/pyzor Sending t/pyzor.t Transmitting file data ..done Committing transaction... Committed revision 1906589. -- You are receiving this mail because: You are the assignee for the bug.
