Search results

@UFHH01 Thanks - what do you use in your imapd-ssl file for TLS_CIPHER_LIST?

Unfortunately, that does not fix our issue - we continue to see the following errors in the maillog (and the mail server does not respond on port 143 or 993): Oct 20 15:14:19 nsxxxxxxxx courier-imaps: couriertls: connect: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher The...

Thanks for your response and suggestions. We have checked all file paths, permissions and certificates and all are correct. The only way we got this to work with mail clients is to modify the TLS_CIPHER_LIST value in /etc/courier-imap/imapd-ssl to the following (as per Bobcares article at...

@UFHH01 Thanks for your suggestions. We have reissued the certificate but this had no effect - same errors in the log files as follows: Oct 19 12:56:57 nsXXXXXXX courier-imaps: couriertls: connect: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher I've tested this on several...

Thanks for your reply. Here's the output on our test server: [root@nsxxxxxxxx ~]# openssl s_client -connect localhost:993 -quiet depth=0 C = --, ST = France, L = Roubaix, O = OVH, OU = --, CN = nsxxxxxxxx.ip-198-100-147.net, emailAddress = [email protected] verify...

I have tested with other mail clients (eg Thunderbird 31.2.0, Mail 17.5 on Windows 8) and the problem is the same - mail on port 993 doesn't work after SSLv3 is disabled and the following error is logged in maillog: Oct 19 07:59:49 nsxxxxxxxx courier-imaps: couriertls: connect...

The mail client is Mail on iOS 7 and also Mail on the Mac (don't know specific version on Mac). Anyone else tried secure POP/IMAP after applying the recommended changes?

After applying the recommend changes to Courier IMAP/POP files users who access mail via SSL are unable to connect to the server - the following errors occur in the mail client: There may be a problem with the mail server or network. Verify the settings for account or try again. The server...

The SpamAssassin bayes database has become ineffective on one of our servers and we want to wipe it and start fresh - can anyone confirm how to do this on Plesk 11.5.30?

After opening a ticket with Parallels on this, they confirmed that FTPS actually works on port 21 (not port 990). You need to set the FTP client to use "Require explicit FTP over TLS" for the encryption mode while still using the standard FTP protocol on port 21. This is not included anywhere...

That's correct - we want to use FTPS without enabling shell access for users, but the server does not seem to be listening on port 990. Is anyone else's Plesk 11.5 server listening on port 990 or is Plesk's implementation of FTPS different from what I am expecting? The documentation for this...

Telnetting to port 990 doesn't work, but port 21 does - is port 990 definitely the port that Plesk runs FTPS on?

This is what we are getting in FileZilla when attempting to connect to ftps://server.hostname:990: Status: Resolving address of server.hostname Status: Connecting to 1.2.3.4:990... Status: Connection attempt failed with "ECONNREFUSED - Connection refused by server". My IP is...

We just upgraded from Plesk 10.4.4 to 11.5.30 and can't seem to get FTPS to work. I presume it should be running on port 990, but the server is not listening on that port (only 21 for FTP). netstat -lptu | egrep 'ftp|990' tcp 0 0 *:ftp *:*...

Is there any alternative available for Plesk 11.5? Having just upgraded from 10.4.4 to 11.5 we are not ready to upgrade to Plesk 12 so are there any other solutions to filtering outgoing mail for spam?

As far as i'm aware, there has been no fix for this issue as we are running the latest update of 10.4.4. The way we work around this is to run the server_pref command hourly via a cron job - not ideal but has prevented any ongoing customer issues. I haven't tested 11 to confirm if the issue...

We are seeing this issue in Plesk 10.4.4 Update #36 - we run the command below and the 'No secure shell available' message goes away: /usr/local/psa/bin/server_pref -u -crontab-secure-shell /bin/sh But after some time, the 'No secure shell available' message comes back and the only way to...

It seems that Qmail runs the 'Handlers Filter' on all forwarding email addresses before sending the message, and if any one of those addresses is rejected then this results in the message failing. For example, let's say an email address is set to forward to these addresses: [email protected]...

We are seeing this as well, also using Plesk 10.4.4. Hi. This is the qmail-send program at server.hostname.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <[email protected]>: Unable to...

We have just migrated a bunch of sites from Plesk 9.5.4 to 10.4.4 using Plesk Migration Manager and for sites where a directory and/or files are owned by 'apache' this was lost on the target host and reset to the domain owner's account with 755 permissions. This results in web applications...