MWES problem after UG from 3.0.0.14 to 3.0.0.17

Well, it's up and running, but I'm not sure if it's doing what it should.
techcareict
Rattled Rabbit
Posts: 3
Joined: Mon Aug 14, 2017 9:30 pm

MWES problem after UG from 3.0.0.14 to 3.0.0.17

Postby techcareict Mon Aug 14, 2017 9:48 pm

Hi,
I have upgraded from 3.0.0.14 to 3.0.0.17 at three sites and all appear to have the same issue.
mail does not appear to be getting filtered and if I hover the mouse over the DELIVERED on a mail item in the STATUS column in the all emails list the popup info is preceded by 'Invalid Licence:'

When i look at 'Settings\Licence' it shows the following (I have replaced private data with **********)

Company: *************
Contact name: ***********
Email: *************
Product ID: (3) - Unknown
Subscription quantity: 9999
Subscription expires: 2018-06-19

clicking on UPDATE LICENCE returns a successful message but the above info remains the same with Product ID showing UNKNOWN.

any advice much appreciated.
User avatar
nick.bolton
The Big Cheese
Posts: 1625
Joined: Thu Aug 28, 2008 4:02 pm

Re: MWES problem after UG from 3.0.0.14 to 3.0.0.17

Postby nick.bolton Tue Aug 15, 2017 6:02 am

Hi

Do you have the following in the Windows Registry or Linux mwes.conf file?

Windows: Open the Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Firetrust Limited\mwes a registry key 'mwes_original'? If you do, can you delete it. If not, then right click, select New>>String Value, and type 'mwes_original', then double click and give it the value 17.

Linux: in \etc open the mwes.conf and look for and remove, or add mwes_original=17

Restart the MailWasher Enterprise Server Service/Daemon to implement this change.
techcareict
Rattled Rabbit
Posts: 3
Joined: Mon Aug 14, 2017 9:30 pm

Re: MWES problem after UG from 3.0.0.14 to 3.0.0.17

Postby techcareict Tue Aug 15, 2017 6:33 am

Hi Nick,
yes its in the reg with the value 17
although its server 2003 so no Wow6432Node, its at HKLM\SOFTWARE\Firetrust Limited\mwes

the others with the problem are also 2003 incidentally ....
techcareict
Rattled Rabbit
Posts: 3
Joined: Mon Aug 14, 2017 9:30 pm

Re: MWES problem after UG from 3.0.0.14 to 3.0.0.17

Postby techcareict Tue Aug 22, 2017 3:25 am

I seem to be not receiving certain emails too, they are shown in MWES as delivered and then sit in a queue for local delivery in exchange for no apparent reason?

Spam is definitely not being blocked, below is part of the header of a spam email I received today showing reason for bypassing MWES as Licence invalid! (I have ***** any sensitive info)

To: <mark@*********.uk>
Content-Type: multipart/mixed;
boundary="3511aeb1694e8bceae054f57bc6d"
X-MWES-scanned: Checked by MailWasher Enterprise Server 3.0.0.17 {W}(2017-08-21 13:30:05)
X-MWES-status: Clean
X-MWES-reason: Invalid License
X-MWES-sourceip: 60.249.45.66
X-MWES-smtp-from: <leanne5555@*********.uk>
Return-Path: <Leanne5555@*********.uk>
X-OriginalArrivalTime: 21 Aug 2017 12:30:05.0033 (UTC)


HELP Please...........
User avatar
nick.bolton
The Big Cheese
Posts: 1625
Joined: Thu Aug 28, 2008 4:02 pm

Re: MWES problem after UG from 3.0.0.14 to 3.0.0.17

Postby nick.bolton Tue Aug 22, 2017 7:47 am

Ok, on the machine with the 'Invalid License' can you remove the registry entry mwes_original=17 and restart the service and see if that fixes it?

Return to “Post Installation”

Who is online

Users browsing this forum: No registered users and 1 guest