We have a few users that use SSL email and we decided to purchase a cheap single-root SSL cert over at namecheap for the host name so that it would end the "self-signed cert" whining.
We got the cert installed and it works great for WHM/cPanel and also works for SSL over IMAP and POP3, but the very first email anyone sends (SMTP) per day gives this warning (Outlook Express):
The server you are connected to is using a security certificate that could not be verified.
A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
It seems obvious that the cert used by the SMTP system is not the new one we installed.
We used WHM's SSL/TLS -> Change Server Certificates link to install the cert.
I am having trouble with setting up an email account to set up the email I go to Mail > Create Email Address > and enter email address (info@example.com) and check the "access to control panel" and create a password and also check "mailbox" .
But in the email client, when I go to use SMTP and I enter the following info:
- SMTP Server: example.com - username: info@example.com - password: password I created above - port 25 - user TLS
I get this error: Your other email provider is responding too slowly. Please try again later, or contact the administrator of your other domain for further information.
I have just install on a new server plesk 12.0.18 Update #7 on centos 6.5 final.Added new hosting for the domain on a dedicated IP. All works fine (website, incoming mails etc) apart from outgoing mails.Both webmail (roundcube) and other mail software (outlook 2010, 2013 , android phone etc) outgoing mail i can't get to work.
I have attached screen from webmail with SMTP error (250) : Authentication failed..With Outlook it will allow me to set up account, test account setting... it say all all complete if i don't set secure connection (SSL)/requires authentication. But when you try sending mails you get the error: Your message did not reach some or all of the intended recipients.
Subject:test Sent:16/07/2014 15:13
The following recipient(s) cannot be reached:
'x@xxx.com' on 16/07/2014 15:13 Server error: '554 5.7.1 <x@xxx.com>: Relay access denied'
When you set the outgoing requires authentication/ advance SSL you get:Send test e-mail message: None of the authentication methods supported by this client are supported by your server.I have tried changing to some outgoing ports to no avail.
Is anyone successfully using cPanel with smtp port 587 and have a working email account?
After deciding that Plesk wasn't for me due to the lack of reference material in this and other forums, I had my hosting company, ServInt, delete my old vps and install a new one with cPanel.
Everything went fine until I configured my email. Just like with Plesk, I cannot access the smtp server via Outlook. I can ping it successfully, but it either terminates the connection or doesn't recognize the correct user name and password. With Plesk, it was a simple matter of enabling the use of port 587.
Not so with cPanel, at least for me. Even though the Exim service is enabled and another instance is enabled on port 587, I still can't connect. Thought it might be CFS, which is new to me with this install, so made sure it was disabled. Opened up a ticket with ServInt and even their techs can't get it functioning, so _they've_ opened up a ticket with cPanel.
Hence the title of this post, I can't beleive that I'm the only one whose had this problem before because blocking port 587 has been done by BellSouth/AT&T for many years now.
Nothing like having your company email down for over 6 hours to keep you up at night.
i have this weird problem of emails not gettign delivered and i am hosting with theplanet. Every email is sitting on the queue and not delivered.
i checked with dnsreport and it says
Timed out [Last data sent: [Did not connect]]
and my exim_mainlog shows
R=dk_lookuphost defer (-1): host lookup did not complete 2008-06-03 04:49:59 SMTP command timeout on connection
i have restarted exim, checked firewall and still i am unable to fix my problem!
update:
i again checked with dnsreport and my nameservers are failing
NS FAIL NS A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox,
it's due to a bug in their DNS Proxy, which must be disabled (31 Jul 2006 UPDATE: several years after being informed of this, there is a rumor that there is a fix that allows the Watchguard DNS proxy to work).
Example: User A sends an email to 100 people (using To,cc and bcc) . However the server needs to stop sending that message and cap a limit of 5 recipients per email
My company is going to launch four online retail site and in need for a dedicated server service provider that can provide us with room to grow from minimal traffic to possibly 2-5k traffic an hour.
A bit of background. We're a Canadian company with an eCommerce (Miva Merchant) website currently hosting with Hosting4Less out of California, and we're using Moneris Solutions' eSelectPLUS gateway to accept credit cards online.
Actually, we're not accepting credit cards online yet as we're trying to become PCI Compliant. At Moneris' recommendation, we've signed with Trustwave to take care of PCI Compliance verification. The problem is, that Moneris requires us to provide them with our third party service provider's (Hosting4Less) PCI Certification, and to this request, Hosting4Less has responded with the equivalent of "a deer in the headlights look". I've contacted two other hosting companies and neither of them seems to be able to provide evidence of their PCI Certification either. So, my question, is providing such certification something that a PCI Compliant web host should be able to provide to their eCommerce customers, or is Moneris asking for something that doesn't exist?
I have a Windows Mobile 6 (Blackjack II) phone that I am connecting to my cpanel VPS via Pop3.
I have a number of pop3 accounts setup to check for email every 30 minutes. However, every couple days the phone stops downloading mail and if I do a manual send and receive I get a "The Server Certificate is not valid. Continue Anyway?" with a yes/no. If I click yes, the email downloads and then the automated emails will work for several days and then the process is repeated.
Does anyone know how to either disable this check on the phone (no luck finding that yet), or to install the certificate from the cpanel mail server to the phone?
I'm running Parallels Plesk 12 on Debian GNU/Linux 7.6...I have a valid certificate for my mail server : mail.mydomain.tld but I don't find the place in Plesk 12 to put it.
I bought a RapidSSL certificate from Namecheap.com (the cheapest one), but after I installed it and everything, and went by their instructions, I get this message in Internet Explorer:
Quote:
The security certificate presented by this website was not issued by a trusted certificate authority.
The security certificate presented by this website was issued for a different website's address.
If you view any page on my site (https://www.hastyhost.com ) it gives you that. I'm a bit new to SSL certificates, so if you know the problem, try to example in simple terms
Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server.
Outlook 2013 complains about the SSL certificate when using email. Installing the certificate still doesn't stop the error/warning. What are my options?
Can I install on the plesk server a self-signed SSL cert and avoid the issues? Can I buy & install a single certificate for that one domain and resolve the issue but not affect others. Do I need to buy a SAN certificate for the whole server?
I am using apache as a reverse proxy, I have several site with http and everything is working fine. For the first time I have tried to configure with https port 443 with certificate, the problem is that it doesn't return to the browser the certificate that I have indicate in the "virtual host" but rather the default certificate of the site.
