Posts by kurgans

Deberas actualizarlo primero a 1.0.7, no lo se con seguridad pero me parecio leerlo por ahi mira en el foro en la seccion de migracion, ojito los upgrades si tienes dominios suspendidos te fallara, ponlos activos para el upgrade de ispcp

Mirate los pm de ispcp ahi tienes para levantar el panel, una vez levantado en la wiki de aqui tienes como migrar el panel, yo ya aprovecharia para cambiar a dovecot ya que parece va a ser el sistema que se va a implantar por su funcionalidad.

Tienes scripts en internet de como migrar el correo de courier a dovecot

Quote from Nuxwin

kurgans: Your note is only valid if you are using the i-MSCP fcgid/fastcgi httpd server implementation. Don't forget that i-MSCP also provides other Httpd server implementation (ITK, PHP-FPM). You can refer to this documentation to learn more about the way i-MSCP manages php.ini files, according the i-MSCP httpd server implementation you are using.

To finish, I should warn you that with the coming fix for proftpd, the user home permissions will be enforced to protect directories (htdocs, backup, phptmp...) against deletion. If you are breaking these permissions, we will not provide any support.

Thanks you for using i-MSCP.

Jejeje

Old school ispcp even makes you think of the old system, I know we have other great opportunities still is the lack of knowledge and learning of new panel.

I'll be looking at all the documentation to get to know everything well.

thanks

Te contesto en español por que se que lo hablas,

La directiva open_basedir la tienes que habilitar a nivel de servidor no en la aplicacion php

Buscala aqui
/var/www/fcgi/dominioquesea.tld/php5/php.ini

Requiere reinicio de apache

Not the same problem, the system deletes perfectly, does not create folders or anything to make the sql injection with toadd state and stays there.

No es el mismo problema, por no actualizar voy agregando soluciones manualmente del master, se ve que algo he modificado en algun archivo y se me ha ido la pinza en retocarle el codigo modificado, el sistema borra perfectamente, no llega a crear las carpetas ni nada hace la inyeccion a la sql con el estado toadd y ahi se queda.

Hello friends, I have noticed that when I create a subdomain is not added, it is always in a state of creation in process.

Now the solution is that we run the debugger panel.
After running the debugger change status to OK and work ok.

When installing the panel worked well I have several subdomains created, it only added <<DomainKey>>, not whether it will have a hand in the creation of subdomains.

Any suggestions to know the problem

Thanks

Seguro que tienes espacio en la particion del panel ......

Metete por phpyadmin o la consola sql y ve a la tabla de subdominios dentro de imscp y ponlos de nuevo en estado OK y vuelve a tirarle el borrado.

imscp » admin
Change
Pass with funcion MD5 and save

Other
change email administrator and resend your new pass to new email

Well I've thought but to make the sed command to replace all the users have found the right way.

ip4: xxx.xxx.xxx.xxx ip4: xxx-xxx-xxx-xxx

Change the entire line, not even the panel know well, I think modifying TPL bind and regenerating the config this problem would be solved, even though the system I'm looking at, but is very familiar but you must learn its new features
[hr]

Quote from Nuxwin

Edit:

After further investigation, I think we must improve postfix configuration.

For now, we tell postfix to listen on every available interfaces (ipv4 and ipv6). This is specified in the main.cf by the following parameters:

Code

1. inet_protocols = ipv4, ipv6
2. inet_interfaces = all

and in the SPF record of each domain we add both, the base server IP and the IP assigned to the customer by the reseller.

With the current way to do, we can end with many problems:

- If we have a stack of 10 IP configured on the server, Postfix will use one of them as IP source for the outgoing mail. Well,, as long the IP is one of these in the SPF record, We will not have any problem but in case the IP is not specified if the SPF record, we will end with a SPF validation error.

- It's not really good to let postfix choose the IP for outgoing mail randomly. If you have a customer with a particular IP that become blacklisted due to spamming actions or anything else, nothing ensures you that the blacklisted IP will be the one assigned to this user.

I've already some ideas to how solve that problems (As Plesk do):

http://kb.parallels.com/en/114491

Another way:

http://www.kutukupret.com/2010…ated-outgoing-ip-address/

Display More

No I agree with you, just caught my attention quite see how gmail prioritizes IPV6 when in config postfix IPV4 its configured to send mail