rspamd starts checking and flagging outbound mails

Hi there,

since the last release, rspamd started scanning outbound emails for spam, independent of whether they were actually sent or whether they are forwarded with a Sieve script. Those mails can then get delayed if they look fishy enough. Especially since the last "hop" through the local node was unencrypted, and a sieve forward could be interpreted as forged sender or recipients.

Commit 630b5c4f introduced a change that uses rspamd for dkim signing. Maybe this change could have caused this behaviour?

A good workaround would be to not scan mails that are originating from 127.0.0.1