Posts by joximu

    So you need to change the content of the message.

    The mailservers only work with the envelope of an email - the "To:" field in the content (mail header) is not changed.


    Maybe its easier if you setup a filter rule in thunderbird which resends the mail to another address....


    But there maybe other solutions....

    Hi



    I use theese values - in the /etc/dovecot/dovecot.conf (at the end...)


    with theese values I have less problems than before... server with lots of mail users...


    /Joxi

    Hallo


    Die Meldung sieht aber nicht danach aus, dass MySQL zuwenig Dateien öffnen kann - sondern das imscp-dsk-quota Skript kommt an die Grenzen. Soweit kam ich noch nie und habe auch > 100 Kunden auf einem Server...

    Diese DB hat wohl sehr viele Tabellen...???


    Vermutlich muss du die Unix-Limits für das skript (für root) erhöhen.


    Meine 2 Rappen.....

    Yes.. yes and yes... :-)


    I know the stories... starting from the end of vhcs - the whole ispcp and i-mscp. Stories with ups and downs...

    I know you're doing a great job - but you are more or less alone....

    And I can imagine the problems when you want to optimize... oh yes..... the software is getting more and more complex...


    How to solve... is a question of *how* to help... and that's the crucial point....


    FB... I have no fb account - I don't see very much - even when I take the tomatoes off my glasses.... ;-)))

    Nuxwin I know that this way is not for everyone - a professional hoster should be able to go this way.

    You see - the last phpswitcher is from nov 2017 and php development increased the tempo since 7.0, and also several php based web applications changed the requirements so they do not need to bother with old php versions.

    That's why php 7.2 (and 7.3) support is so heavily needed for the last stable i-mscp and phpswitcher version.

    I know - a new i-mscp version is also needed... and I know (or I have the impression) that most of the tasks are on your todo list.....

    Maybe there are some people who could help with the different tasks - but they are only in the forum and not in github... even on github it's somtimes difficult to see what's going on - where are the problems etc.

    Ok, it's possible to have a look at your twitter or fb sites... but it's not very clear (twitter) and on fb I see nothing at all.

    You wrote in Dec 2017 you'll "add support for php 7.2 soon".... well.... this raises hopes... so it's no wonder people are asking and asking for the same.

    As far as I can see there's a development in the project - but the steps sometimes are to big to be done by one person in a reasonable time - an internal switch to another technique has so many consequences that many hours are needed to fix everything.

    I can understand... you want to go on using new techniques (whatever)... but you cannot do the development auf 1.6, 1.5.4 and maintenance of 1.5.3 alltogether alone. That's the impression I got when having a look at the project in the last months...

    Hi guys

    I also had the problem of delivering PHP 7.2 to customers (eg. TYPO3 9 needs 7.2 or higher).

    It is possible even with old infrastructure (imscp 1.2.x, phpswitcher 2.1.1) to adopt some parts and get a php 7.2 - need some try&error because of the debian patches for php but in the end it worked... not the latest, but 7.2.9 at least... maybe not the best solution, but one I can live with for the moment (it was February 2019).


    /J

    Oder so wie bei mir. 2 Server (A, B)...

    Server A hat laut SNDS am 28.5. 350 Spams geschickt (rot), ist aber nicht als geblockt aufgelistet und Mails gehen durch.

    Server B hat nicht massenweise gespamt, ist aber als geblockt angegeben und Mails gehen nicht durch.

    Sowas von logisch.


    Ich benutze dann Server A als Relay für B....


    Muss aber trotzdem diesen Report ausfüllen... sonst wird auf einmal A auch gesperrt und B noch nicht freigegeben...


    Das kann sich nur ne Bude wie MS leisten.

    My solution would be:

    either remove the vu2017 cron entry in the imscp databas

    or add a temp user "vu2017" (or jaust a fake line for it in /etc/passwd) and then remove the cron job - ander afterwards the temp user/fake entry...


    Seems the removal of a domain does not remove cron jobs belonging to this domain...


    /Joxi