We're using hMailServer as a relay for devices, appliances, and applications that are not capable of sending their own messages. We just changed our server from simply sending messages to instead relay through Google (our G Suite environment) via "smtp-relay.gmail.com" and "SSL/TLS" on port "465". This would help improve the security/quality of the emails, so they would meet our SPF requirements and not trigger SOFTFAIL errors. We don't seem to be hitting any of Google's message quantity limits, but we are hitting authentication limits.
With nearly 30,000 messages per day passing through the hMail relay, Google started to send "RECEIVED: 454 4.7.0 Too many login attempts, please try again later. n10sm657166pjo.6 - gsmtp" messages. These seem to pass fairly quickly, but the email queue quickly builds up, and when their retry time is reached, the emails quickly flood out and re-trigger the warning message. It seems as though this may be due to hMailServer logging in separately for each individual message. Is there any way to get it to stay logged in or somehow slow things down a bit so that we're not hitting Google's authentication limit?
Any advice or suggestions are welcomed.
Use this forum if you have installed hMailServer and want to ask a question related to a production release of hMailServer. Before posting, please read the troubleshooting guide. A large part of all reported issues are already described in detail here.
2 posts • Page 1 of 1
You could just have hMailserver deliver to the final recipients directly, and not route through gmail at all, or deliver some directly, and by using routes and rules deliver SOME via the gmail relay
Just 'cause I link to a page and say little else doesn't mean I am not being nice.