Posts by lestatminiyo

    Do you know what is the right way to include a domain in Spamassassin whitelist with IMSCP?


    I just include whitelist_from_rcvd *@example.org in 00_imscp.cf file but... I think it will be remplaced on the next update.


    Thanks.

    Until now, I was using the Rainloop API to login from external sites to the webmail.
    From my last iMSCP update, the API always return an empty hash.
    I can't get if I should send the password in other way, or Rainloop API is just not working on this version.


    I'm having arround 10 spam emails per day on my inbox since last months.
    I checked spamassasin is running and evaluating but not very accurated...


    Code
    1. May 13 11:54:02 panel spamd[3347]: spamd: result: . 1 - DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,MISSING_HEADERS,SPF_HELO_PASS,SPF_PASS scantime=1.6,size=13680,user=info@MYDOMAIN.com,uid=113,required_score=5.0,rhost=ip6-localhost,raddr=::1,rport=49862,mid=<CO2PR01MB2088DF3582D3B0D4FB98B372C5E30@CO2PR01MB2088.prod.exchangelabs.com>,autolearn=no autolearn_force=no

    Do you know can I activate the autolearn and keep it after imscp updates?
    Autolearn will be working with Desktop clients?
    Do you know how can I set a DNSBL (as http://uribl.com/usage.shtml) properly?
    Any other idea to improve the spamassasing score?


    Thanks

    I'm fully interested on this topic.


    From my point of view, here are the Pro and Cons I see on both systems:


    Centralized:


    PROS
    [*]

    • Easy management
    • Just http API needed to comunicate with other server backends

    [*]CONS

    • All servers must be on the same iMSCP version, and same packages installed
    • Probably all servers must have same plugins installed
    • Many services duplicated using resources
    • Different Mail host addresses per each node, or relay needed.



    Distributed


    PROS

    • Optimal resources consumption
    • Big Scalability and possibilities
    • Load balancing according to the resources
    • Plugins managed just by 1 host
    • MySQL/ PostgreSQL servers
    • Maybe apache / nginx servers also

    CONS

    • Harder code development i think
    • srv1 or other host must be relay


    About non-free plugins, in Distributed maybe you must go to a "license per host" model
    Maybe you must think on distribute your software only just for debian, create a repository, and deploy the software like this... apt install imscp-mysql / ismcp-frontend imscp-apache imscp-nginx imscp-mailserver
    Later, just an apt update on each machine will give the last version of the frontend, backend, and rest of services
    On this way, all the people can have the same imscp version with the same rest of packages version and avoid incompatibilities...


    Just ideas...


    @vsimax


    I'm pretty sure that there is not problem at all. You should be a bit patient.


    Teamviewer?

    Yes, if the log file is not created I guess maybe letsencrypt is not launched yet by the plugin.

    Hi,


    I found a bug related to mailman.
    Recently I changed the IP address of the iMSCP server running /var/www/imscp/engine/setup/imscp-reconfigure
    and selecting only the new IP address (old one was deleted on /etc/network/interfaces previously)


    X.X.X.X new IP
    Y.Y.Y.Y previous IP


    It changed all the apache sites .conf files appending the new IP beside the old IP.
    <VirtualHost X.X.X.X:80 Y.Y.Y.Y:80>


    But, after doing that, if I create a new list, the list.example.com.conf file is created with the old IP:
    <VirtualHost Y.Y.Y.Y:80>


    Regards