Just as a side note, I was checking out: https://github.com/ovh/cerberus-ux I don’t think it will work for us, but it’s main purpose is to delegate spam reports into categories. As a customer, I can say they kick ass, for this contribution for us, meh… But it’s worth checking out at least.
P.S. It seems like nosignal.org’s cert on let’s encrypt still hasn’t updated yet. > On Jun 28, 2016, at 7:14 PM, Steve Atkins <st...@blighty.com> wrote: > > >> On Jun 28, 2016, at 3:57 PM, Hal Murray <hmur...@megapathdsl.net> wrote: >> >> >>> There is currently no way to deliver spam to abuse@<google hosted domain> >> >> Google isn't the only problem. There are lots of outfits that do content >> filtering on their abuse mailbox. >> >> It seem reasonable to reject mail from IP Addresses on black lists, but >> rejecting spam reports because they look like spam seems silly. What did >> you >> expect them to look like? >> >> Is that mentioned in any BCP? Do any spam-filtering examples process abuse@ >> correctly? >> >> How much actual spam arrives at abuse@ after filtering on source address? > > It can be a lot. It's not too difficult to distinguish from abuse reports for > a decent ticketing > system or for custom filters, but it is difficult for typical email content > filters to distinguish > the two streams. > > (It's particularly hard to distinguish between spam directly to abuse@ and > badly > written or misdirected spam reports. Fortunately you take the same action on > both). > > Cheers, > Steve > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
