vhcs2 auto responder not working

[Reptile]

Seems the official forums are closed and I don't know where else to turn so i have come here

I am trying to get the auto responder working on the email but I get a message returned to me saying this

: Command died with status 255:
    "/var/www/vhcs2/engine/messager/vhcs2-arpl-msgr". Command output: If
    specified by -literal_key, then the key length must be equal to the chosen
    cipher's key length of 56 bytes at
    /var/www/vhcs2/engine/messager/vhcs2-arpl-msgr line 1410

I checked the master.cf file to see if there were any parameters passed to vhcs2-arpl-msgr and none where.

It seems that the script has a problem decrypting some key and cannot retreive the auto response message from the database, maybe?

[chuckl]

What version are you using? There were some changes to where the Postfix keys were kept round version 2.4.7

[Reptile]

2.4.7.1 is the current version. From memory it was a claen install and it says there are no upgrades in the control panel.

[chuckl]

Ok, then does the /var/www/vhcs2/engine/messager folder contain
vhcs2-db-keys.pl?
From the error, it sounds tome like it is missing a keyfile or key access file.

My evaluation version is the VmWare image with 2.4.7, haven't used it in a year or so, but I can fire it up and check?

[Reptile]

yes it does. The contents have a file with 32 characters in db_pass_key.

[chuckl]

Right found the VM and reloaded it, that looks like it's in the db password decrypt routine.
Can you check the owner and group on the db_pass_key file? Should be vmail and mail.
Can also check the /etc/postfix main.cf for a line like

vhcs2-arpl_destination_recipient_limit = 1

and try adding that if it's not there.

[Reptile]

yeah that line is there and the permissions are correct. I tried applying the so called fix i found in the vhcs wiki but it's actaully for a different error message. SO still no luck.

[chuckl]

No recent changes to passwords etc? only other possibility is the conf file, but it's dying on the password decrypt, which suggests either a bad password, wrong cipher, changed key or similar.

I discovered that the VMWare image is actually 2.4.7.1, on Debian Sarge, so if you can give me an example of exactly what you were trying, I can test it out on a 'clean' system.

[Reptile]

Nope nothing since I installed the system from clean.

I basically went into the control panel, added an email address and turned on the auto responder. I emailed myself as a test and get that error message instead.

the error message seems to be the key length. maybe i can safely regenerate a new one? The only problem is it is running a company's email system and i cant sod it up.

[chuckl]

OK, create hosted domain, add a user/email address, turn on autoresponder and light blue paper.
Let me give it a try and see what blows up. I've got what is essentially a clean install, so not corporate repercussions involved.