Mike,
> One of SpamAssassins weaknesses is that it only has access to the
> message body of the email. It can't create rules to detect certain
> behaviours of the connecting host during delivery.
[...]
> I was thinking along the lines of an interface where the mta connects to
> SpamAssassin when a connection comes in, and it then sends the full smtp
> transaction to SpamAssassin as it happens.
> SpamAssassin would then be aware of various extra metrics, such as the
> examples I gave in my original email.
See:
Adding one optional arg to M::S::parse allows caller to pass
additional info to SA
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6088
It allows passing synthetic rule hits or other information from
a caller to SpamAssassin on its API, without having to insert
synthetic header fields into a message. Available in SA 3.3.
Mark
