Hi,
ok, so what might actually be in that line 3 of the input I have
zero idea, thats something being communicated from spamassassin to
exim from what I understand which I also guess is transient info so I
dont know how Id go about seeing that...
The sections relevant to bsmtp in my exim config are:
spamcheck:
verify = false
condition = \
${if !or{ \
{eq{$received_protocol}{asmtp}} \
{eq{$received_protocol}{spam-scanned}} \
} {yes} {no}}
driver = accept
transport = spamcheck_pipe
headers_remove =
X-Spam-Checker-Version:X-Spam-Score:X-Spam-Report:X-Spam-Level:X-Spam-Status:X-Spam-Flag:
.......
begin transports
## Handoff to the SPAM scanner, which will then resubmit.
spamcheck_pipe:
driver = pipe
command = "/usr/local/sbin/exim -oMr spam-scanned -bS"
use_bsmtp = true
transport_filter = "/usr/local/bin/spamc -u mailnull"
user = mailnull
group = mail
home_directory = "/var/spool/exim/scan"
current_directory = "/var/spool/exim/scan"
log_output = true
return_fail_output = true
return_path_add = false
message_prefix =
message_suffix =
Im quite happy to provide whatever info may be useful to someone more
knowledgeable on exim than myself, I might need some help to know what
that info would be as Im pretty stumped on how to trouble shoot this.
Perhaps I have an outdated method of integrating spamassassin with
exim? This is a config I inherited and its been unchanged for many
years, although its a config that has worked without this error for
many years too. Is there a better way to configure spamassassin than
this now? I did google this but I couldnt work out which of the
various methods, if any, was the current recommended method.
thanks Andy.
Quoting Ted Cooper:
> If you want someone with more a clue to respond to your query,
> you're going to have to provide something a bit more than an obscure
> error message and no other information.
