This is what you need to do:

1. Select the Settings icon on the Home screen, then select Mail, Contacts, Calendars.
2. Select Add Account.
3. Select Other.
4. Enter your name, e-mail address and password. Select Save.
5. Select POP.
6. Enter your incoming mail server: mail.yourdomain.com
7. Username: your username @ yourdomain.com
8. Password: should be set already.
9. Enter your outgoing mail server: mail.yourdomain.com
10. Select Save.
11. Select Yes when the ‘Cannot Connect Using SSL’ message appears.
12. If presented with a SMTP certifcate warning, select Continue.
13. Select the Mail icon on the Home screen.
14. Select e-mail account to retrieve e-mail messages from your account.

Can’t send e-mail with Rogers?

First make sure the following settings are set:
1. Follow step 1 above and select your account.
2. Scroll down to Advanced.
3. Under Incoming Settings, set Use SSL to Off.
4. Set Server Port to 110.

You can also try using port 587 with Plesk, provided the Plesk configuration is set up to allow that port. I think it’s under the Server-wide Mail Preferences and is called “Enable message submission”.

Still doesn’t work?

1. Follow step 1 above and select your account.
2. Scroll down to Outgoing Mail Server.
3. Select SMTP.
4. Under Primary Server, select your domain account.
5. Set Server to Off. Go back.
6. Under Other SMTP Servers, select Rogers SMTP server.
7. Set Server to On. You should be able to send now.

For Step 6, you can also select smtp.gmail.com provided you have a Gmail account set up already.

That’s it

Since the fix isn’t published online, I’ll post my fix here.

I noticed quite a few posts mentioned the cURL ‘-k’ or ‘–insecure’ flag, which does not verify the SSL certificate (eg. if a self-signed certificate is being used). If you can’t verify a SSL certificate, then its authenticity is questionable. The ‘-k’ flag does NOT send communications in clear-text, as I previously noted (sorry!). That’s not something I approve of, nor something I would recommend to a friend or client.

So, what to do? First of all, I determined the path to the cURL CA bundle on the system.

grep -ir “curl” /etc
/etc/init.d/psa:CURL_CA_BUNDLE_FILE=/usr/share/curl/curl-ca-bundle.crt
…

From the output above, we determine that Plesk is looking for the cURL CA bundle in /usr/share/curl/ and that the filename should be curl-ca-bundle.crt.

Next, we need to download cacert.pem from http://curl.haxx.se/docs/caextract.html. I recommend using wget to download it to your server directly. You will need to rename the file to curl-ca-bundle.crt once it’s downloaded.

Copy curl-ca-bundle.crt to /usr/share/curl. If you get an error stating the path doesn’t exist, then you will need to create it using mkdir -p /usr/share/curl. Once the path exists, copy the file to the new path: cp curl-ca-bundle.crt /usr/share/curl.

This is where it gets tricky. Open curl-ca-bundle.crt in vim or your favorite editor and search for “Equifax Secure Global eBusiness CA”. Copy everything in the block, including that text and including END CERTIFICATE. We need to copy that block to one more file (search for ca-bundle.crt on your system): /usr/share/ssl/certs/ca-bundle.crt. Append the block to the bottom of the file. Remember to press ENTER after the last line. Of course, remember to ask your payment processor who their SSL vendor is and use the correct block.

Next, simply restart the Apache process: service httpd restart

That’s it. You should now be able to process transactions using cURL and SSL.