Posts by Delta04

Indeed, it's about config.php inside SpamAssassin plugin.
I know the learning feature of Bayesian filter. Problem is that he was learning also to block good things.

Quote

Result: SpamAssassin is not involved for outgoing email (mail sent from our server) and that what we wanted.

it's only on outgoing? I thought that by entering the IP address, messages from and to the server using this IP is not scanned/blocked by Spam Assassin.

Hello everyone,

I want to open a thread for those who personalize SpamAssassin plugin's settings.
The config values I found working well for my setup are,

use_bayes = no
site_wide_bayes = no
use_auto-whitelist = no
use_razor2 = yes
use_pyzor = yes
use_dcc = yes
use_rbl_checks = yes
use_lang_check = no
heinlein-support_sa-rules = no
DecodeShortURLs = yes
liXhash2 = yes
markasjunk2 = yes
reject_spam -1
networks = we include our ip class and localhost (still, aparently I notice that it ignores this setting and mark as spam emails from the same server/domain).

It is necessary to install extra application (ex: dcc) so those settings to work.

I wonder, what other custom settings or improvements this community is using.

I just updated the i-mscp from 1.3.16 to 1.4.1 and the error above appeared.

OS: Ubuntu 14.04 LTS
Plugins: ClamAV, Let's Encrypt 2.0.5, Mailgraph, OpenDkim, Roundcube plugins, SpamAssassin.
Php: 5.6

I deactivated all plugins before running the update script.

Line 1 in /etc/apache2/imscp/before/vhost.conf is,

Alias /.well-known/acme-challenge/ /var/www/virtual/LetsEncrypt/.well-known/acme-challenge/

Line 19 in /etc/apache2/sites-enabled/domain.ro_ssl.conf is,

-pass-header Authorization

Any suggestions?

Thanks.

I did that. All worked fine.

Thanks for help.

Fresco and serverhost are two different servers. I use serverhost and the problem appeared. Fresco, a client he notice also this problem...

Quote from Nuxwin

@Delta04

We cannot help you without more details.

SMTP or IMAP ?
Also

• Be sure to configure your mail client with the name used in your cert.
• Give use the domain name used in the cert if you want make us able to process some tests.

BTW: LetsEncrypt is a plugin and we have a specific section for plugins...

Thread moved.

Display More

Both, SMTP & IMAP.

I did configure the mail client with the domain name used in cert.

Domain is serverhost.ro and mail.fresco.ro (website is hosted by other hosting provider).

Hello, everyone.

This morning, by checking email (with Thunderbird, Mail client in iOS) I notice a warning that inform me that the Let's encrypt SSL is untrusted.
I disable/enable SSL for services on that domain, hopefuly it will renew, but no effect. This happened over night.

On https (web) all green, no problem.

Info:
Ubuntu 14.04 LTS
i-mscp 1.3.16
Let's encrypt 2.0.5

Not sure if it's a bug, a problem with let's encrypt servers or something else. Is there anyone that encounter this problem?

Thanks

Ok. Thank you.

First of all, I don't think it's an i-mscp related problem because the problem is only on one of the servers, the rest are working perfectly.
If you can help me with an advice to fix it, I'll apreciate it very much.

The problem is that, each time the email client (Thunderbird, Outlook) is opened, every email in the account is downloaded. Client is configured with IMAP. Weird is that the problem apeared after upgrading from i-mscp 1.3.1 to 1.3.5.
I searched the web and I found that dovecot has some index files in each email account folder. Those files can be sometimes corupted and the problem appeared.
I followed the recomandation to fix it by deleting those files with dovecot stoped and after, start over dovecot. Indeed, dovecot rebuild those files but the problem is still there.

Thank you.

According the reporting rules,

• You must ensure that the problem has not been already reported on our issue tracker

Did not find anything related.

• You must ensure that the problem is not already fixed in latest released version or development branch of latest i-MSCP Serie

Did not find anything related.

• You must create your own thread to avoid to pollute other discussions

Done that.

• You must create exactly one thread per problem

Done that.

• You must give us the following informations:
• 
  
  
  • Your Distribution and its codename

  Ubuntu 14.04 LTS
  

  • The i-MSCP version in use

  I-mscp 1.3.5
  

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

  Dovecot, Postfix.
  

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

  I disabled all plugins so I don't think they are problem. Still, I use SpamAssassin, Roundcube Plugins, OpenDkim, ClamAV plugins. The last version.
  

  • A understandable description of the problem

  You can find that at the begining of the thread.
  

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

  Nothing weird in the logs. if needed, I can give you the logs. Just tell me which one.
  

  • The exact steps to reproduce the problem

  You can find that at the begining of the thread.
  

Cool. Didn't know. Thanks for info!