New answers tagged gmail
This happens because Google recently implemented a policy change, which in their own words, is one in a series of changes to strengthen email authentication, and end any practices by Google products which break authentication. There are many options being suggested such as to change the ports for the smtp server, to enable "allow less secure apps" option ...
Set up a separate AWS account for your client, preferably billed directly to them. Problem solved.
Finally I've managed to solve the problem using this link: https://workaround.org/ispmail/squeeze/ssl-certificates Had to run those commands (as root): mkdir /etc/ssl/private/ openssl req -new -x509 -days 3650 -nodes -out /etc/ssl/certs/dovecot.pem -keyout /etc/ssl/private/dovecot.pem chmod o= /etc/ssl/private/dovecot.pem openssl req -new -x509 -days ...
You need to enable the setting called "Allow per-user outbound gateways", this can be found in the Admin Console under "Configure advanced settings for Gmail" and then search for "End User Access". Regards
This post needs to be updated again. I was having trouble with my mailx install on my CentOS 7 box. Mail would send but I was still receiving the "Error in certified: Peer's certificate issuer is not recognized." error. I found the solution here, had to translate it though. Here is a quick way to do it: # Create a certificate directory mkdir ~/.certs # ...
Top 50 recent answers are included