[ESET Mail Security with greylisting on - my Exchange transaction logs are out of control]

Hi,

 

Using EMSX v 6.3.10007.0 with Greylisting enabled with Exchange 2010 SP3 (SBS2011). Enabling Greylisting has cut down our spam by a massive amount.

 

However, my Exchange server's transaction logs are now out of control and consuming disk space to the point where my mailstore disk is full and external email is no longer delivered. I'm now having to truncate the logs three of four times a day to ensure that mail flow isn't affected.

 

The issue is definitely all down to the Greylisting - if it's disabled the logs stay more or less at a constant size, all nicely behaving.

 

Is there anything that can be configured in EMSX to reduce the size and amount of transaction log files?

 

I'm loathed to remove the Greylisting as it's doing a great job with our spam, but if that's what's needed, then so be it.

 

 

 

[MS Outlook protection on a Remote Desktop Server?]

Thanks.

 

EFSW 6.3 fixed the issue.

[MS Outlook protection on a Remote Desktop Server?]

Apologies if this has been asked before.

 

I'm running a Windows Server 2012 R2 with RDS, and for as long as it's been up and running, I've had ESET File Security installed, it being a server.

 

However, I'm not sure how to integrate ESET FS with Outlook. There's certainly on option for it in the File Security settings (Setup > Advanced Setup > Web and Email > Email client protection), but no add-in appears to be available in Outlook. I'm sure it should be there - the user documentation for FS v6 is full of references to Outlook and e-mail client integration.

 

Is this something that can be forcibly installed or pushed to the RDS clients?

 

I'm using MS Outlook 2016 (16.0.6001.1078) and ESET FS 6.2.12007.0.

 

 

 

Cheers

 

 

 

Neil

[era_mdm_db_log.LDF is out of control!]

A couple of days in and everything seems to have settled down.

 

I'd disabled Auto Shrink (I understand it's bad practice to leave this enabled) and left the auto grow disabled. The LDF is now only 3MB.

[era_mdm_db_log.LDF is out of control!]

Thanks.

 

I've done that and registered one Android device with it.

 

18 hours in and the new MDF is just shy of 5MB, but the LDF is approaching 1GB in size. It's not looking good.

 

What I have noticed is the Recovery model for the database is set to Full and Auto Shrink is set to False. I've changed the recovery model to 'simple', enabled auto-shrink and disabled autogrowth to see if taht can keep the file size to a more manageable level.

 

 

 

Neil

[era_mdm_db_log.LDF is out of control!]

Hi,

 

The backup is scheduled daily, using the Backup Database Task from the SQL Management Studio. I've no reason to believe it isn't working (the schedule backs up a few other SQL databases at the same time and they're all OK).

 

As suggested, I've run a manual backup from the SQL Management Studio, then attempted to shrink the Database (not Files), and the allocated space is now 75,686.56MB! Yikes !

 

 

Is there a way to completely remove the MDM settings/database and start over?

 

 

 

Cheers

 

 

 

Neil

[era_mdm_db_log.LDF is out of control!]

Hi,

 

My SQL server alerted me this morning that it was running low on disk space. It turns out that one of the, what I thought insignificant, databases (the era_mdm_db_log file) was eating away at my disk.

 

era_mdm_db.mdf - 9MB

era_mdm_db_log.ldf - 71GB     

 

I only have one mobile device registered with my ERA!

 

What the hell!?

 

I can't shrink it - there is only 0.24MB of space available.

 

Can this file be deleted and recreated, then size-limited before it kills my SQL server?

 

 

Cheers

 

 

 

Neil