[quote=468474:@Sascha S][/quote]
He may have it obfuscated in code, we just don’t know the details…
No different than having an API key for Mailjet etc embedded…
Can be read in memory just before the request goes online…
Maybe, but you won’t be blacklisted/blocked because you use “the account” from multiple locations … 
[quote=468478:@Sascha S]Can be read in memory just before the request goes online…
Maybe, but you won’t be blacklisted/blocked because you use “the account” from multiple locations … ;)[/quote]
As I said, it’s all about perspective. If you’re writing an app that is selling 20,000 copies a week then yeah, be careful. This sounds like a small bespoke app and the password sending is a backup method to a primary method failing. It might be 2 emails a year sent, we just don’t know.
I run a web hosting company (have done for 25 years), nobody blacklists your email because you send it from multiple locations. Think about how many people travel all over the world.
Isn’t that the point of this thread? That the OP got blacklisted? It’s not because of multiple locations by itself, it’s because they build up a risk profile. If your email account is used to send an email in the USA and, two hours later, used to send another email from India, from a different mail client, alarm bells will ring with the provider.
I suspect it’s not blacklisting per se, it’s more likely configuration. Gmail is quite picky about things like this.
We have support email accounts that are sending hundreds of emails a day from all around the world with the same address.
I always try to go the “better be safe than sorry” route. 
Thanks guys! All I want to do is get an email sent to the user with an unlock key. I don’t care really how it gets done…
The tricky dilemma I’m in is that gmail is not allowing users to get their email from my gmail account.
Right now it gets sent from the app. I never knew that is would be so complicated to send basically a confirmation email!
To be fair - I just did a complete upgrade of my product to 64 bit and a lot of bug fixes, new interface and registration overhaul.
I did have a PHP solution that worked for a couple of years (I paid 1 girl in Poland to di it for quite a lot of $$$). It broke and she couldn’t be bothered fixing it. So this is why I created this app sending email solution (which I thought would be great). I’m open to any ideas?
I just checked out Digital Ocean - I didn’t really see how to setup a Xojo app running system there 
[quote=468590:@Sean Clancy]Thanks guys! All I want to do is get an email sent to the user with an unlock key. I don’t care really how it gets done…
The tricky dilemma I’m in is that gmail is not allowing users to get their email from my gmail account.
Right now it gets sent from the app. I never knew that is would be so complicated to send basically a confirmation email!
To be fair - I just did a complete upgrade of my product to 64 bit and a lot of bug fixes, new interface and registration overhaul.
I did have a PHP solution that worked for a couple of years (I paid 1 girl in Poland to di it for quite a lot of $$$). It broke and she couldn’t be bothered fixing it. So this is why I created this app sending email solution (which I thought would be great). I’m open to any ideas?
I just checked out Digital Ocean - I didn’t really see how to setup a Xojo app running system there :)[/quote]
That PHP script is the best way to do it at a small to medium load. I expect it would be more than enough for you. Otherwise, an email delivery service such as the previously mentioned MailGun would be ideal. MailGun offers an SMTP server, so switching would be straightforward. But Id personally prefer using the web service instead of SMTP.
If you already have a server setup, can handle writing a pho script to do it, and that server has email authenticated with SPF and DKIM, then thats the way to go.
Otherwise, pay somebody to handle your delivery for you.
If you want to try MailGun, take a look at this Repo: https://github.com/1701software/MailgunX