Hi everyone,I am setting up a separate thread as I did not receive any specific reply in other threads.
The case concerns Sophos Anti-Spam Interface after upgrading from v18.5MR2 to v18.5MR3 and from v19EAP1 to v19EAP2.
Before updating, antispam works great in legacy mode, detects a lot of intrusive messages and tags with a prefix (near 99%). After updating, only some messages are detected as spam and tagged (I did not do any changes in configuration).
What it comes from? How can I edit my lists to achieve pre-update spam detection?
Greetings
Just to update this thread, RE: NC-90702, development will include a fix in SFOS 18.5 MR4 and 19.0 MR1.
I am curious.
Are only Home Users seeing this issue? Because it looks like, only Home Appliance are affected by this potential issue. Or does somebody with a Appliance (SG/XG/XGS) have the same issue?
__________________________________________________________________________________________________________________
Helo,
i have a Virtuell Home Appliance and at Work a brand new 116 XGS. And Yes i have the same Problems with spam.
So i rollback on both Appliance to 18.5MR2 380 and all Works fine.
Hi,
screenshots from the sasi.log this morning on my XG115W
What the XG pattern update shows.
Ian
XG115W - v19 GA - Home
1225v5 6gb ram, SSID, 4 NICs 20w - v19 EAP - on holiday.
If a post solves your question please use the 'Verify Answer' button.
I am a Home User, setup SFOS in MTA mode.I do not experience more spam coming through then before the upgrade to 18.5 MR3.
Behind the XG is a mailserver with a second line of spam defence, that doesn't show an increase in activity either.
Same here, but what I noticed is I don't get any confirmed spam in quarantine anymore, and probable spam is not tagged with [SPAM]. Seems those mails are not processed by spam engine and go straight through to my mail server.What works is the RDNS and RBL checks.
Hi LuCar Toni,
I've got a few customers upgraded to MR3, one off them has this problem and so am I with my LAB/Home version. Customer is xg210 with paid license. The thing that's the same is we both do IPv6 on the in and outside.
Opened case Nr: 05143473
Bart.
Bart van der Horst
Sophos XG v18(.5) / v19 Certified Architecthttps://www.bpaz.nl
Ok it seems its now working for me. It seems Antispam service was not running properly. Monitoring was not complaining and under "System Services" it was shown as "Running". I tried to stop it, but I got an error.
The solution: Restarted my firewall, and turned off and on the Antispam function in my SMTP policy. Since then spam is properly sent to quarantine or tagged with [SPAM] again.
I confirm this solution. It's a temporary solution, but it works. Stop SPAM rule, stop SASI service, start SASI and start SPAM rule. Working sice yesterday. E-mails are tagged properly. It works also in v19EAP2.
And unfortunately stops working :/
For me its still working, I can see I get all X-SASI headers in the incoming emails. Maybe you need to restart the firewall as I did.
This issue has been assigned Development Reference ID NC-90702 and we will keep this post updated as we get more information.
Best,