Download getmail at http://pyropus.ca/software/getmail/old-versions/getmail-4.20.3.tar.gz

wget http://pyropus.ca/software/getmail/old-versions/getmail-4.20.3.tar.gz
tar xzf getmail-4.20.3.tar.gz
cd getmail*
python setup.py install

Now you have to create a getmailrc , the getmail configuration file inside the home folder of the user. getmailrc need not be inside the home directory. You have to create the folder .getmail where getmail keeps a log of the emails retrieved based on each configuration file you may have.You can have multiple destination and retriever sections in one single getmailrc as well.

I must say getmail is so much flexible and rightly coded when the mailsync or imapsync didn’t do their job right or up to the mark. And is an excellent replacement for fetchmail. It supports POP, POP3S, IMAP4 and IMAPS, and also can store the mails retrieved in mbox or maildir format at the destination.

An extremely simple getmailrc file will look like this

[retriever]
type = SimpleIMAPRetriever
server = mail.domain.com
username = direct@domain.com
password = direct

[destination]
type = Maildir
path = /home/cpusername/mail/.direct@domain_com/

The file format should be pretty self-explanatory. You’re telling getmail to fetch your email from server, mail.domain.com by logging to it using the mentioned username and password. The destination section mentions where to store the retrieved email and in which format (Maildir or mbox or mboxrd). Make sure that the cur, new and tmp are there inside those folder though. However getmail may create those folders automatically though.

Finally to get this going, just run “getmail –rcfile getmailrc”

Once you run it, assuming that the getmailrc is properly configured, you will be welcomed by a below output.

getmail version 4.20.3
Copyright (C) 1998-2009 Charles Cazabon.  Licensed under the GNU GPL version 2.
SimpleIMAPRetriever:direct@domain.com@mail.domain.com:143:
 msg    1/3983 (299328 bytes) delivered
 msg    2/3983 (2815 bytes) delivered

“This request cannot be completed because the link you followed or the form you submitted was only valid for minutes. Please try again now.”

Solution

Edit C:\inetpub\vhosts\webmail\horde\lib\horde.php (Drive Letter will depend on where you installed Webmail/Plesk and configured IIS to load virtual hosts from)

And search for section ” SESSION['horde_form_secrets' " in the Horde.php  and instead of

if ($_SESSION['horde_form_secrets'][$token] +  $GLOBALS['conf']['urls']['token_lifetime'] * 60 < time()) {
return PEAR::raiseError(sprintf(_(“This request cannot be completed because the link you followed or the form you submitted was only valid for %s minutes”),  $GLOBALS['conf']['urls']['token_lifetime']));
}

it should be

if (($_SESSION['horde_form_secrets'][$token] + $GLOBALS['conf']['urls']['token_lifetime']) * 60 < time()) {
return PEAR::raiseError(sprintf(_(“This request cannot be completed because the link you followed or the form you submitted was only valid for %s minutes”), $GLOBALS['conf']['urls']['token_lifetime']));
}

Note the extra braces in red + bold

So after several tries we find that it is not possible to remove the domain from the plesk interface. So the problem needs to be dealt at the root level. So what is the root of all the entries in plesk? Of course the plesk’s DB ! Here are the steps to follow for the troubleshoot:

1) Since plesk uses different DBs we shall now try to find what DB server it uses.
Go to Start>All Programs>Plesk?Plesk Reconfigurator. In the pop up window obtained, select ‘Switch DB provider’. Note the field for ‘Server Type’. It will show the DB type plesk is currently using. You may find that it supports MySQl,MSSQL and Jet. I shall now continue the article with refernce to Jet DB.

2) Now we have our target clear: editing plesk’s Jet DB to remove all instances of a particular domain. We shall now try to find a frontend GUI tool for editing plesk’s Jet DB tables. I used ‘MDB Viewer Plus’. It is a DB viewer combined and an editor software. You can download the file from:

http://www.alexnolan.net/software/MDBPlus.exe

Then proceed with the installation.

3)Run the program. Navigate to File>Open. Now search for the DB location. It will usually be in %Program Files\Parallels\Plesk\admin\db\psa.mdb. Open the particular db.

4)Open the ‘Query’ from the toolbar. This helps us to execute MSSQL queries from this program. Into the space for query, enter:

SELECT d.name FROM domains d LEFT JOIN dns_zone z ON d.dns_zone_id=z.id WHERE z.id IS NULL;

and click ‘Execute’. It will display the list of domains having missing or inappropriate IDs in psa.mdb.

The meaning and reason for the error is that in the DB file psa.mdb, the ‘dns_zone_id’ record in the table ‘domains’ points to inexistent ‘id’ record in ‘dns_zone’ table for one or several domains. It may happen because of Plesk internal issues, broken database, incomplete domain deletion. We shall verify this now.

5) In the toolbar for the list of tables of the psa.mdb, navigate to the table ‘dns_zone’. You will find multiple entries for the domain in question. Remove the latest entries and then note the ‘id’ record for the particular domain.

6)From the toolbar navugate to the table ‘domains’. Click on the domain in question. Then move the scroll bar below to search for the record(or coloumn ‘dns_zone_id’). Note the this id. You will note that this will be different from the ‘id’ record in step 5. This mismatch had led to the dns zone being NULL for the particular domain.

7)We can verify this by running commnads in ‘Query’ toolbar also. Open ‘Query’ from the toolbar and run the commands:

a. to verify step 5: Select id from [dns_zone] where name=’domainname’
b. to verify step 6: Select dns_zone_id from [domains] where name=’domainname’

We can see the two different id results.

8)So we need to eliminate this mismatch. For that we will need to provide the correct id for the table: ‘domains’. For this we will replace the result of  7)b with 7)a. Run the following command:

UPDATE domains SET dns_zone_id=’dns-zone-id’ WHERE name=’domainname’;

Replace dns-zone-id with the result of  7)a.

The issue is fixed !

ISSUE

DNS zones are never created, and the DBs are not properly updated. Even after reconfiguring the domains using websrvmng.exe –reconfigure-vhost –vhost-name =”domain.com” it couldn’t be deleted. Shows the message “Information: Domains are now removed”, but in real, the domain will be still shown under the domains list.

And the domain will be in suspended state. Unsuspension of the domain will result in an error message “DNSZone::Table::select() failed: no such row in the table”

Solution for the above issue is explained at http://www.supportsages.com/blog/2009/08/plesk-account-unsuspension-tableselect-failed-no-such-row-in-the-table/

However even after fixing the DNS like this, the issue cycles.

Removal of domain results in suspension of domain -> Unsuspension of domains results in above error -> Fixing the error allows to unsuspend and Removal of domain results in suspension of domain

SOLUTION

So solution I used to solve was to manually remove the domain related entries from plesk database, from the file system and also from the email services. Get into MySQL or whichever DB plesk is using. For finding the current DB, use Plesk Reconfigurator and then follow the parallels KB found at http://kb.parallels.com/en/3472

The instructions below assumes that you are using Mailenable and Plesk vhosts directory is at “C:\Inetpub\Vhosts” . This location can be at D:\ or E:\ even. Also, I hereby assume that there are no two domains which can match the mysql LIKE query I used below i.e There are no domains like 1domain.com , 2domain.com along with actual domain.com. If there is one, please use your “brain” to find the right domain and the IDs associated with it. When in doubt, please comment.

Disclaimer : If you mess up the database neither me or SS will be responsible for it

Let’s first gather all the ‘id”s first, like dom_id, sys_user_id, id etc which will be helpful in the deletion of database entries relating to the domain name which you want to removed.

1. Getting the IDs.

Domain ID – dom_id or id

 mysql> SELECT id FROM domains where name=’domain.com’

We are assuming that dom_id you got as a result of above command is 8880

Database ID – db_id

mysql> select id FROM data_bases where dom_id=(SELECT id FROM domains where name=’domain.com’);

We are assuming that db_id you got as a result of above query is 1433. Please note that you could get more than one result. Please save all the db_id and re-execute the sql query for each db_id.

System User ID – sys_user_id

mysql> select id FROM sys_users where home like '%domain.com%';

We are assuming that sys_user_id you got as a result of above command is 8843

Let’s start the actual deletion process

Shall we backup ? Better be safe!

C:\Program Files (x86)\Parallels\Plesk\Databases\MySQL\bin>mysqldump -P8306 -uadmin -p<plesk DB admin pass> psa > c:\psa.sql

You are now ready to delete. Please execute the follow sql commands in mysql prompt

delete from db_users where db_id='1433';
delete from data_bases where dom_id='8880';
delete from mail where id='8880';
delete from subdomains where id='8880';
delete from dns_recs where id='8880';
delete from domains where id='8880';
delete from domain_aliases where dom_id='8880';
delete from hosting where sys_user_id='8843';
delete FROM sys_users where id='8843';
delete from dns_zone where displayName=’domain.com’;

Database entries are deleted. Now it’s time to remove the users and files from the filesystems, IIS, Server, Mail server, DNS server etc.

1. Remove the domain from inetpub -> vhosts
2. Remove from Mail Enable Administrator. If it is SmarterMail, follow other steps.
3. Start => run => mailenable.msc => Post Offices and remove it.
4. Remove Sites “domain.com” and “Application Pool” from Internet Information Services manager. If IIS7, use command line option => %systemroot%\system32\inetsrv\APPCMD.EXE delete site “domain.com” .
5. Remove from Computer management Console -  System Tools > Local Users and Groups > Users. You must remove references to the domain for Plesk Domain User and Plesk IIS User as well.
6. Remove DNS entry – depending on the DNS server.

Finally,

cd %plesk_bin%
domain.exe -r domain.com

These steps should help remove the domain manually from the plesk. Please note that this article is based on the second attempt and could be buggy. I assume some “common sense” when running these commands. Understand the commands and each step before you actually execute it. Good luck. Don’t MESS up!!

C:\> %systemroot%\system32\inetsrv\APPCMD.EXE migrate config "domain_name.com/virtual_directory"
Successfully migrated section "system.web/httpModules".
Successfully migrated section "system.web/httpHandlers".

Now if you are going to migate the web.config inside the WEB_ROOT directory itself and not inside any virtual directory don’t miss a forward slash, / after the domain name.

eg:

C:\> %systemroot%\system32\inetsrv\APPCMD.EXE migrate config "domain_name.com/"
Successfully migrated section "system.web/httpModules".
Successfully migrated section "system.web/httpHandlers".

Otherwise you may get an error like below,

ERROR ( message:Cannot find APP object with identifier “domainame.com”. )

A good article to refer is available at http://blogs.msdn.com/tmarq/archive/2007/08/30/iis-7-0-asp-net-pipelines-modules-handlers-and-preconditions.aspx

Suspend and quickly unsuspend the domain works around 20% of situations and if that also fails, we may need to work in the Plesk PSA database. Before you work on this, please make sure that the plesk psa database is backed up.

cd %plesk_bin%
cd ..\..\MySQL\bin
mysql -u admin -pPASSWORD -P 8306

In most cases, Plesk MySQL server’s admin PASSWORD will be the Plesk password itself. If it isn’t reset the plesk password again, but with “%plesk_bin%\plesksrvclient.exe” -set NEW_PASSWORD_HERE true (true parameter will reset the MySQL admin password as well)

Assuming you are now in the plesk mysql server prompt, follow the below steps in mysql prompt.

mysql> use psa;
mysql> select * from dns_zone where name like 'domain_name.com';

In the output shown similar to below, check the status of the zone. I have seen only the values 0 and 2. Not sure whether there is a status value of 1 even.

If DNS for some domain is managed in Plesk Control Panel, the status for this domain in dns_zone table is temporary setting to value 2 (to lock it for any changes) and sets it to 0 value when the transaction is over. If for some reason the transaction is interrupted during DNS managing (Plesk restarts for example) the status field value is not changed to 0 and stays as 2. Domains with that status value are not recorded in named.conf file during any DNS management.

Now check to see whether there is only one such record for the ID shown for the above sql query. Chances are there could be two and if there are two, you should delete the record which is orphan or has no reference back to dns_zone.

mysql> select * from dns_recs where dns_zone_id=`the_id_you_got_from_the_above_mysql_query`;

The results you get should be matching with the DNS_Zone_ID and the domainname in question.

If you see anything else, i.e orphans or else if you don’t see any entries in dns_recs corresponding to the dns_zone_id, delete it.

mysql> delete from dns_zone where id=[wrong_record_id];

And finally update the status from 2 to 0;

mysql> update dns_zone set status=0 where id=[the_dns_zone_id_you_got]

When it’s done update DNS records using dnsmng.exe utility:

cd %plesk_bin%
dnsmng.exe update domain.com

Finally there could be a few situations where the entire DNS service is down. Usually the monitoring should detect such situations. However I usually noticed that this happens only when it is the BIND server which is being used as the DNS server software. A switch of the DNS server to Microsoft DNS should fix the issue. You may need to check the versions supported at the release notes available at http://www.parallels.com/products/plesk/docs/ . On my investigation disabling the zone of an internationalized domain name solved the issue with one server though and let us continue using BIND server.

References : http://kb.parallels.com/en/5242

You can edit default server backup repository directory path through registry. Go to

Regedit and then browse the keys
HKEY_LOCAL_MACHINE\SOFTWARE\PLESK\PSA Config\Config

Right Click on variable “DUMP_D” select Modify and set the server backup repository path as you wish. Default Directory Path for Plesk Backup is “C:\Program Files\Parallels\Plesk\Backup\”. Go ahead and change it to a location of your wish, say “E:\Backup”

Windows 64 bit edition

Again it’s the registry only, but the location may be a bit different. You need to browse to
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PLESK\PSA Config\Config

And repeat the steps mentioned above. If you cant find these keys, search for the “DUMP_D” without quotes and update it.

Linux 32/64 bit editions

#vi /etc/psa/psa.conf

Find the following variable, DUMP_D and edit the server backup repository directory PATH as you wish. Default Directory Path for Plesk Backup is “/var/lib/psa/dumps” You may change it to /media/backups

# Backups directory
DUMP_D /var/lib/psa/dumps

Okay. Those were the steps of a sysadmin not so greenhorn. If you are not comfortable with running regedit, use Plesk Panel Reconfigurator.

By using Parallels Plesk Panel Reconfigurator you can move the Parallels Plesk Panel backup files storage directory to another location on the same or another partition.

To change location of the backup files directory, follow these steps:

1. Run Parallels Plesk Panel Reconfigurator and select the Change Plesk Backup Data location option.
2. Specify the destination directory name. If the directory does not exist, it will be created.
3. Click Next. During this operation all Parallels Plesk Panel services will be restarted.

What I could get was “Bad Request (Invalid Hostname)” in bold letters. Here is what I did to fix the same.

Start -> Run -> inetmgr -> Expand the (+) -> Websites -> Right click on the domain name -> Take Properties -> Website -> IP Address (make sure that it has the dedicated IP assigned there) and then click “Advanced”

Add/Edit Web Site Identification

IP Address : Choose the dedicated IP from drop down list
TCP/IP Port : 80
Host Header Value : Leave it blank (Important)

Leaving the Host Header Value should fix the issue and fetch the website when accessing it using the IP.

1. Login as root to the server using ssh
2. Then issue the command below, to see your plesk password cat /etc/psa/.psa.shadow

To Recover your plesk password on a windows dedicated or VPS server

1. cd %plesk_bin%
2. Make sure that you ended up in a folder which is a line similar to “C:\Program Files\Parallels\Plesk\admin\bin\” If not, you will have to do a “D:\” or so depending on which drive or disk you installed Plesk on and then issue the below command
3. plesksrvclient.exe -get