Posts by Delta04

It's so great to see a new fresh stable version of i-mscp. Congrats and keep on the good work!

The alias webmail was good because it is more easy to remember for the customer. From the security point of view you are right, still I did not have any attack on the webmail :P.

So, is not a bug, it's a feature.

The hostname and reverse IP is OK, and to be sure, the domain that I use is the main domanin from where the e-mails are sent. There must be something else...

A bit offtopic, there is a problem with the domain.tld/webmail redirect in the gitmaster version of 12 ian 2014.

Thanks for the answer. Last night I did some digging on the web and, indeed, the problem is not with the dkim or spf. Also the source of email says pass on those two,

Quote

spf=pass (google.com: domain of [email protected] designates 94.x.x.x as permitted sender) [email protected];
dkim=pass [email protected]

It must be something else.

I have some problem with gmail, practically every mail sent from the server using opendkim / spf in gitmaster imscp version is landing in spam folder.
I have searched the web for info and I have found the following,

Quote

Messages with DKIM signatures use a key to sign messages. Messages signed with short keys can be easily spoofed (see http://www.kb.cert.org/vuls/id/268267), so a message signed with a short key is no longer an indication that the message is properly authenticated. To best protect our users, Gmail will begin treating emails signed with less than 1024-bit keys as unsigned, starting in January 2013. We highly recommend that all senders using short keys switch to RSA keys that are at least 1024-bits long.

Source

The question is, does the opendkim plugin generate 1024 bits long RSA key?

Thank you for the answer.
[hr]
According to this,

Quote

DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; ....

I guess is a 256 bit key. Too weak for today's standards. I guess this is the reason that gmail treat those email as spam.

Is there a way to make it 1024 bit long?

Thanks! That was the problem on Ubuntu. Unfortunately, on the Debian server I can't do the update now. I'll try in the night time...

Nuxwin, I notice that you can read logs with your telepathy.

Thanks once again.

Quote

root@server: /usr/bin/php5 -v
PHP Deprecated: Comments starting with '#' are deprecated in /etc/php5/cli/conf.d/apc.ini on line 28 in Unknown on line 0
PHP Deprecated: Comments starting with '#' are deprecated in /etc/php5/cli/conf.d/apc.ini on line 45 in Unknown on line 0
PHP Warning: PHP Startup: apc.shm_size now uses M/G suffixes, please update your ini files in Unknown on line 0
PHP 5.3.10-1ubuntu3.9 with Suhosin-Patch (cli) (built: Dec 12 2013 04:27:25)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2012 Zend Technologies
with Suhosin v0.9.33, Copyright (c) 2007-2012, by SektionEins GmbH

Display More

I wonder it the "PHP Deprecated" was the problem.

On Ubuntu.

Quote

[FATAL ERROR]
iMSCP::Requirements::_programVersions: Unable to find /usr/bin/php5 -v version: No output

If I manually run /usr/bin/php5 -v, there is an output.

Hello,

I did try to update to the latest git master version (09.01.2014) and the install script does not work. It just crash with the following message,

Quote

[ERROR]

iMSCP::Debug::END: Exit code: 1

The problem is on Debian and also Ubuntu 12.04 LTS. The only difference is that on Ubuntu it crash sooner.

I know is the experimental/unstable version but I think is good to know about this issue.
The reason that I'm updating is that on the Ubuntu, from time to time Apache (with fpm) just fall asleep.