Dopo circa 8 mesi di ricerca e troubleshooting sono riuscito a risolvere l’errore che mi dava WordPress in fase di creazione e visualizzazione dei post: “Invalid Post Type”.

Tutto dipendeva da una impostazione del server web: “PHP execution mode” era impostato su CGI wrapper. Ho modificato il parametro impostandolo a FCGid “et voilà” tutto ha ripreso a funzionare regolarmente…

PHP script execution mode


31 luglio 2009 (ultimo venerdì di luglio)

10° Anniversario

System Administrator Appreciation Day

sysadmin unpacked the server for this website from its box, installed an operating system, patched it for security, made sure the power and air conditioning was working in the server room, monitored it for stability, set up the software, and kept backups in case anything went wrong. All to serve this webpage.

sysadmin installed the routers, laid the cables, configured the networks, set up the firewalls, and watched and guided the traffic for each hop of the network that runs over copper, fiber optic glass, and even the air itself to bring the Internet to your computer. All to make sure the webpage found its way from the server to your computer.

sysadmin makes sure your network connection is safe, secure, open, and working. A sysadmin makes sure your computer is working in a healthy way on a healthy network. A sysadmin takes backups to guard against disaster both human and otherwise, holds the gates against security threats and crackers, and keeps the printers going no matter how many copies of the tax code someone from Accounting prints out.

sysadmin worries about spam, viruses, spyware, but also power outages, fires and floods.

When the email server goes down at 2 AM on a Sunday, your sysadmin is paged, wakes up, and goes to work.

sysadmin is a professional, who plans, worries, hacks, fixes, pushes, advocates, protects and creates good computer networks, to get you your data, to help you do work — to bring the potential of computing ever closer to reality.

So if you can read this, thank your sysadmin — and know he or she is only one of dozens or possibly hundreds whose work brings you the email from your aunt on the West Coast, the instant message from your son at college, the free phone call from the friend in Australia, and this webpage.

Show your appreciation

Friday, July 31, 2009, is the 10th annual System Administrator Appreciation Day. On this special international day, give your System Administrator something that shows that you truly appreciate their hard work and dedication. (All day Friday, 24 hours, your local timezone).

Let’s face it, System Administrators get no respect 364 days a year. This is the day that all fellow System Administrators across the globe, will be showered with expensive sports cars and large piles of cash in appreciation of their diligent work. But seriously, we are asking for a nice token gift and some public acknowledgement. It’s the least you could do.

Consider all the daunting tasks and long hours (weekends too.) Let’s be honest, sometimes we don’t know our System Administrators as well as they know us. Remember this is one day to recognize your System Administrator for their workplace contributions and to promote professional excellence. Thank them for all the things they do for you and your business.



Lo scorso fine settimana il mio server si è piantato. Ho dovuto reinstallare tutto e recuperare il backup del blog.

Consiglio: non usate LVM di linux come filesystem. Se si corrompe sono czz… fare un repair perchè i classici repair boot-cd non hanno tool compatibili. Usate ext3.


A Telnet test involves establishing a Telnet session from a computer that is not located on the local network to the external (public) IP address of the Exchange server. You need to carry out the test from a machine at home, or from another office. Doing the test from a machine on your own network will produce useless results.

  1. Start a command prompt.
    Either click start, run and type CMD
    or Choose Command Prompt from Start, Programs, Accessories, Command Prompt
  2. Type “telnet” (minus quotes) and press enter.
  3. At the Telnet prompt, typeset localecho

    (minus quotes) and press enter. This lets you see what is going on.
  4. Still in the telnet prompt, enter the following command and then press enteropen external-ip 25

    where external-ip is your external IP address eg:open 111.222.333.444 25
  5. You should get a response back similar to the following:220 mail.server.domain Microsoft ESMTP MAIL Service, Version: 6.0.2790.0 Ready at
  6. Type the following command in to the telnet windows:ehlo testdomain.com

    and press enter (note “testdomain.com” can be anything that isn’t a domain that the Exchange server is responsible for.
  7. After pressing OK you should get a response back250 OK
  8. Type the following command in to the telnet window:mail from:address@testdomain.com

    and press enter (again where address@testdomain is an email address that is not on the Exchange server. Note the lack of space between from and the first part of the address).
  9. After pressing OK you should get a response back:250 2.1.0 address@testdomain.com….Sender OK
  10. Type the following command in to the telnet window:rcpt to:address@anotherdomain.com

    and then press enter (where address@anotherdomain.com is not either an address you use internally or the address you entered earlier as the from. Once again note the lack of space between to and the first part of the e-mail address). 
  11. After pressing enter you will get one of two responses.
    If you get550 5.7.1 Unable to relay for address@anotherdomain.com

    then you are relay secure.
    However if you get250 2.1.5 address@anotherdomain.com
    Then you are an open relay.