Posts by flames

    бывает :)


    дело в том, что диск лучше...
    1. монтировать прямо туда, где он требуется. если весь диск исключительно для /var/www/virtual, то монтируем прямо туда. например mount /dev/sdb1 /var/www/virtual
    2. если диск содержит директории для разных целей, то монтируем диск куда либо, например в /mnt/disk, после чего директории находящиеся на диске монтировать с помощью bind --mount в нужные директории. например mount /dev/sdb1 /mnt/disk
    mount --bind /mnt/disk/mail/virtual /var/mail/virtual и mount --bind /mnt/disk/www/virtual /var/www/virtual


    можно использовать /etc/fstab, для правильного синтаксиса погуглить.


    если диск не в нативном формате linux, или в устарелом формате, т.е. не ext3fs или ext4fs, то проблемы могут возникнуть даже при правильном монтировании.
    unlink поддерживается всеми нативными файловыми системами linux, но например extended attributes, которые пользуются для защиты директорий в i-MSCP требуют современную файловую систему. так-же не все сетевые диски/shares поддерживают нужные функции.

    Give me one for debian (test it first) ;) Then, I can code that plugin.


    check!


    I've one netgrear and one Linksys routers and both don't provide such option ;)


    are that WRT firmware based router? i will check the default vendor firmware settings and report. i have an asus rt ac66u and a netgear r7000, both have custom dyndns stuff :)


    not all, just the steps how to get a letsencrypt certificates.
    istead of the symlinks you can use the listener (but the listener is just a case study to prove the scenario).
    UncleSam's way is to prefer! I posted the listener as answer to UncleSam, so he can try and improve. Else I would have made a separate Thread.


    in my personal case UncleSam's way was not update safe, because the symlinks were overridden with new self-signed certs. then i created the listener, to get through i-MSCP updates. I need to add, the overriding might be an issue of my custom i-MSCP configuration.

    • I cannot develop such plugin by closing my eyes. I'm located in France and as stated above, our boxes don't allow such setup. Of course, I can mimic the FRITZ!Box behavior by developing my own client but that would take much time.

    yes, agreed. about the special french situation i was not aware.


    just for completeness sake, there are a lot of open source and freeware clients, that allow custom dyndns update urls and variables, for every operating systems. so there is no need for your own one.
    in point of view of hardware routers, indeed, only few (Fritz!Box, Sophos, Fortigate, and almost all WRT based routers, like ASUS, Linksys, Netgear) support custom settings.


    @mrpink, yea, this one looks good. thanks for the info! but when do they start to limit their service also? i guess, as soon, as it gains popularity and the cost of the freebies service exceeds the budget. like happened to dyn.ee, eisfair.org dyndns service, dyndns.org, noip.com (former noip.hopto.org)


    thread can be closed?

    @Nuxwin, no, this plugin is a DynDNS service. So any customer on an i-MSCP server can have dynamic hosts as subdomain on his own domain.
    Since services like dyndns.org and noip.com limited their free accounts, this plugin got very interesting.

    I try to do a short translate...


    the question is, how to proceed at apt-get upgrade or apt-get dist-upgrade, if a new configuration file for a package is available like such dialog:



    With i-MSCP I do always choose the new configuration file version, and overwrite the original one.
    With i-MSCP this is safe, because i-MSCP setup will anyway recreate all needed configs.
    Other advantage is, in cases, where a package has indeed big changes in the config file structure/syntax or configuration parameters/values, it might happen, that after installation of this package and leaving the old configuration file, the package might not work or have issues.


    In cases with other software (not i-MSCP) You should know or learn how that special software works and proceed the appropriate way. So there is probably no perfect answer except of "create a backup, try, learn"

    You could try this listener and improve


    yes. the behaviour is right, spamassassin sets the spam score on incoming smtp, not on internal traffic (local delivery, outgoing smtp traffic). so the spam score of your catchall delivery is set on incoming smtp traffic to the original recipient, while on forwarding it is not changed anymore.
    indeed, you can set spamassassin to do also local and outgoing traffic filtering, but this is outside of the current plugin spectrum.