The application-password that you create will need to be added in two places in your Apple Mail app.
There is your Incoming Mail Server password, which is immediately visible under your account information.
Below that you can see the selection for Outgoing Mail Server (SMTP). The default will be Gmail. Click on the drop down box and select "Edit Server ...
Google is getting out of the business of sending email using domains that it does not administer, because it stands in the way of implementing rules that reduce spoofed email, such as DMARC. This also has the side effect of encouraging customers to host their email domains with Google.
Google is grandfathering existing email address configurations, but ...
I ran into this problem as well, and after a while determined it's related to the Keychain Access where the passwords are stored.
One forum I found suggested running a "Repair" of the login keychain (available via the "First Aid" menu item), which resolved the problem for some people. For me, however, the repair process found nothing to fix.
Finally, I ...
The solution in my case was to VPN to a location close to where my school was and then ping. It seems that outlook smtp is located close to where your account was opened, not where you are at the moment.
As my school was in Melbourne (while I am in Athens) before the VPN I was getting outlook.ms-acdc.office.com as the result of
Use an email sending service that's designed for sending out large numbers of notifications (such as Mandrill).
Don't use Gmail to send out lots of email - they view such traffic as suspect and will mark your account as requiring manual verification when they see such traffic.
Microsoft relies on various authentication filters to determine if an email is spam or not.
Common industry practices include reviewing email for the presence of a SPF Validation, Sender ID and DKIM records within email received.
The Sender ID Framework is an e-mail authentication technology protocol that helps address the problem of spoofing and phishing ...
On Google's support site, regarding 2-step verification, they speak directly of this issue and say this it more or less comes down to being sure that your check off the "remember this password" box
Quoted directly from Google's support site:
Soon after you turn on 2-step verification, you'll be alerted that your password is no longer working (see image ...
First of all you should not have posted the full log above. It contains your gmail username and password! So the very first thing to do is to change your gmail password.
Now to work on your problem:
If you are using 2factor auth, you will need to create an application password and use that to authenticate.
You will need to enable "insecure" apps as ...
I found that the only solution was to create another user, for which the primary email uses the alias domain.
In your case, connect to the admin console for g.mydomain.com.
First, remove the email alias you say you have set up for your first account.
Create a new user with the same name as the first account, and for its primary email address you should be ...
I understand that the domain registration is on Google Domains. Right? If so you can use Google Domains' Email forwarding feature.
Here is the Google help page how to set it up with detailed instructions https://support.google.com/domains/answer/3251241?hl=en
Email forwarding allows you to set up alias email addresses. An alias email ...
You'll need to enabled "less secure" app access to your account.
First, go to your Google Account. On the left navigation panel, click Security. Near the bottom of the page, in the Less secure app access panel, click on "Turn on access (not recommended)":
This will bring you to a new screen with a control to click on to enable this access:
I just found this question after having a similar issue. It turns out the issue was on my side, as the - I copied in the e-mail address wasn't actually a dash, but a ‐ (a unicode hyphen, \u2010)
If anyone is having a similar issue I suggest trying to re-type the e-mail address instead of copying it.
If you need to send your message now, try a different email service to send it.
Here is a thread from 2017 on the Official Gmail Help Forum UTF-8 Message not delivered. Unfortunately, it doesn't include a workaround, just several replies from Nina - Community Specialist, who have the Expert - Google Products badge, saying:
I believe there are two options:
The way Gmail sends mail from a normal free account using another domain is by logging in to the SMTP server you specify and sending the mail via SMTP. So if you cannot send mail via the SMTP server yourself, Gmail is not going to be able to either.
For this to work, you would need to get someone to host your domain on ...
To make this work, the aliased email address (firstname.lastname@example.org) needs to be configured as a "Send mail as" address in both your regular Gmail account (email@example.com) and your Google Apps account (firstname.lastname@example.org).
When you send an email from your Google Apps email alias while being logged in to your regular Gmail account, the following ...
Check the following
use Gmail SMTP server ;
Gmail SMTP server - requires authentication with your Gmail/Google
Apps account and password. Messages can be sent to anyone inside or
outside of your domain.
(not sure) enable Allow less secure apps: ON setting.
Send mail as: Coding Goûter <email@example.com> ;
Mail is sent ...
You haven't actually been sending mail through Google's SMTP relay. It's address is smtp-relay.gmail.com or smtp.gmail.com as seen here. The server at smtp.myuniversity.org would belong to myuniversity.org. You would need to contact whoever runs that server for help with this issue.
Additionally if Google's servers were rejecting your messages you would ...
The documentation at the link that you provided says:
Your other email provider has to provide authenticated SMTP support for you to use this option. We'll use TLS by default, or SSL if you enable it. Many email services that provide POP or IMAP support also offer authenticated SMTP support, and you can likely find your SMTP server configuration ...
This question has been answered here, but I'm unable to close it because of the bounty.
In short, you may use Gmail's SMTP server for your alias address, as long as you have enabled two-factor authentication.
Yes, Google suggests using the SMTP servers of @yourdomain.com.
If you are able to log in / read and send mail from there you should be able to use this process:
Log into your domain and find the SMTP server information
Add that to the Google Settings.
Note: all of my ...
You say you have already tried a VPN?
As I know one way would be to tunnel all here traffic through a VPN to one fixed location - thus each time she connects via SMTP it will appear she is only ever at one location.
I find that somehow the 'TLS Certificate' gets set. I change this to None, and it starts to work again.
In my case I use the following settings
TLS on port 465
As password, I use my new two-way identification password defined here: SmsAuthSettings
For users attempting to send email from a Google Apps account address via a different gmail address, while avoiding the "on behalf of" issue. Based on this answer, I can confirm that Google requires the following security setting change before you are allowed to "Send mail as" a different Gmail/Google Apps account.
Log into the account whose ...
I'm not able to find this page, seems Google change the place again... SMTP do not appear, and I can't find the "Allow users to send mail through an external SMTP when
configuring a "from" address hosted outside your email domains"...
I hassle with this for some time now and had the same problem as you:
Gmail appears to detect ...