Posts by Delta04

You are killing me with the reporting rules.

• When you want report a problem, you must create your own thread to avoid to pollute other discussions

Done. Thread created.

• You must ensure that the problem is not fixed yet in latest released version or development branch for latest serie

I search the forum and did not find anything related.

• You must create exactly one thread per problem

Single thread created. It was more like a question and not sure if it's a problem.

• You must give us the following informations:

• The i-MSCP server implementation in use for the concerned service (for instance: ITK, Fcgid, PHP-FPM, Proftpd, Vsftpd ...)

i-mscp 1.3.0 on ubuntu 14.04 LTS. Bind, Apache...

• The plugin name and its version if your problem belongs to a plugin

I don't think is a plugin related problem. I use the following plugins: ClamAV, OpenDkim, RoundCube plugins, SpamAssassin.

• A understandable description of the problem

The description of the problem (if there is one) I mention it above, on the first thread.

• The service logs (generally located under /var/log)

If you consider it is necessary, I'll search the logs for some related lines.

• The exact steps to reproduce the problem

I just created the client account by clicking Add Customer.

• If your problem is considered a bug by our team, you must create an issue on our bug tracker

Not sure if it's a bug...

Happy?

Indeed, that's how it wrote xn--visemplinite-8fb.ro.

Using dig command, here is what it display

root@server:/home/ubuntu# dig viseîmplinite.ro

; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> viseîmplinite.ro
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9221
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;vise\195\174mplinite.ro. IN A

;; AUTHORITY SECTION:
ro. 1799 IN SOA primary.rotld.ro. hostmaster.rotld.ro. 2013783170 10800 3600 604800 3600

;; Query time: 45 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Aug 31 10:36:27 EEST 2016
;; MSG SIZE rcvd: 107

Hello, everyone.

Here in Romania our TLD offer the possibility to register and use domain name with special characters (diactritic) ex: viseîmplinite.ro.
Unfortunately we notice that the domain name was incorrect written inside the bind, apache and other conf files. Any idea how to solved this problem? Does i-mscp support special characters?

Thank you.

Story:

Today I encounter a problem in Roundcube. I wanted to make an Spam Assassin rule using the Roundcube webmail for a certain account. I fowllow Settings + Junk + Address rules. I entered the rule and everyting was OK. I logout and login using other mail account to follow thesame path when I notice that "Junk setting" was not available ( it does not exists in the menu) for this account. Same server, same domain.

Info:
OS: Ubuntu 14.04 LTS
I-mscp version: 1.3.0
SpamAssassin Plugin version: 1.1.0
Roundcube Plugins: 1.2.4
Other plugins used: ClamAV, OpenDkim.

This is all information I got in this moment, following the rules. If you need more I'll be happy to provide them.

Hope it helps.

Story:

Today I encounter a problem with the OpenDkim plugin. The zone files in /var/cache/bind/ where empty so DNS was not solving the domains.
I deactivate OpenDkim, information appeared in the files (that's the moment when I discovered that Opendkim is causing the problem) and than activated it again, fies where still empty. I activate OpenDkim for a customer (domain) and DNS information apeared in those files.

Info:
OS: Ubuntu 14.04 LTS
I-mscp version: 1.3.0
OpenDkim Plugin version: 1.1.1
Other plugins used: ClamAV, SpamAssassin, Roundcube Plugins.

This is all information I got in this moment, following the rules. If you need more I'll be happy to provide them.

Hope it helps.

Just reboot the server and it's going to be fine.

Hello,

Once I updated the i-mscp to 1.2.11 and SpamAssassin plugin to 1.0.7, setting function for spam assassin in Roundcube just dissapeared. This could be a bug so I thought it's a good ideea to report it.

Solution was to downgrade to SpamAssassin to 1.0.6 and it seams to be working OK.

Hello, Nuxwin.

Thanks!

I strongly recommend so that mail function can be disabled from the Php-editor section for each domain (adding a "mail" button in the "Value for the disable_functions directive").

I encounter may websites with poor security that are spamming via php. The only option to stop them, as an server administrator without cutting the whole account, was to manualy edit the php setting by adding mail to disabled function. Unfortunately this is overwritten on the next update or by other reason.

Thanks!

Thank you all for help!

Ok, and this ini file where is located?

Thanks!