Email Forwarding and Heroku Hosting

[githubgigmasters]

I am running into two problems.

My first problem is attempting to get my text messages to forward to Gmail. Te second problem is, ever since I have started attempting to setup email forwarding, my heroku hosted app seems to be crashing and won't let me log in. I get notifications from uptime saying my site is down. Error on the app is simply "Application Error"

Not sure if they are connected, but thought I would mention it. May be a limitation on the free tier of Heroku/MongoDB possibly?

For the Gmail forwarding, I am attempting to do the following settings:

Username: username@gmail.com
Password: mypassword123!@#' (password includes a lot of random special characters)
EmailFrom: username@gmail.com
EmailTo: simplelogin@catch-all-domain.com
SMTPServer: smtp.gmail.com
Port: 465
Secure

Is anything in this setup incorrect? I have also attempted to use port 587 without the secure box checked as well.

Logs from Heroku:

2022-07-09T17:13:28.047267+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/api/auth/get-update-version/" host=herokuwebpage request_id=6006f75e-7b27-48e0-9343-692216e23b5d fwd="publicIP" dyno= connect= service= status=503 bytes= protocol=https

2022-07-09T17:13:28.054434+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=POST path="/api/auth/get-signup" host=herokuwebpage request_id=830fef20-01e7-4b6c-89f2-ea1106f6bcc5 fwd="publicIP" dyno= connect= service= status=503 bytes= protocol=https

2022-07-09T17:13:29.234894+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=POST path="/api/auth/login" host=herokuwebpage request_id=45ea47a0-af3e-4b12-9570-fb9330a75373 fwd="publicIP" dyno= connect= service= status=503 bytes= protocol=https

2022-07-09T17:14:12.752323+00:00 app[api]: Starting process with command heroku logs --tail by user heroku@emailaddress

2022-07-09T17:14:15.761438+00:00 heroku[run.5525]: Awaiting client

2022-07-09T17:14:15.775305+00:00 heroku[run.5525]: Starting process with command heroku logs --tail

2022-07-09T17:14:15.893068+00:00 heroku[run.5525]: State changed from starting to up

2022-07-09T17:14:18.886242+00:00 heroku[run.5525]: Client connection closed. Sending SIGHUP to all processes

2022-07-09T17:14:19.130739+00:00 heroku[run.5525]: Process exited with status 127

2022-07-09T17:14:19.378079+00:00 heroku[run.5525]: State changed from up to complete

[getsean]

mailgun.com works great and they have a free option. Also check your outbound firewall rules

[githubgigmasters]

@getsean I am looking into mailgun now, I do not have any outbound firewall rules that would be affecting this, and I am seeing the same problem when running straight cell service.

I did just go into MongoDB and delete the forwarding email attempt. I did this by going to the Project, expanding my Database, expanding emails, and then deleting the entry. I then redeployed my Heroku project through the Heroku management page. My Heroku web app immediately was available again. Which leads me to believe there was some kind of a syntax error or something crashing the system with my email forwarding attempt.

[githubgigmasters]

So I seem to have gotten this to work with Mailgun.com
I had to hard reset the MongoDB and Heroku App multiple times though whenever I put settings in that didn't work.
I finally managed to get it working with the following:

Username: postmaster.....mailgunemail
Password: mailgunpassword
EmailFrom: postmaster....mailgunemail
EmailTo: Simplelogin@catch-all-domain.com
SMTPServer: smtp.mailgun.org
Port: 465
Secure: checked

I am currently getting my emails quarantined by SimpleLogin, but I am going to attempt to add my domain name to mailgun in order to avoid that.

[0perationPrivacy]

For gmail specifically, you need to go into your google account and allow "less secure apps"

[githubgigmasters]

Gmail no longer provides support for "less secure apps" at least not that I am seeing anymore.

[0perationPrivacy]

check this thread as well for smtp providers: #59
If the email is getting block, you need to verify it in the smtp provider, follow their process of verifying ownership of the "from" address. Otherwise it's considered spoofing and SPF will not validate and get put into junk.

[githubgigmasters]

I have gotten 100% online with mailgun and a catch-all domain. No longer getting messages sent to quarantine or junk by simple login. Just needed to get the entire domain verification system in place.
Thanks for your help!