GICT knowledge base
How to Use Google’s Free SMTP Server
Published
How to use Google’s free SMTP server as outgoing mail server? Yes Google’s Gmail offers a free SMTP server which can be used anyone who has Gmail account. Follow the steps given below to configure it.
1) Login to your Gmail account. If you do not have any Gmail account creates an account.
2) Click the button ‘Settings’.
3) Go to the option ‘Accounts and Imports’.
4) Click on ‘Add another email address you own’.
5) Enter the email address and click the option ‘Next Step’.
6) Click the button ‘Send Verification’ to complete the process.
7) Go to email account to set up SMTP server.
8) Go to the settings section and use the following details to configure the SMTP server.
Outgoing Mail (SMTP) Server: smtp.gmail.com
Use Authentication: Yes
Use Secure Connection: Yes (this can be TLS or SSL depending on your mail client)
Username: Gmail account
Password: Gmail password
Port: 465 or 587
Note : Google do have a mail sending limit if you are using this portable SMTP server. It’s 99 mails per day, per user accounts. If the limit is reached, it will be removed after 24 hours. So keep that in mind.
That is how we can use Google free SMTP server as outgoing mail server.
If you need any further help please reach our support department.
Related guides
How to Test Application Emails with Mailpit
Capture staging emails with Mailpit over a private connection. Inspect message formats and attachments without confusing capture with real delivery.
EmailHow to Test SMTP Login and TLS with swaks
Diagnose SMTP connectivity, TLS and authentication with swaks. Protect credentials and distinguish server acceptance from recipient delivery.
EmailResolving: This message was classified as rSPAM and may not be delivered
Resolve InterServer rSPAM rejections using the SMTP code and MailBaby rule details. Check authentication, security and false positives through support.
EmailHow to Check SPF, DKIM and DMARC Using Message Evidence
Diagnose email authentication using real message identities and selectors, DNS answers and alignment instead of guessed records or delivery assumptions.



