Delete pop email after so many days

You may get your email from multiple sources to cater for failures or just handy to have access while on the road. For example retrieve email from your ISP from both a home mail server and your Gmail. In this case your want to instruct both your home mail server and Gmail to not delete email from the ISP’s pop mail server, the problem is neither Gmail or my home server will provide a setting of delete the pop mail after so many days and my pop mailboxes fill up over time.

Using a simple one line script and adding it to a cronjob does the job of deleting this old mail still sitting up on the ISP.

CAUTION: The script will delete mail, test it first with a different command or on a test mailbox that does not matter to you.
The script:

find [email protected]_com/cur/* -mtime +30 -exec rm -rf {} ;

The above script will delete all mail in the users mailbox that is 30 days or older.
If you have an account such as spam where all mail that is meant to be spam is sent to the spam mailbox, you can setup a script to just delete all new mail after 30 days like so:

find [email protected]_com/new/* -mtime +30 -exec rm -rf {} ;

Disable IPV6 Windows 7/Server2008

Until IPv6 is really required you may want to totally disable it from your network, to do this in Windows 7 and Ws2008 you need to do more than just un-tick the check box in the properties of the protocol section.


Using regeditor (regedit.exe) to modify some registry entries:

  1. Click Start and type regedit in the Start Search box, and then click regedit.exe in the Programs list.
  2. In the User Account Control dialog box, click Continue.
  3. In Registry Editor, locate and then click the following registry subkey:
  4. Double-click DisabledComponents to modify the DisabledComponents entry.Note If the DisabledComponentsentry is unavailable, you must create it. To do this, follow these steps:
    1. In the Edit menu, point to New, and then click DWORD (32-bit) Value.
    2. Type DisabledComponents, and then press ENTER.
    3. Double-click DisabledComponents.
  5. Type any one of the following values to configure the IPv6 protocol, and then click OK:
    1. Type 0 to enable all IPv6 components.Note The value “0” is the default setting.
    2. Type 0xffffffff to disable all IPv6 components, except the IPv6 loopback interface. This value also configures Windows Vista to use Internet Protocol version 4 (IPv4) instead of IPv6 in prefix policies.
    3. Type 0x20 to use IPv4 instead of IPv6 in prefix policies.
    4. Type 0x10 to disable native IPv6 interfaces.
    5. Type 0x01 to disable all tunnel IPv6 interfaces.
    6. Type 0x11 to disable all IPv6 interfaces except for the IPv6 loopback interface.

tcpspy utility for Linux

tcpspy is a Linux utility that can monitor inbound and outbound network connections and is probably best suited for small or home networks. While the tool is fairly old it works great and can be very effective. The alternative is to use a network monitoring system together with an IDS system such as Ossim and Ossec, but this can be an overkill for a small network, so tcpspy will fit nicely under those requirements.

Good article here and to install it use your distro’s package manager e.g. aptitiude install tcpspy

Application Layer DDoS simulator

DDoSIM is a tool that can be used in a laboratory environment to simulate a distributed denial of service (DDOS) attack against a target server. The test will show the capacity of the server to handle application specific DDOS attacks. ddosim simulates several zombie hosts (having random IP addresses) which create full TCP connections to the target server. After completing the connection, ddosim starts the conversation with the listening application (e.g. HTTP server).

More details and download at:

Top 5 new vCLI commands in vSphere

VMWare have added a number of new interesting and useful capabilities to the vCLI.  The Top Five New vCLI Commands in vSphere 4.1.:

  1. NFS statistics in resxtop
  2. AD configuration with vicfg-authconfig
  3. Host Operations with vicfg-hostops
  4. Network information with esxcli network
  5. Kill unresponsive VMs with esxcli vms

Further details about these at the ESXi blog