Daryl C. W. O'Shea wrote:
René Berber wrote:
Matthew Dickinson wrote:
When sending messages from clients using SMTP Auth to a server
running sendmail, I'm seeing issues with SPF and Botnet thinking
these messages are spam-like - I'm not sure if this issue lays with
SA or with sendmail itself.
The issue is with SA, sendmail is an innocent bystander.
There's no evidence of that. In fact there's evidence of the contrary.
Since the X-Spam header fields were appended to the bottom of the
header they were added by a milter and not SA. It's quite likely that
they were added by a milter like spamass-milter that isn't providing SA
with the auth info it needs to extend trust accordingly.
Looks more like MailScanner to me, not a milter, notice the virus scan... and MS
does include the full received headers. But your point is valid, that could be
the cause of the problem in some cases.
SA: do you have trusted_networks set correctly?
In the case of auth'd connections from unknown in advance IPs it's up to
whatever passes the message to SpamAssassin to provide the appropriate
auth info. trusted_networks only needs to be configured to include the
server that the auth'd user/device/whatever connects to.
Correct, my observation was ambiguous, I meant that the server should be
included in the trusted_networks, not the client.
--
René Berber
