Firetrust Support Forums

There was a subtle change in 2.8, not enough to create a new version - the difference was less than a day.

2.8 = First release
2.8.0.0 = Current release.

Hi Ton, Sorry - I missed your response. Firstly, can you upgrade to the latest version of MWES - you're a version behind. The upgrade process is installable over-the-top, and a simple restart of the MWES service. (doesnt hurt to stop the service initially as well) Secondly, it looks like the spammer...

Hi Ton,

Depending on your mail client, the view source may show different aspects.

If you are using Outlook, Right click on the message and select "Message options" to view the headers.

Hi Ton, Sincere apologies on the delay in responding, I havent seen your post untill now. Every time a message is passed through MWES, it is tagged with the reason why is was passed, or blocked. Look at the headers of the email (View Source in Outlook) and look for the header starting with: X-MWES-{...

Hi Nick, use_replay=0 will need to be added to the registry if it doesn't exist Sounds like something is awry though. Is it possible to get access to the cluster (just need access to the front end) to take a look? - email me on cliff@firetrust.com with the credentials if you will allow me to do so. ...

Hi Nik, MWES is fully compatible with an Exchange 2007/2010 cluster (Front end with Mail stores behind) - we installed it without issue on a cluster just last month in fact. There are a couple of caveats however: * The current/latest version of MWES needs to be installed (it has specifics to handle ...

Hi There, A trusted IP allows mail sent from the specified IP to pass through without the need to authenticate - it's often called a 'relay client'. In Linux installations, no more needs to be done, as MWES will be trusted by the MTA. In Exchange installations, you may need to adjust the exchange re...

No problem - glad it was a nice easy fix

~ C

Hi there, The error message shows that another spam filter is blocking the message from getting through - in the this case, Exchange Content filtering. It is recomended to disable ALL other filtering, with exception to Recipient filtering, as it prevents mail destined for unknown/non exitant users f...

Hi there,

If you mouse-over the error message, it will display the reason for the error. Let us know what that error is

~ C

Hi there, The stats are updated when a mail message is sent through - this is to save CPU (oposed to having a constantly ticking thread to check times etc). When your next message is received, it will do a cycle on the statistics, and the columns will be populated. it just happens you are catching i...

Hi There, We have not tested placeing MWES on a front server, but I don't see any issues with it working. MWES acts as a proxy, (opposed to a plugin/milter), the only thing MWES needs is communication to an SMTP server. As long as it has full SMTP communication, including user verification etc, it w...

The MTA hostname should be the IP/DNS that MWES connects to. If you are receiving mail through MWES, then this is set correctly.

I'll get in touch via email

~ C

Hi there, Some settings to check for the Digest: * You have Digest Report checked (System > Configuration) * Each user has a primary email address entered into the User Settings (Settings > User) - this must be receivable by the connected MTA * Each user has an appropriate value entered into the Use...

Hi there,

Just to clarify, you are wanting to configure a recipient address or domain, hosted on your MTA, which will not be filtered my MWES?

It sounds like something we can add in. I'll have a chat to the developer when he gets back from holiday (2 weeks) and let you know

~ C