If you’ve been using SpamAssassin and have been reporting to SpamCop then you’ll have found overnight that you got a heap of bounces back saying things like:
<devnull@prod-sc-app7.sv4.ironport.com> (expanded from <spamassassin-submit@spam.spamcop.net>): unknown user: "devnull"
It turns out that the spamassassin-submit@spam.spamcop.net appears to be something that the SpamAssassin developers set without consulting with SpamCop, and SpamCop have just been blackholing those reports for an unknown amount of time. Last night it went away and so now IronPort are rejecting them which was how I learnt of this. I’m not impressed by what the SA developers did her, it should have required you to put in a registered SpamCop address and not reported if that wasn’t set.
I’ve disabled my SpamCop reporting by commenting out this line in /etc/mail/spamassassin/v310.pre
on my Debian mailserver:
loadplugin Mail::SpamAssassin::Plugin::SpamCop
If you use SpamAssassin and don’t have a registered SpamCop account you’ll want to do the same.
Cool, thanks. I figured that it was something like this, but I didn’t realize that the developers had wedged it up. I had a script using my registered address but was still getting these from the plugin.
Glad it helped. It’s quite disappointing that the SA devs had done that but at least the issue is fairly easily fixed once you know what’s going on.