Pruning "Trash" and "Spam" folders automatically on MDaemon

The accountpruner is a powerful tool, but it’s not always the easiest thing to use. With that in mind, here are some rules from my \MDaemon\App\midnight.bat file that might be useful. This batch file is executed by MDaemon at midnight each night. (If you haven't this file, you can create it and it works).

c:\MDaemon\App\AccountPrune.exe /m /d=10 /p=”Spam.IMAP”
c:\MDaemon\App\AccountPrune.exe /m /d=10 /p=”Junk Mail.IMAP”
c:\MDaemon\App\AccountPrune.exe /m /d=10 /p=”Junk E-mail.IMAP”
c:\MDaemon\App\AccountPrune.exe /m /d=2 /p=”Trash.IMAP”
c:\MDaemon\App\AccountPrune.exe /m /d=2 /p=”Deleted Items.IMAP”
c:\MDaemon\App\AccountPrune.exe /m /d=2 /p=”Deleted Messages.IMAP”

Obviously, if you have installed MDaemon server in an another path, just use it.

The result is that at midnight each night, MDaemon’s accountpruner will go through each user’s mailbox, and in each of the “Spam”, “Junk Mail” and “Junk E-Mail” folders, delete all messages over 10 days old.

In the “Trash”, “Deleted Items” and “Deleted Messages” folders, messages over 2 days old will be deleted. Combine this with the accountpruner’s own options to delete IMAP mail flagged as deleted, and you’ll have a solution that works for users of all mail clients, whether the mail client uses a dedicated “Trash” folder, uses IMAP deleted flag, or both.

VmWare ESX with Windows based NAS (NTFS)

Above there is the complete procedure to use a Windows Based NAS NTFS share as NFS for VMware ESX server.

The main steps in this process are:

1. Installing Windows Services for UNIX (WSFU)


2. Copying the ESX Server password and group files to Windows


3. Configuring WSFU for accepting ESX Server connections


4. Sharing the Windows folder for NFS compatibility


5. Configuring the ESX Server to mount the Window NFS Share as Datastore.

1. Installing Windows Services for UNIX (WSFU)

Download windows services for UNIX at:
http://www.microsoft.com/windowsserversystem/sfu/downloads/default.mspx

Install WSFU on the desired machine
Add in the following options
NFS + Server for NFS
Authentication tools for NFS + user name mapping
After installation, open services control panel applet and change the service ‘User Name Mapping’ to startup automatically and then start the service (if it's not started)


2. Copy the ESX Server password and group files to Windows

Use a program like WinSCP or similar process to copy the following files to your local system where WSFU is installed
You can get WinSCP from the fowling location.
http://winscp.net/eng/download.php#download2
Transfer the file /ect/password and the file /ect/group to C:\SFU or to the location where you installed WSFU


3. Configure WSFU to accepting ESX Server connections

Click Start, Programs, Windows Services for UNIX, Services for UNIX Administration
Go to user name mappings then configuration
Click password and group files
Then browse for the password and group files that you copied, from the browse dialog box for both the password and group fields
Click apply
Then go to maps
Click Show User Maps
List Windows users and list Unix users
Then select a local administrator user on the left that will be mapped to the root account and the root user on the right.
Then click on Add button
Then click apply (upper right)



4. Sharing the Windows folder for NFS compatibility

Right click the local folder you wish to share via NFS
Share the folder by clicking NFS sharing
Type in the name for the share i.e. NFS-VMFS01
Remove allow anonymous access
Click permissions
Now Change type of access to “Read+Write” then check allow root access.


5. Configure the ESX Server to mount the Window NFS Share as VMFS

Open the VC client and highlight the Vi3 host
In the Configure tab choose Networking
Add networking, VMKernel then pick a vSwitch, then give the VMkernel an IP that is accessible via the NFS host.
Now open the storage option for this host
Click add storage, > Network File System
In the Server Field enter in the name or the ip address of your server
In the Folder field enter /NFS-VMFS01 (or the name you give to the share)
For the Datastore I also used NFS-VMFS01

Add users to Team Foundation Server

All Team Foundation Server editions require users to be members of a Team Foundation Server group at the project level or server level. The level and group depend on the functionality that you want to enable for the user. For example, if you want to have a user create a team project, the user must have the Create New Projects permission set to Allow, must be assigned to the role of Content Manager in SQL Server Reporting Services, and must be assigned to the role of Administrator for Windows SharePoint Services. However, the user does not have to be a member of the local administrator group on the computer. For more information about users and roles, see the topic “Team Foundation Server Permissions” in the Team Foundation Server Administrator’s Guide on MSDN Library.

To add users to Team Foundation Server:

1. Log on as a Team Foundation Administrator, open Team Explorer, and connect to the Team Foundation Server for which you are adding a user.


2. From the Team menu, click Team Foundation Server Settings, and then click Group Membership.


3. In the Global Groups dialog box, click Team Foundation Licensed Users and then click Properties.


4. In the Team Foundation Server Group properties dialog box, click Windows User or Group, and then click Add.


5. In the Select Users or Groups dialog box, type the user accounts you want to add, and then click Add.


6. Click Close.

Note
You cannot use the Global Security group dialog box to add users to this group.
You can add individual user accounts but not a group account.

In this way the user can only connect to the server but can't create or access projects. To complete the configuration, you can use the TFS Admin Tool. It allows a TFS administrator to quickly add users to all three platforms utilized by Team Foundation Server (Team Foundation Server, Sharepoint and SQL Reporting Services) all through one common interface. The tool also allows administrators to change the current permissions on any of the three tiers, identify any errors and view all of the users and their permission sets across Team Foundation Server, Sharepoint, and SQL Reporting Services.

The program is written in C# and is released via CodePlex.

Asterisk / Trixbox: listen to calls in progress

With Asterisk or Trixbox it's possible to listen to calls in progress made by other clients.

Insert the line below into "extensions.conf" inside a customized context. In Trixbox or @home write it into "extensions_custom.conf "under [from-internal-custom]

for example:

exten => _61XXX,1,ChanSpy(SIP/${EXTEN:2},q)

with as many X as number of figures or chars in "names" of your extensions (3 in this exemple)

After a reload, is sufficent to type on telephon keypad 61206 to listen the extension 206 call

Asterisk / Trixbox: recording calls

With Asterisk or Trixbox its possible to record clients made calls.
To do it we have to insert the rows below into "extesion.conf" on Asterisk or into "exstension_custom.conf" on Trixbox. (PS: on Trixbox it's also possible to enable this function from the GUI)

exten => _61XXX,1,Monitor(wav,rec${EXTEN:2},m)
exten => _61XXX,2,ChanSpy(SIP/${EXTEN:2},q)
exten => _61XXX,3,Hangup

in /var/spool/asterisk/monitor we'll find the recordings in wav format, named rec"extensionNumber"