Re: [Assp-test] fixes in assp 2.6.6 *SPAM-Evaporator* build 21302

2021-10-30 Thread K Post
I've spent the better part of 2 hours trying to figure out what's going on. First, please note that for me, both 21293 and 21302 appear to record the .msg file in errors-spam/errors-notspam correctly. The .msg is getting extracted from the report properly. If I do an analyze from the GUI on

Re: [Assp-test] fixes in assp 2.6.6 *SPAM-Evaporator* build 21302

2021-10-30 Thread Thomas Eckardt
>found a possible MIME header start in the middle of the mail - the analyze may be wrong [CR][LF] • Subject: FW: test of report message[CR][LF] Is there any one else on this mailing list, who expects an email received by assp to start with an empty line followed by (html code) or that the

Re: [Assp-test] fixes in assp 2.6.6 *SPAM-Evaporator* build 21302

2021-10-30 Thread K Post
sorry, I sent the last message before proofing or finishing. Grr, gmail. I'll wait to hear from you. I have more thoughts on NWLI and other sections. On Fri, Oct 29, 2021 at 6:00 PM K Post wrote: > This is simply terrific. You keep making ASAP better! The rebuild config > efficiency

Re: [Assp-test] fixes in assp 2.6.6 *SPAM-Evaporator* build 21302

2021-10-30 Thread K Post
>> Is there any one else on this mailing list, who expects an email received by assp to start with an empty line followed by (html code) or that the first header line of such a mail is the subject header line ? That doesn't happen when I send the exact same report with 21293. It does with 21302