On 8/18/2016 2:15 PM, Bowie Bailey wrote:
On 8/18/2016 3:05 PM, Jerry Malcolm wrote:
On 8/18/2016 1:45 PM, Bowie Bailey wrote:
On 8/18/2016 2:21 PM, li...@rhsoft.net wrote:
Am 18.08.2016 um 20:18 schrieb Jerry Malcolm:
This is the X-Spam-Status header I got back on an uncaught spam. No,
hits=0.3 required=5.0. The spam was selling an all-in-one charger
we need the *report* header
By default, the report header is only added to messages marked as
spam. To add it to all messages, add this line to your local.cf file:
add_header all Report _REPORT_
On a linux box, this would be in /etc/mail/spamassassin. I have no
idea where it would be on your "SpamAssassin In a Box". Once you
find and update the file, you will need to restart whatever
SpamAssassin or Spamd service is running on your system to have it
re-load the configuration.
I see the local.cf file, it is already configured with 'all
report'. But I looked at a msg that was flagged a spam. It doesn't
have a report header either. I guess it's possible that the JAMES
invoker mailet is stripping the headers. But I don't see any obvious
code that appears to be removing headers. Are there any other
options that might be controlling whether SA adds that header?
Why don't you put your local.cf file on pastebin so we can see how it
is set up?
I doubt anyone here is going to know anything about the JAMES mailer.
I'm still trying to see why I'm not getting the report back. I've gone
all the way back to the source code that does the streaming of the spamd
invocation on port 783. I can't seem to find the documentation
anywhere on the format of the data I should read back on port 783 from
spamd. It looks like I'm getting two text lines back on the read:
SPAMD/1.1 0 EX_OK
Spam: True ; 7.7 / 5.0
followed by a blank line and then a null. I believe I read in the
spamd doc that it should return the entire message back, apparently
modified with headers that you add. I'm not seeing it. I looked
through all of the options for spamd and didn't see anything obvious
that says whether to send the message back or not. Currently, my MTA
code just parses the two lines above and adds headers based on that info
to the original message. But if you are adding additional headers such
as reports, etc., I'm not seeing the modified message coming back to
me. What am I missing? Can you point me to a link to documentation on
the in/out data flows over port 783 to spamd?
The following info is written to the socket followed by the message itself:
CHECK SPAMC/1.2\r\n\r\n
This is the Windows Service entry for spamd:
SpamAssassin deamon. Starting parameters:
--allow-tell --syslog="spamdLog.txt" --max-spare=2 --max-children=20
--timeout-child=85
