Add to Gmail
GMass changelog

Product Updates

A running record of the things we ship: new features, improvements, fixes, and the small details that make GMass better.

334 updates Latest: September 3, 2026
Latest
Custom tracking domain SSL monitoring fix: We fixed an issue that could cause GMass to incorrectly decide that SSL had stopped working on a user's custom tracking domain. Previously, temporary connection timeouts or HTTP responses such as 429 Too Many Requests could be interpreted as an SSL failure, causing GMass to unnecessarily switch the tracking domain back to HTTP and notify the user that their SSL certificate was no longer working. GMass now distinguishes actual SSL/certificate failures from ordinary HTTP errors and temporary network problems. Any valid response over HTTPS confirms that SSL is working, while timeouts and other inconclusive connection errors leave the existing SSL setting unchanged. SSL is now disabled only after GMass confirms a genuine SSL failure.
Faster launching for very large Google Sheets campaigns: Launching a campaign to a very large Google Sheets list is now much faster and more reliable. Previously, GMass could load the entire recipient list and build the full personalization map immediately when you clicked the GMass button — even when the campaign was large enough that it would simply be queued for background sending anyway. For campaigns using a single list with more than 10,000 recipients, GMass now performs only the lightweight checks needed to schedule the campaign and defers the expensive recipient expansion and personalization work until the background sender actually begins sending. This reduces launch delays and avoids excessive memory usage on very large campaigns, while smaller campaigns and unusual list configurations continue using the existing processing path.
Custom unsubscribe text formatting improvement: The HTML editor for custom unsubscribe content now includes an easy-to-find Size control, letting you change the font size of any text in your custom unsubscribe message.
**Campaigns can now be paused or resumed even if Gmail access has been lost:** Previously, pausing or resuming a campaign could fail if GMass no longer had OAuth access to the user's Gmail account. GMass was attempting to access the Gmail draft in order to update its paused label, even though that label change isn't critical to controlling campaign sending. Pause and resume operations now work independently of Gmail access, so users can stop a campaign immediately even if their Gmail connection is broken or needs to be reauthorized.
Custom tracking domain SSL reliability improvements: We’ve overhauled the infrastructure that manages HTTPS certificates for custom tracking domains. In rare cases, a certificate renewal retry could previously associate a certificate with the wrong private key, resulting in a public/private key mismatch. That could cause a bad SSL certificate to be deployed and HTTPS to stop working for that tracking domain. Certificates are now cryptographically validated before deployment to ensure the certificate and private key actually match, and renewal retries safely reuse the correct private key. We also migrated custom tracking-domain SSL to a centralized certificate system on newer infrastructure, so renewed certificates can be deployed instantly without modifying thousands of individual IIS bindings or temporarily disrupting tracking-domain traffic. The result is faster, safer renewals and significantly more reliable HTTPS for custom tracking domains.
**Faster personalized test emails for large Google Sheets:** Sending a test email from a large Google Sheets campaign is now dramatically faster. Previously, GMass could load the entire recipient list and personalization data — potentially 1 million rows — just to send a single personalized test message. GMass now retrieves only the test recipient’s matching database record and Google Sheets row, avoiding the full-list download while preserving the same personalization behavior.
Conditional logic spacing fix: We fixed an edge case with GMass’s automatic conditional-logic spacing cleanup. When a conditional block appeared inside an existing HTML section and the selected branch ended immediately before the next paragraph, GMass could sometimes add an extra blank line between the conditional content and the following always-visible content. This happened when the campaign already had spacing after the conditional block, but GMass added another spacer during cleanup. GMass now detects when the surrounding message already provides the needed separation and avoids adding extra spacing, so rendered conditional content flows cleanly into the next paragraph.
**Delivery Routes now recognize more email security services:** GMass can now automatically identify recipients whose mail is protected by Proofpoint, Proofpoint Essentials, Cisco Secure Email/IronPort, Broadcom/Symantec MessageLabs, Forcepoint/Websense, Trend Micro, and Sophos Email. You can create a Delivery Route for any of these services to force those recipients through Gmail or SMTP, or selectively disable open or click tracking. GMass identifies the service from the recipient domain's MX records, so one route can apply across every domain using that email gateway.
We've just launched a new website for GMass. It's been 8 years since we did a re-design, and this new site, especially the homepage, reflects the evolution of GMass over the last 8 years. It's no longer a simple mail merge tool -- it's a full blown email operations ecosystem for your entire organization.
A/B testing reports are now easier to read while results load and after they appear. GMass now shows an “A/B Test Data Loading...” message while the stats are being generated, and once the results load, the better-performing cells for opens, clicks, and replies are visually highlighted. Each metric is evaluated independently, so one variation can lead in opens while another leads in clicks or replies.
A/B testing improvements: Improved A/B testing behavior for campaigns testing 100% of recipients. These campaigns will no longer pause at the end to wait for a winning variation, since there are no remaining recipients to send. I also added better internal logging around A/B test pause decisions so it’s easier to diagnose exactly when and why a campaign reached its testing threshold.
GMass’s **Aggressive Bounce Handling** now more reliably detects unthreaded bounce notifications generated by our internal SMTP servers. Previously, these bounce messages could be missed because they retain the campaign’s original subject line rather than using a typical bounce subject such as “Delivery Status Notification” or “Undeliverable.” GMass now recognizes these internal SMTP bounce messages based on their sender, while still applying stricter subject-line checks to Google-generated mailer-daemon messages. This improves bounce-list accuracy for accounts with Aggressive Bounce Handling enabled, particularly when **Skip Sent** causes the bounce notification to arrive outside the original sent-message thread.
**Fixed “undefined” appearing in the campaign End Time field** We fixed an edge case where the campaign End Time setting could sometimes display the word “undefined.” GMass now avoids saving an invalid End Time value and automatically cleans up any bad value that may already be stored. A new version of the GMass Chrome extension, **version 6.0.44**, will soon be available in the Chrome Web Store with this fix. Active GMass users will receive the updated extension automatically.
GMass now handles invalid campaign **End Time** entries more gracefully. If an incorrectly formatted time is entered — for example, `22:00pm` — GMass will now show a useful validation error instead of allowing the send request to fail unexpectedly.
Dashboard improvement: Campaigns are now sorted by **Created, newest first** by default, so newly launched campaigns are easier to find. If you've chosen to sort by **Last sent** and have campaigns created within the last 6 hours, the dashboard now displays a notice explaining that those new campaigns may not appear near the top. You can click **Created** directly in the notice to instantly switch to the Created sort.
**Spam Solver now puts seed-test Spam results in context:** If 10 or more of your 20 Spam Solver test emails land in Spam, GMass now reminds you that seed-account placement does not necessarily predict what will happen with your real recipients. Email delivery is recipient-specific, and inbox providers learn what types of email each person normally reads. GMass uses AI to analyze your campaign and describe its topic in a short phrase, then explains that recipients who regularly engage with email about that topic may still see your campaign land in the Inbox—even when our seed accounts don't.
**Support form reliability improvement:** We’ve made the GMass support form more reliable, particularly for the occasional submission that previously failed while communicating with our support-ticket system. Support requests are now processed on newer infrastructure with automatic retries for connection failures, and we’ve also hardened attachment handling so a missing filename or failed attachment can’t prevent the rest of a support request from going through.
* **Campaign Deep Analysis:** Campaign reports now include a new **Deep Analysis** feature that goes beyond the headline open, click, bounce, and block rates to investigate the underlying campaign activity. It looks for patterns such as automated opens, click scanners, privacy/prefetch activity, unusual timing, delivery issues, and other anomalies, then summarizes the most important findings with supporting evidence and confidence levels.
**Transactional email unsubscribe control:** GMass now lets you choose whether transactional emails should respect your account’s unsubscribe list. A new account-level setting under **Transactional Platform** can allow transactional messages to reach recipients who previously unsubscribed, which is useful for essential messages like receipts, password resets, and account notifications. The setting applies to both transactional API calls and messages sent through the GMass SMTP relay; bounced addresses are still suppressed.
Multi-account dashboard switching improvement: Users with access to multiple GMass dashboards can now switch accounts from a dropdown at the top of the dashboard, with the main account clearly identified. These users now land directly on their main dashboard after logging in instead of seeing a separate account-selection screen.
**Direct links for Google Sheets exports:** After exporting campaign data to Google Sheets, GMass now provides a clickable link that opens the newly created spreadsheet immediately. No more searching through Google Drive to find your export.
Dashboard search improvements: The Clear button now clears text entered in the main search box along with all advanced search fields. Additionally, the X button for clearing active filters now appears when you search using only the main text box, making it easier to reset your search and return to the full campaign list.
**More precise scheduled campaign statuses:** The single-campaign report now shows how long until a scheduled campaign begins sending—such as “5 minutes from now” or “2 hours from now”—instead of simply saying it’s scheduled for later.
Campaign report shortcut: GMass confirmation messages now include a direct link to your campaign report after your emails have been processed or when a scheduled campaign is about to begin sending. This makes it easy to jump straight into the live report and watch opens, clicks, and other activity without first navigating through the dashboard.
Copy buttons added throughout campaign reports: We’ve added subtle copy buttons throughout the GMass dashboard and single-campaign reports, making it easy to copy campaign subjects, IDs, account and recipient email addresses, IP addresses, shareable report links, and click-tracking URLs. Just click the copy icon beside any supported value, and a green checkmark confirms it’s on your clipboard.
**Campaign report stats display fix:** We fixed an issue where campaigns that had not started sending could display “NaN” in the report’s rate boxes. Reports now show the proper empty state until recipients exist, then calculate percentages normally once sending begins.
Campaign report fireworks performance fix: We fixed an issue that could cause first-open fireworks animations to accumulate when a campaign report was left open in the background for an extended period. When returning to the report, hundreds of effects could appear at once and significantly slow down the browser. GMass now pauses fireworks while the report is hidden, limits their frequency, and automatically clears the animation so long-running reports remain responsive.
Dashboard account-switching fix: We fixed an issue that caused saved search filters and team selections to carry over when switching between GMass accounts, sometimes resulting in an unexpectedly empty dashboard. GMass now saves these dashboard preferences separately for each account, so every account opens with its own previously selected view.
MultiSend API enhancement: We’ve expanded the GMass Campaigns API to give developers more control over MultiSend campaigns. API users can now skip the primary sending account entirely or set a separate MultiSend sending limit for the primary account, matching options already available in the GMass UI. Existing per-account MultiSend weights continue to work using the email|weight format.
**“Everyone” auto follow-up timing fix:** We fixed an issue affecting auto follow-up stages set to **Everyone** when some recipients had skipped the immediately preceding stage. Those recipients could be incorrectly excluded or have their timing calculated from a stage they never received. GMass now handles these recipients correctly when the **“For ALL-based auto follow-ups, skip prior stage check”** setting is enabled in Auto Follow-up Settings, using the appropriate earlier campaign as the timing reference instead of requiring the recipient to have received the prior stage.
Auto follow-up split-stage timing fix: We fixed an issue that could cause later auto follow-up stages to calculate their timing incorrectly when a previous stage had been split into multiple campaign IDs. This would cause some later-stage auto follow-ups to not send. GMass now checks all campaign IDs associated with the prior stage, so each recipient’s next follow-up is scheduled based on when that recipient actually received the previous stage.
Embedded image template fix: We fixed an issue that could cause multiple pasted images in a GMass campaign or template to display as the same image after the template was reloaded into a new Gmail Compose window. This could happen when Gmail assigned identical filenames, such as image.png, to several inline images, causing later uploads to overwrite earlier ones. GMass now assigns each embedded image a unique filename before storing it, so all images remain distinct and display correctly.
AI-powered scam detection for transactional email: We have integrated AI-powered scam detection directly into the SMTP conversation for GMass transactional email. The system can analyze a transactional message for signs of fraud or deception before accepting it for delivery and reject suspected scams during the same SMTP session. This applies only to transactional email sent through the GMass SMTP relay—not regular GMass campaigns.
New-account transactional email limits: To reduce abuse of GMass’s transactional email service, newly created free accounts can now send up to 50 transactional emails during a seven-day trial period, beginning with their first transactional email. Once either limit is reached, the account must upgrade to continue sending through the GMass API or SMTP relay. This restriction applies only to accounts created now and in the future.
Campaign daily-limit SMTP fix: We fixed an issue affecting campaigns approved to finish sending through GMass’s in-house SMTP server after reaching a user-set daily limit. When the user chooses to send the remaining emails immediately, GMass now removes that campaign-level daily limit so the rest of the campaign can send now as intended. Campaigns stopped early by Gmail’s limits continue to respect any daily limit set by the user.
Amazon SES SMTP connection fix: We fixed an issue that could prevent users from sending via Amazon SES through GMass’s SMTP feature. An outdated certificate trust chain on one of our servers could incorrectly reject Amazon’s valid TLS certificate. Amazon SES SMTP connections now validate and send normally.
Campaign reporting dashboard fix: We fixed an issue where campaign statistics could stop updating in the web-based dashboard for users who had turned off campaign report notifications in Gmail. Web-based reports now update normally regardless of the Gmail notification preference, while disabled Gmail notifications remain off.
Friendlier click-tracking links: GMass now supports cleaner, friendlier click-tracking links for both regular campaigns and transactional emails. Instead of long tracking URLs with multiple query-string parameters, tracked links can now look like https://ajaygoel.fmailroute.net/wordzen_contact_xduqmatr or, with a branded tracking domain, https://track.wordzen.com/contact_p47izv7q. Existing click-tracked links continue to work normally.
Click-tracking redirect fix: We fixed an issue where click-tracked links could redirect incorrectly if the original link was entered as a bare domain like www.wordzen.com instead of a full URL like https://www.wordzen.com. GMass now handles these links properly and redirects recipients to the intended website.
Long-running auto follow-up scheduling bug fix: We fixed an issue affecting campaigns whose cumulative follow-up schedules extended beyond 255 days. In some cases, the timing values for stage 9 and later could roll over to smaller numbers, causing follow-ups to become eligible earlier than intended. We corrected all affected campaign schedules, and long-running follow-up sequences now retain their intended timing.
Inbound email routing bug fix: We fixed an issue that could prevent GMass from recognizing certain recipient addresses (replaced gmail.com addresses) when the address’s username contained a period but the corresponding routing domain did not. These messages are now matched to the correct GMass account and processed normally.
MultiSend bug fix: We fixed an issue where a campaign could be marked complete if none of its selected sending accounts were currently eligible to send. MultiSend campaigns in this situation now preserve the campaign draft and automatically resume later.
GMass API documentation fix: The allowedDays campaign setting now correctly explains that days should be submitted as full weekday names, such as “Monday,Wednesday,Friday.” The previous documentation incorrectly indicated that numeric day values should be used.
Transactional API improvement: Transactional emails sent through the GMass API now honor your configured Message Routes. This also means accounts sending to Mimecast recipients can now automatically use the appropriate sending method, including OAuth or SMTP as configured, matching the behavior of regular GMass campaigns.
MultiSend bug fix: Report notifications (such as open notifications) are now determined by the settings of the account that owns the campaign, rather than the MultiSend account that actually sent the email. Previously, if an email was sent through a MultiSend account, notification preferences from that sending account could be used instead of the campaign owner's settings, causing notifications to be sent (or suppressed) incorrectly.
Extension version 6.0.43 has been published. This version has improvements to the experience when using the GMass button to reply to an email. Now, the "Scheduling" section includes the ability to select certain days. Additionally, when using Auto Follow-ups, the Number of Days is now a "sticky" setting that will persist the next time you either open a new Compose window or reply to another email.
MultiSend daily limits now apply correctly when creating drafts. Fixed an edge case in MultiSend where campaigns set to create Gmail drafts, rather than send immediately, did not always distribute drafts across multiple sending accounts according to each account’s daily limit. For example, if a campaign was limited to 10 drafts per day and two MultiSend accounts were each limited to 5 per day, GMass now correctly creates 5 drafts in each account instead of creating all 10 in one account.
Rate-limit retry bug fix: In certain situations, campaigns that hit a Gmail rate-limit error while also being configured to auto-push through SMTP could retry too soon instead of waiting for the proper retry window. This could cause repeated failures and repeated “We pushed your GMass campaign through your SMTP server” notifications. This is now fixed, so campaigns in this situation wait at least an hour before retrying.
Foreign character bug fix: We fixed an issue where certain non-English characters, such as accented letters in Spanish, French, and other languages, could appear garbled in some GMass-sent emails. Messages containing international text now preserve those characters correctly when sent.
Major click-tracking bug fix: We fixed a long-standing issue that could occur when a message route disabled click tracking for a campaign. In that scenario, GMass should have left the original URLs alone, but in some cases the URLs in the final email could become malformed. This is now fixed, so campaigns that disable click tracking through a message route preserve URLs correctly.
SMTP routing bug fix: We fixed an issue that could occur in campaigns using system SMTP routes, such as special routing for Mimecast recipients. In some cases, after GMass routed one recipient through a specific SMTP server, later recipients could also be sent through that server even when they should have used a different sending path. This is now fixed, so each recipient is sent through the correct SMTP route based on the campaign’s routing rules.
Affiliate sign-up bug fix: We fixed an issue where some users signing up through the affiliate flow could have their shared tracking-domain setting incorrectly set to 0. This could leave the account without the proper default shared tracking-domain configuration. Affiliate sign-ups now correctly receive the expected tracking-domain setup during account creation.
MultiSend enhancements for SMTP sending routes: GMass now handles MultiSend campaigns more intelligently when a domain- or service-based route, such as a Mimecast route, requires sending through SMTP. Only the sending routes tied to the primary account are considered. If an SMTP route applies, the message will send through the primary account, even if that account is not selected in the MultiSend account list. For auto follow-ups, however, GMass preserves the original sender when appropriate: if the original email went through account B and an SMTP route was added later, between the original send and the follow-up, the follow-up will still go through account B to maintain continuity with the original message.
Auto follow-up bug fix for hourly recurring campaigns with End Times: If a campaign was set to repeat hourly but also had an End Time, GMass could incorrectly treat the allowed sending window as a moving target. In some cases, this caused auto follow-up stages to never trigger for certain recipients, even though they were eligible to receive the next stage. This is now fixed, so hourly recurring campaigns with limited sending windows correctly trigger their auto follow-up stages.
New setting: Aggressive Bounce Detection. In some rare cases, Gmail bounce notifications are not threaded to the original sent message, which means GMass’s normal bounce detection may not be able to connect the bounce to the campaign. With Aggressive Bounce Detection enabled, GMass scans for these standalone bounce notices, extracts the bounced email address, adds it to your bounce list, and labels the message under “GMass Reports → Bounces.” This helps prevent future sends to addresses that bounced, even when the bounce can’t be tied back to a specific campaign’s stats.
Personalization improvement: You can now escape curly brackets in GMass campaigns. Since GMass uses curly brackets for personalization tags like {FirstName}, there were cases where users needed to include literal { or } characters in an email without triggering personalization. This is now supported, making it easier to include things like code snippets, examples, formulas, or text that naturally contains curly brackets.
Bug fix for Transactional Email click-tracking reports: In some cases, when opening the click-tracking statistics page for transactional emails, the report could show a runtime/server error at the top of the page, even though the actual tracking data was still loading farther down. This was caused by a dashboard component trying to load campaign-specific click aggregate data on a transactional email report. This is now fixed, so transactional click-tracking reports render cleanly.
New setting: Auto fix line spacing for conditional logic. This new setting is available in the dashboard under "Other" and is an account-wide setting. It normalizes the line breaks around blocks of conditional logic code so that you can space out your conditional logic code without having excessive line spaces show up in the rendered email.
Dashboard bug fix: Some campaigns that were actively sending did not show the Pause button in the dashboard, even though the campaign was running and should have been pausable. This made it difficult to stop a campaign mid-send if there was a problem, such as a tracking-domain issue or other sending concern. This is now fixed, so running campaigns properly show the Pause button again.
GMass Transactional API improvement: The Transactional API now supports Cc recipients when MessageRaw is passed in. Previously, when sending a raw MIME message through the API, Cc recipients included in the raw message were not handled properly. Now, GMass recognizes and sends to the Cc recipients included in MessageRaw.
Bug fix for a rare account setup issue involving tracking domains: In rare cases, a database timeout during account setup could result in a user’s account not being assigned a shared tracking domain. When that happened, the user could run into an internal error while trying to send a campaign, because GMass could not determine which tracking domain to use for opens and clicks. This has now been fixed. We also found and repaired a few hundred older accounts from over the years that had been left without the proper shared tracking domain setting.
Bug fix for randomized sending order: In some cases, campaigns set to use “Randomize” for Sending Order were still sending from the spreadsheet in top-to-bottom order. This could cause messages to the same domain to go out together instead of being spread throughout the campaign. This is now fixed, so randomized sending order properly shuffles recipients before sending.
Bug fix with hourly recurring campaigns that have end times: If you created a recurring campaign set to run every hour between specific hours, such as 8 AM to 4 PM, and the campaign reached the end of its sending window without sending any emails, the next scheduled run could be pushed 24 hours ahead instead of continuing on the proper hourly schedule the next day. This is now fixed, so hourly recurring campaigns with end times recur correctly within their scheduled sending window.
Bug with with Preview Text and Friendly Name: When you loaded a Template from the campaigns dropdown, if that campaign had Preview Text or a Friendly Name associated with it, the fields would populate in the Settings box, but upon clicking the GMass button, those settings would not apply to the new campaign, unless you made a change to either field. This is now fixed, such that no editing needs to be done to the field in order for the settings to apply to the new campaign you're working on. This is fixed in Version 6.0.42 of the extension.
Extension bug fix: When you loaded a Template from the campaigns dropdown, if that campaign had Preview Text or a Friendly Name associated with it, those settings would populate in the Settings box but would not always stick when the campaign was saved. This is now fixed, so the Preview Text and Friendly Name from the loaded Template are properly applied and saved.
Dashboard bug fixes: When certain users used the "Search" function in the dashboard, that would sometimes result in an error and the search results wouldn't display. Specifically, if an apostrophe was used in search criteria, or the dashboard was sorted by the "Polls" metric, then an error would be thrown. This is now fixed.
Improvements to custom Labels: It's always been the case where if you applied a custom Gmail Label to your campaign's DRAFT, that same Label would be applied to all of the emails in your SENT folder as the campaign is sending. But in certain scenarios, the Label would fail to apply to the SENT emails, such as if you sent via SMTP or if you created DRAFTS first and then clicked a link to send. Now, custom Labels will be applied in all sending scenarios.
Personalization bug fix: If using a Sheet with Cc or Bcc columns for personalization, if the SUBJECT or BODY of the email campaign also contained the string "Cc:" or "Bcc:", the Cc and Bcc functionality would fail. This has been fixed.
New Feature: Open Tracking Hardening. You can now "harden" the open tracking pixel in your sent emails. This feature prevents you from triggering your own opens when you open up a sent email from your SENT folder in Gmail. It works by replacing the pixel for emails in your SENT folder with a dummy pixel instead. Your actual recipients still receive emails with the normal open tracking pixel. This is an account-level setting that can be accessed from you Dashboard --> Settings --> Other.
New Feature: AI Templates. You can now use AI to generate custom HTML templates for newsletters and email marketing campaigns. Instead of picking from a fixed gallery, click the AI icon in the settings box and open the new Templates section—describe the design you want (layout, colors, sections, etc.) and GMass will build it for you on the fly. You can also use it to modify an existing template by describing changes (for example, “change the background to green”). This feature is designed for users who send visually designed emails, rather than plain-text cold outreach.
Dashboard improvements: The Campaigns dashboard now combines Current and Previous campaigns into a single view with improved search and column sorting (defaulting to Last Sent, newest first). Recurring, paused, and “sends next” campaigns are color-coded so they’re easier to spot at a glance, and archived campaigns are hidden by default but can be viewed with a new “Is Archived” search filter and clearer archive/unarchive buttons. Column headers no longer wrap, campaign details are organized into cleaner chips, and we’ve removed the social sharing buttons for a less cluttered layout. Filters are now more obvious, can be cleared with one click, and your sort/filter settings are remembered so your preferred view sticks between visits.
AI SMTP Bug Fix: Applications to use the in-house SMTP server had been failing since November 7 due to a bug in code. This is fixed.
From Replacement Improvements: If you're using the GMass SMTP server, and you haven't set up DKIM, then your From address is likely being auto-replaced. Before, "alias" From addresses weren't being replaced properly. The replaced-address was based on the Google account's address rather than the true "From" address of the campaign. Now it's based on the true "From" address of the campaign. More info: https://www.gmass.co/blog/from-address-replacement/
Spam Solver bug fix: If your "Preview Text" had an apostrophe in it, the Spam Solver would fail to load. This is fixed now.
Report bug fix: The "Opens by time" chart on the single-campaign report page was erroring out due to a time zone bug if you weren't logged in when viewing the report page. This is fixed.
Tracker Blocker major fix: This extension, which blocks the GMass tracking pixel, so you don't trigger it yourself when opening up emails from Sent, had not been working for the last year. We just revamped it and it's working again now.
Account bug fix: If you are on the Professional plan, the wrong plan was being shown in the "account settings" section.
Extension bug fix: From Address selection now behaves correctly. This version fixes a longstanding issue we've had for years, where if you had multiple From Addresses set up in your Gmail account, if the LAST change you made to the Compose window was to set your From Address, and then you hit the GMass button, the From Address you chose was NOT used. You had to make at least ONE more change to the subject/message after setting the From Address, in order for the correct From Address to be used. This is now fixed. NOW, you can set the From Address as the last thing you do before hitting the GMass button. Now, this behavior is corrected — you can change your From Address last, and GMass will send from the correct one. Technical context: Gmail auto-saves Drafts when modifying recipients, subject, and message content, but not when changing the From Address. We had solved this years ago under InboxSDK, but when moving to GMassSDK, the fix did not carry over. This update restores that correct behavior.
Reporting improvement: The single-campaign report page has been improved. 1) It is now responsive and looks great on mobile. 2) New icons added for the open-tracking live feed for the GoogleImageProxy and the Apple MPP User Agents. 3) Fireworks launch whenever there's a first-time opener.
Open tracking accuracy improvement: When you have "open tracking" turned ON, and an email bounces back, traditionally opening up the bounced email would also open the original sent email underneath it, which would cause the open-tracking pixel to fire, which would then register an "open" for the recipient that just bounced. Now, however, emails won't get counted as "opens" if they bounce.
Reporting improvement: The single-campaign report page has been improved with 20+ changes. Better colors, spacing, and alignment now make this page more user friendly. Additionally, you can now see how your open rate, click rate, and reply rate, changes day by day for a multi-day campaign.
Bug fix for "send test" feature: When you used the "Send Test" button with auto follow-up stages selected, sometimes only the first email would send, and the auto follow-ups would not send as part of the test. This happened if you had "Skip Holidays" or "Choose specific days" enabled and the current day was either a holiday or not in the selected days.
AI SMTP: Sometimes the call to the OpenAI API fails when a user requests a push through our SMTP server. Before, this left the campaign in a "declined" state. Now, the user can reload the page to try again.
AI SMTP: Alias addresses are now supported. If you send from an "alias" address rather than your main Google account, you can still request to push a campaign through our SMTP server, and the domain of the "alias" will be analyzed for DMARC and DKIM compliance, which will then determine if the campaign can be sent with the actual alias "from" address or the GMass "replaced" address.
AI SMTP: We've added some limits to how many emails can be sent when the AI decision maker approves a campaign to be sent over our SMTP server.
AI SMTP: For users applying for permanent use of our SMTP server, in case of rejections, the AI-generated reason will now be emailed to the user.
Dashboard bug fix: For cancelled subscriptions with time still remaining on the account, the active plan "end time" was sometimes showing incorrectly. This is now fixed.
Campaign sending fix: Some campaigns were erroring out with this message: "System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive." These campaigns will be auto-retried, so that no action is required from the user.
AI SMTP: For users who send through our SMTP server and who have not yet set up DKIM, GMass now assesses whether ther user is a "bulk sender", as defined by Google, in determining whether to use the From-Address-Replacement system or not.
AI SMTP: Bounce processing was not working for Workspace users who had campaigns pushed through our SMTP server and were using the GMass From-Address-Replacement system. This is now fixed.
Extension bug fix: When you choose "Send as replies", the first option is supposed to be "Last conversation with recipient", but that option has been missing since June 2025, when unlimited auto follow-up stages was added. That option is now back. The fix is in version 6.0.39 of the extension.
AI SMTP: When requesting an SMTP "push" for an individual campaign, the page is now stateful. You can now reload that page and see the current state of the request.
AI SMTP: Now if a user is rejected by the AI decision maker, a detailed rejection notice will be shown to the user on screen and emailed to the user.
AI decision making for SMTP requests: Requests to push a campaign over our SMTP server, and requests to send through our SMTP server permanently, are now handled by AI, and decisions will be rendered instantly.
DMARC bug fix: The email analyzer, at gmass.co/analyze, sometimes reported that a DMARC record didn't exist when it actually did exist. Specifically, if the From Address contained a sub-domain, as do the "from" addresses that GMass generates when the Gmail-from-address replacement system is enabled, then our DMARC record lookup code was only querying the TXT record for the full sub-domain instead of the organizational domain also.
Invoices improvement: The "Invoices" page in the dashboard now shows the 100 most recent invoices instead of only the 10 most recent.
Auto follow-up bug fix: For stages where the "Days" parameter was set to higher than 255 days, in some cases, the follow-up stage went out earlier than the set number of days. This was due to a "tinyint" rollover bug for values higher than 255. So, if you set your "Days" to 268, the stage may have sent (268 - 255) = 13 days after the campaign instead of 268 days after the campaign. This only happened in certain cases though, not all cases where the "Days" was higher than 255.
Dashboard enhancement: The purple fly-out areas for each of the main metrics (Recipients, Opens, Clicks, etc.) now includes the Date column, and each column is sortable by clicking on the column header.
Firewall fix when deleting multiple unsubscribes/bounces: If a user deleted multiple rows of unsubscribes or bounces from the "Settings" section of the dashboard, that was triggering the threshold for "too many requests" on our firewall, which would then prevent sending for a short period of time. This has been corrected in our firewall.
View message bug fix: If a user shared a campaign templates with another account, and then that account used that template in an auto follow-up stage and clicked the "eye" icon to view the message, an error would result. If the user attempted to view the message enough times, then the error threshold of our firewall would be triggered, and that would prevent sending for a short period of time. This is now fixed.
Personalization bug fix for "instant" Sheet campaigns: In some cases, campaigns connected to a Google Sheet that used the Apps Script provided by GMass to detect new email addresses instantly, which would then trigger the campaign, would have personalization fail for the new rows, if multiple new rows were added in succession in a short period of time.
Campaign OAuth connection error bug fixed: When campaigns are first processed, an initial check is performed to make sure the OAuth connection to the Google account works. Some campaigns were erroneously erroring out, claiming an invalid OAuth connection when in fact the connection was intact. Rather, a temporary network error was occurring. Still though, GMass was requesting the user to "take action" by re-establishing the account conection and clicking the campaign "reset" link to fix what was being reported as an OAuth error. This has now been corrected such that if this temporary network occurs, the campaign is re-tried 10 minute later rather than requiring the user to re-connect and click the "reset" link.
AI content generation bug fix: Sometimes when using the OpenAI tool to generate the Subject/Body/Auto Follow-ups from a prompt, the text "Subject: " would appear in the subject line, the text "Body: " would appear in the body, and each follow-up stage would be labeled with "Follow-up 1", "Follow-up 2", etc. This won't happen anymore.
Extension update: Version 6.0.38, which is currently being approved by Google, will include an enhancement where the OpenAI content generation tool for the Subject/Message/Auto Follow-ups will save previously used settings in the form. The prompt, number of sentences, whether to generate auto follow-ups, and how many stages of auto follow-ups will now remember the last used choices.
GPT-5: Several areas of GMass that use AI-based content generation, such as the SpinMax feature, have been updated to use the new GPT-5 model.
API validation: Validation added when submitting campaigns via the API such that an auto follow-up stage cannot be added unless the prior auto follow-up stage is present. For example, you now CANNOT submit a "Stage 9" unless "Stage 8" is also present. If you do this, an exception is thrown.
Bug fix for auto follow-up calendar view: Campaigns that had mixed auto follow-up types, such as Stage 1 = No Opens and Stage 2 = No Clicks for example, had an auto follow-up calendar view that was inaccurate. Stage 1 would be broken out into two batches, and the calendar view would show sending to openers even for Stage 1 on the day that Stage 2 should go out. This is fixed.
Auto follow-up calendar view enhancement: Weekday name added to auto follow-up calendar view.
Bug fix for campaign recipient count in dashboard: For campaigns where a "delay" has been specified between recipients, only while actual sending, the main dashboard view would display an inflated recipient count. The recipient count would update to the accurate count after sending was completed, but during sending, it was inflated. This has been fixed.
API and the first 8 auto follow-up stages: Added parameters "stageOneThread", "stageTwoThread", etc. to specify "same" or "new" thread for each of the first 8 stages, to match the settings available in the UI. Default is "same". Only applies if a custom campaign ID is specified for the content of the auto follow-up. When the "stageXCampaignText" is supplied, it's always sent as part of the same thread.
API and auto follow-up stages: The API, which previously only allowed submitting up to 8 stages of follow-ups with a campaign, now supports unlimited stages, just like the UI does. Use the new input parameter "additionalStages" to specify more than 8 stages with the /Campaigns endpoint.
Auto follow-up calendar view: Improvements and bug fixes. It will now show the schedule for stages 9 and beyond. Days shown will be more accurate and will now reflect whether the user has "Count only selected days of week" on or "Strict count of days between stages" on. Additionally, it will enforce the same spacer logic as actual auto follow-up sending, where two stages of follow-ups can't go out within 16 hours of each other.
Speed improvement for auto follow-up stages 9+: Previously, our auto follow-up processor was taking an inordinate amount of time to process stages 9 and higher for a campaign, due to an inefficient algorithm. This would result in stages 9+ sending 1-2 hours later than they should have. This has been addressed.
Auto follow-up display fix in dashboard: Clicking the auto follow-ups + symbol for a campaign row in the dashboard expands the area underneath to show the campaign stats for each auto follow-up stage. Previously, only stages 1-8 were being shown. Now stages 9+ will also be shown in the dashboard.
Auto follow-up incorrect content bug for stages 9 and higher: If you had set up stages 9 and higher, and you inputted both text and chose a campaign from the dropdown, the content from the campaign would send EVEN IF you had selected the radio button to use the text. This is now fixed.
Auto follow-ups minimum gap bug fix: In certain rare scenarios, an auto follow-up stage would send merely an hour after the prior stage sent. GMass has a safeguard of requiring at least 16 hours before two consecutive auto follow-up stages are sent, but a bug caused that safeguard to fail. The bug is now fixed.
Auto follow-ups UI bug fix: If you were setting your auto follow-up stages to use a campaign from the dropdown, rather than typing text, and then you loaded up a saved campaign by opening up its DRAFT in Gmail, the dropdowns would show the LAST SAVED options across your account rather than the SPECIFIC CONTENT for that particular campaign. The bug was only in the UI though -- on the backend, the right campaigns were saved and being used for each auto follow-up stage. The UI bug has been fixed.
We've removed the "share" widget that pops up on the campaign report if your stats are good. Some users found it annoying.
Extension suppression bug fix: When loading a campaign template, if you chose to also load the template's settings, and the settings included suppression settings, the suppression section of the settings box wasn't expanding automatically to show the settings. This has been fixed in version 6.0.36.
Bug fix: “Dangerous request” error when angle brackets were used in Subject lines. A security rule on our web server mistakenly flagged < > in Subject lines as unsafe, blocking sends and surfacing an IIS “potentially dangerous Request” error.
Extension bug fix: After we rolled out unlimited follow-up stages a few days ago, the "stickiness" for auto follow-up settings stopped working. Meaning, if you launched one campaign with particular text in the auto follow-up boxes, or custom campaigns in the dropdowns, those are supposed to be pre-set for you when you launch a Compose window the next time, and those settings weren't being pre-filled. That's fixed in the latest extension version 6.0.35.
New feature -- unlimited auto follow-ups! The extension has been updated to version 6.0.34 in the Chrome Web Store, and this version has the ability to send an unlimited number of auto follow-up stages.
Extension bug fix for "Send Test" when testing the full sequence: If the Settings box was set to "Create Drafts" and "all at once", and the user's account had an SMTP server configured, even if the "Send Test" button was configured to "Send email" rather than "Create Draft", the main settings box settings would still interfere, and this would result in only the primary email and the first auto follow-up being sent, rather than all auto follow-up stages.
Minor bug fix in sending notifications for gmail-dot-com users who were sending "from" a non-Gmail alias and ran into limits: The "sending complete" notification was erroneously mentioning the "from address replacement" system that GMass has in place for gmail-dot-com accounts, rather than directing the user to set up DKIM to be considered for re-routing through our internal SMTP server.
Bug fix for gmail-dot-com users, sending through one of our SMTP servers, who created DRAFTs first: Emails weren't being DKIM-signed and they were sending "from" a combination of *.gmuser.net and *.gmusers.net instead of just *.gmuser.net. Additionally, the emails logged to the account's SENT folder would still show the "From" as the gmail-dot-com address rather than the replaced @xxxxx.gmuser.net address. This is all fixed.
New reporting feature: Live campaign status + speed. The single-campaign report page now shows a real-time campaign state badge (Sending now with animated arrows, Paused, Scheduled, or Error). When a campaign is actively sending, you’ll also see a live-updating “emails per minute” counter that smoothly counts up or down every 10 seconds.
Bounce/block handling improvement: In certain rare cases, a bounce/block would arrive and the wrong address would get added to the bounce or block list. This would happen in cases where an email had multiple addresses in the To line or multiple addresses across the To/Cc/Bcc and the address that bounced was NOT the first address in the To line. This happened across the transactional and campaign platforms.
Transactional email API unsubscribe/bounce improvement: Now, all addresses in a transactional email, including all the addresses in the To field, the Cc field, and the Bcc field will be checked against the account's unsubscribe and bounce lists. Addresses that are on the lists will be removed from their respective fields. If no addresses remain in the To field, an exception will be thrown.
Transactional email API improvement: Multiple recipient addresses can now be put in the "to" field instead of just a single address. Separate multiple addresses with a comma or a semicolon.
SMTP Relay Bug Fix: Our SMTP relay endpoint at smtp.gmass.co would sometimes incorrectly respond with "250 Ok xxxxxxxxxxx" after the RCPT TO or DATA commands were issued, even when there was an error (xxxxxxxxxxx is the Message ID).
SMTP Test Tool Bug Fix: The three bouncy dots that indicate activity at the bottom of the SMTP session would stay present, even when the SMTP session was completed. Now they'll disappear after the SMTP session is complete.
SMTP Test Tool Improvement: There's now an "eye" icon in the Password field so you can hide/reveal the password.
Sending Error Re-try: We've noticed a new kind of network errors surfacing for some campaigns. The error is this: "An exception has been raised that is likely due to a transient failure. If you are connecting to a SQL Azure database consider using SqlAzureExecutionStrategy.". Now, campaigns that error out with this particular error will be automatically re-tried, and no action will be required by the user.
Google Picker Fix: The "Google Picker" UI option when choosing a Google Sheet had been broken since Friday morning, due to a GMass API endpoint, ext.gmass.us, going offline. The "Picker" UI is back up, and with a bug fix included. It will now show just your Sheets, instead of all the files in your Google Drive, and this will make it easier to find the Sheet you want.
Auto follow-up timing fix: Campaigns that had set "end times" and auto follow-ups, in rare cases, could have auto follow-ups send outside of the allowed sending time window. This has been fixed.
Instant Google Sheet row detection fix: Previously, when a new row was added to a Sheet, the campaign would start sending immediately, without regard to timing settings like "allowed days", "skip holidays" and campaign end times. Now, those settings are respected, such that when a new row is added, the row is still instantly detected, and the campaign finds the next allowed time to send the campaign, if the current time is not an allowed sending time.
SpinMax bug fix: Occasionally, the text "body:" was being preprended to the re-worded body of the message.
Scheduling bug fix: A bug was inadvertently introduced on 5/19/25 where if you launched a campaign with a set time for the future and a set "end time", then the start time for the campaign would be incorrect.
Triggered emails bug fixes: We recently identified and fixed an issue that caused some triggered emails to fail to send under specific circumstances. This bug affected a small number of users and was due to one of the following three conditions: 1. Capital letters in recipient addresses: If the To field in the campaign included any capital letters in email addresses instead of all lowercase, the triggered emails could silently fail. 2. Tagged alias addresses: Campaigns using a From Address that included -static or -dynamic tags (rare case). 3. MultiSend delay timing: If MultiSend was used and the triggered emails were scheduled with a delay rather than sent instantly. Approximately 60 users were affected. We’ve already reached out to those impacted by the first and third issues. All three bugs have now been resolved, and triggered emails should work reliably in all scenarios going forward.
Bug fix with campaigns connected to a Sheet: If the Google Sheet had a cell with a value containing the string "error", then the campaign would error out.
Transactional Bounces: Bounces that result from transactional emails will now be captured and added to your account's bounce list. This will happen whether your emails are sent natively from Gmail or from a custom SMTP server.
Transactional Platform Enhancement: When sending emails through the GMass relay at smtp.gmass.co, you can now have your emails send through a custom SMTP server instead of your native Gmail account.
Bug fix for SpinMax: Sometimes, a few recipients out of a campaign would error out when calling the OpenAI API to generate a SpinMax message variation. These recipients would sometimes fail to be retried later on and could have been skipped by the campaign if OpenAI threw an error the first time. Now these recipients will always be retried later. An example error is: Response status code does not indicate success: 502 (Bad Gateway).
Another bug fix for campaigns with end times: If a campaign was thrown off its normal schedule with an unexpected event, like running into Gmail limits and getting over-limit bounces, the sending schedule was not reverting to the user's intended schedule after solving the problem. The campaign was staying on the altered schedule created by the "problem". This is now fixed.
Bug fix for campaigns with end times: In situations where the allowed sending window crossed over midnight, the campaign would advance one day more into the future than needed for its next scheduled sending time. This is now fixed.
Bug fix with dynamic lists and Sheets: From April 15-May 14, 2025, a bug was in place that affected a small number of users. Campaigns connected to a Sheet where the "To" address did not contain the actual Google Sheet alias address, because the user clicked "Expand addresses", which replaced the alias address with the actual recipient addresses and also set the campaign to recur to new or all rows were affected. These campaigns were NOT actually checking the Sheet for new rows. This was fixed on May 15, 2025.
Sending update: Campaigns that processed 30x without being a recurring campaign would normally send a user notification saying "Your campaign has processed 30 times, click link to keep sending" and a link would need to be clicked to keep the campaign sending. This mechanism was an "emergency brake" for runaway campaigns that couldn't be completed in 30 attempts due to OAuth conneciton or limit issues. We have modified the condition for this notice to be sent. NOW: Only if the campaign sends 0 emails 30x in a row will the user have to click this link to keep the campaign going. The benefit of this change is if you have a campaign to 4,000 prospects sending at 100/day, then after 30 days, when only 3,000 emails have been sent, you will now NOT have to take action to keep the campaign sending.
Bug fix with dynamic lists and auto follow-ups: If you sent a campaign to a list from a Sheet using a dynamic list, and you then deleted rows from the Sheet, those were not being reflected in the auto follow-ups sent for the campaign. Meaning, auto follow-ups were still going to the deleted rows. This is fixed now.
Spam Solver Improvements: The Spam Solver, available in the settings box, has been improved greatly. 1) You can now see the results to specific corporate filters like Barracuda, Sophos, and ProofPoint, 2) Based on your results and your testing parameters, advice is provided on what to test next, 3) There's an option for AI-generated advice based on your specific email campaign, and 4) The design of the page has been improved
New feature: Set your sending order. By setting your sending order, you can determine the order in which GMass goes through the rows of your Sheet to send. Leaving it as the "default" will make it so that GMass goes from top to bottom in your Sheet. You can also choose to randomize, use alphabetical order by email address, or reverse the order that the rows appear in the Sheet. This setting is an account-level setting, not a campaign-level setting, so you can find it in your dashboard's settings under "Sending". Screenshot: https://dl.dropboxusercontent.com/scl/fi/ni1v3wc5ui4vm9u8vkx72/chrome_TwZY0yPRoQ.png?rlkey=dsu88ju3ghqz5wpy0n1c9y7eg&dl=0
Bug fix with "new vs all rows" option in settings box: After adding in the "dynamic lists" feature, the "new vs all rows" option in the "Repeat" section of the settings box wasn't always showing in the right situations. This has been fixed.
New "end time" setting: The latest version of the GMass extension, 6.0.27, has been published, and it includes an often-requested feature, the ability to set a daily campaign "end time". For example, you might want to set your campaign "end time" to be 5:00PM so that your recipients don't get any emails after the traditional work day is over. This way, when the clock strikes 5:00PM, the campaign will pause and resume sending on the next allowable day.
Improved unsubscribes/bounces management for team leaders: Team leaders can now manage the "unsubscribe" and "bounce" lists for their entire team when logged into the team master account.
There is now a "Delete All" button on both the Unsubscribes and Bounces management pages in the dashboard's settings.
Improved list functionality: Now, any GMass-generated list address, in the format of 5-recipients-e89adb94@gmass.co can be 1) Made dynamic by adding "-dynamic" to the local part of the address, 2) Made static by adding "-static" to the local part of the address, and 3) Can be used as a suppression list. Dynamic lists will always pull the recipient list from their source, typically a Google Sheet, at send time. Static lists will never pull the recipient list from their source at send time and will only used what was pulled at the time of list creation.
Recipient removal lists: Campaign "send" notifications, that get emailed to you after a campaign has sent, will now contain an attached text file detailing any recipients that were removed from the campaign due to reasons such as the recipient being on the unsubscribe or bounce list.
Extension update with SpinMax: New version, 6.0.25, is now live in the Chrome Web Store, and it includes our new feature, SpinMax. SpinMax is an automatic spintax system that varies the subject/email to every recipient in a campaign. Documentation here: https://www.gmass.co/blog/spinmax/
Campaign send counts: The send "counts" for a campaign, which appear in the various "campaign" dropdown menus in the settings box, will now be more frequently updated. Before, if you sent a campaign to 100,000 recipients, and then in the middle of sending, looked at that campaign in the dropdown menu, the send "count" would still say 0, because the campaign hadn't finished sending yet. Now it will be updated throughout the sending process.
The "link checker" screenshot fix: The "Link Checker" feature in the settings box had been failing to generate screenshots of links in an email campaign for some time, due to an undocumented change in the screenshots API that we were using. We have now worked around that API change and now screenshots for links are working again.
Extension update: New version, 6.0.22, now live in the Chrome Web Store. A minor update which presents a different opening popup for new users to invite them to take the guided tour.
AI "welcome" email: New users who sign up will now receive an AI-generated "welcome" email that guides them on their use of GMass based on who they are. The AI analyzes their email address to determine their identity and use case for GMass. Existing users can receive this email by going to this URL in the browser: https://ext.gmass.us/ai/welcomeemail?emailaddress=you@company.com (replace the email address with your own)
Extension update: New version, 6.0.21, now live in the Chrome Web Store. This new version addresses several bugs with "radio" buttons in the GMass settings box that surface when multiple campaigns are being worked on in multiple Compose windows simultaneously.
Bug fix for incoming messages: Certain bouncebacks that should have been classified as "blocks" were being classified as regular "bounces" due to a string case sensitivity comparison bug. For example, if a bounceback had the phrase "fails DMARC" in it, this was being classified as a "bounce" instead of the correct classification as a "block".
Triggered emails enhancement: Triggered emails will now include the List-Unsubcribe header if your account has the List-Unsubscribe header turned ON in your account's dashboard settings.
Transactional API enhancement: There's a new setting called "listUnsubscribeHeader" that can be passed into the transactional API method, and this setting determines whether a List-Unsubscribe header is used in the transactional email.
Reporting bug fix: Long-running large campaigns would not have their recipient counts updated regularly on the dashboard's main screen, leading to inflated statistics on the main dashboard page. Statistics were still accurate on a campaign's report page, since those are calculated in real-time, but just not on the main dashboard page.
Bug fix for triggered emails sending over SMTP: Previously, if a campaign was set to send through an SMTP server, and the account had multiple SMTP servers configured, the triggered emails would send throug the account's DEFAULT SMTP server rather than the campaign's specifically chosen SMTP server. This is now fixed, and the triggered emails will now send through the campaign's chosen SMTP server.
Bug fix for DKIM signing emails on triggered emails: If triggered emails were sending over an SMTP server, then the emails were not being signed using your configured DKIM settings. This is now fixed.
Bug fix for Date on triggered emails: The Date header was not being set correctly for outgoing triggered emails. The Date header was being set based on the date/time the trigger TEMPLATE was created, rather than the current date/time of the outgoing email. This is now fixed.
Bug fix for repeating campaigns: When a campaign is set to repeat to ALL ROWS of a Sheet, or to repeat to a freehand recipient list, and if the campaign also had auto follow-ups set, it was previously not possible to cancel the auto follow-ups for a specific past instance of the campaign. It was only possible to cancel them for the current instance of the campaign, and if you tried to cancel them for a past instance, they would only cancel for an instance chosen at random rather than the user-specified instance. This was due to a non-uniqueness of identifiers assigned to past instances of the campaign.
Extension updated to 6.0.20: Fixed bug where if you have multiple SMTP servers configured for your account, and in your GMass campaign settings you had set an SMTP server, when using the Spam Solver, Send Test Email, or Email Analyzer functions, the email would instead send the email through your account's default SMTP server instead of your actual chosen SMTP server. This is now fixed.
Another transactional API enhancement: When using the transactional API method to send transactional emails, if "useCustomerSMTP" is set to true, and your account has multiple SMTP servers configured, then you can also set the new setting "SmtpServerId" to decide which SMTP server to send the email through. If "SmtpServerId" is not specified, then the transactional email will send through the account's default SMTP server.
Transactional API enhancement: When using the transactional API method to send transactional emails, if "useCustomerSMTP" is set to true, and the user has configured DKIM in the account's settings, the transactional emails will now be DKIM-signed.
SPF Checker Fix: If your domain's SPF record used dynamic variables, then our Email Analyzer was unable to parse the SPF record and using the Email Analyzer would result in a bounce and incomplete results. Our Email Analyzer still can't handle dynamic variables in an SPF record, but it will now state that, skipping the SPF results but still displaying the rest of the analysis including DKIM, DMARC, the SMTP conversation, and more. Also, you won't get a bounce anymore.
Bug fix: If you copy/paste an HTML campaign from your Gmail Sent folder into a new Compose window, and then send that campaign, and that copy/pasted message has click-tracked links in it, GMass has always "re-tracked" those links if the new campaign was also sent with "click tracking" on. The plain text MIME part of the campaign, however, was also getting those click-tracked URLs because Gmail creates the plain text MIME part behind the scenes from the HTML in the Compose window. The bug was that the click-tracked links copied/pasted in the plain text version were not reverting to their original URLs, and now they will be. Just FYI, links in the plain text MIME part of an email are never click-tracked even when "click tracking" is on.
Bug fix: When using MultiSend with auto follow-ups and setting custom content to go as a NEW thread, rather than in the SAME thread, and also selecting "Force prior conversation to appear below message" in your account settings, the message from the "prior conversation" was actually a result of searching for the last conversation with each recipient RATHER THAN finding the last message in that particular campaign.
Bug fix: When using MultiSend with auto follow-ups and setting custom content to go as a NEW thread, rather than in the SAME thread, and also selecting "Force prior conversation to appear below message" in your account settings, auto follow-up batches would error out with this message: "You can't use the MultiSend feature when you have a campaign set to send as replies to the last conversation with each recipient." That issue has been fixed, and these auto follow-up batches will now send as expected.
Better icons: Better visual icons have been added to the left-hand Settings section that flies out when you click the "gear" icon in the dashboard.
The "Time Zones" feature is complete. You can now set your preferred time zone in your dashboard settings, and have that time zone reflected in all campaign reports. Additionally, your chosen time zone will be the default time zone that appears in the extension's Scheduling field. Finally, you can opt to have recurring campaign times adjusted back and forth according to changes in Daylight Savings Time for your selected time zone.
Extension updated to 6.0.13: Bug fix where a JavaScript interval specific to a Compose window could be left running and therefore consuming system resources even after the Compose window is destroyed.
Extension updated to 6.0.12: This new version supports our upcoming "time zones" feature, where a GMass account can have an assigned time zone, and then the extension's "Schedule" section will default to that time zone rather than the computer's local time zone.
New Setting: A "Time Zones" section has been added to the dashboard's settings, in preparation for our upcoming "time zones" feature.
Extension updated to 6.0.11: Bug fix. When you loaded a Template from the dropdown, if you chose to load the Settings as well as the Subject/Message, the Settings option wasn't setting the Gmail vs SMTP options correctly. Now that's fixed.
Fixed bug where if you connected your campaign to a Sheet with many columns, the helper box in the Gmail Compose window, with personalization and conditional logic options, would get cut-off and not show all the options. Now, a scroll bar will appear when necessary.
Fixed bug where after the "multiple SMTP servers" option was deployed, some users' settings reverted to Gmail instead of their last used SMTP option when launching a new campaign.
Extension bug fix: When using the AI option to generate a full sequence of emails, even though the sequences would appear to be set in the "Auto Follow-up" form fields, sending or saving the campaign would not actually save those settings and content, unless you focused into each field at least once. This is now fixed.
Extension updated to version 6.0.5: This version features a dropdown allowing you to choose which SMTP server to send through, if you have multiple SMTP servers set up in your dashboard. You can choose to send either via normal Gmail or any of your SMTP servers.
Open tracking bot filtering: We've updated our algorithm that attempts to filter out "opens" caused by "bots". This may result in a decrease in open rates for your campaigns, but this will also result in more accurate "open tracking". One of the main changes is such that if the User Agent string contains "Chrome" and "Safari" and "Edge", we are now counting that as a false "open" instead of a real "open".
New feature: You can now add multiple SMTP servers to a single GMass account. Before, you could only connect one SMTP server to your account at a time. Now you can add multiple servers and choose which is the "Default", and the "Default" choice will be used for SMTP-based sending and is the SMTP server that will show up in the extension's settings box when you opt to choose via SMTP instead of Gmail.
New feature: Spintax text generator using AI. Click the "AI" icon above the Templates dropdown, navigate to the Spintax Generator, put in the text for which you would like to generate spintax variations, along with the number of variations, and our AI engine will generate the variations for you in the GMass spintax format.
New feature: Easier management of the Templates dropdown in the extension. Because this dropdown saves all of your campaigns, you can now clean up what's in the dropdown inside the dropdown itself. Just hover over a campaign, and a "trash can" icon will appear. Click the "trash can" to remove the template from the drop down. If you change your mind, you can always re-add it by going to your Dashboard --> Settings --> Templates.
Fixed a scheduling bug involving MultiSend (Inbox Rotation) and setting "weights" for each MultiSend account. If you configured a campaign with MultiSend and used account weights to set each account's daily limit, the scheduled start time of the campaign was being ignored in favor of the current time.
When sending natively through a Gmail/Google Workspace account, GMass has always automatically forced a slow-down in sending speed once a campaign hits 70% of the account's sending limit. So for a Google Workspace account, 70% of 1950 is 1365, so after about 1365 emails are sent, a forced delay of 5-10 seconds is added after each individual email is sent. Some users don't like this forced delay, so now the 70% factor is configurable and can be set to 100% which would cause there to never be a delay. For now this is an internal account setting, and eventually, it will become a setting in the dashboard's interface.
Fixed a longstanding bug with emailing contacts from a Google Sheet, where the Sheet has duplicate email addresses and you've applied a filter to send to just certain rows. Before, if you chose the default option of having duplicates eliminated, and the second instance of an email address in the Sheet matched your filter, then that address wouldn't receive the email, because the list was de-duped first, and then the filter was applied. So the second instance would be lost in the de-duping process. Now the order has been flipped so that the filter is applied first, and then the list is de-duped.
We've modified our sending system to auto retry a new type of Google API error, "The service sheets has thrown an exception. HttpStatusCode is BadGateway." This error has been showing up in our logs since Sept 1 2024 and has been especially prevalent in the last two weeks. Now, campaigns that encounter this error will be automatically retried 10 minutes later.
Improved handling of new Google OAuth Granular Consent: Before during the OAuth connection process, if a user didn't check all the permissions boxes, on the next screen, a GMass error would be displayed. Now a friendlier notice indicating that the checkboxes must be checked is displayed.
Bug fix related to "blocks" and "over-limit" bounces for campaigns: If a campaign was using Inbox Rotation, and you attempted to send a new behavior-based campaign to just the "blocks" or "over-limit" bounces, not all of the email addresses were being retrieved from all the accounts used in the Inbox Rotation of the original campaign. Additionally if you attempted to download "blocks" from the dashboard for an Inbox Rotation campaign, not all of the blocks were downloaded. This is now fixed.
Bug fix for DRAFT creation and sending: When you set your campaign to create DRAFTs first and then use the GMass link to send them after reviewing, the link was set to send ALL DRAFTs that had been created as part of that campaign up until that point in time. Now, the link contains an identifier which will allow the link to send only the DRAFTs that are referenced in the notification that contains the link. This improvement will prevent situations where a daily recurring campaign creates a batch of DRAFTs on one day, the user clicks the link to send them, but due to a limit issue, not all DRAFTs are sent, and the remaining DRAFTs are scheduled to be sent 24 hours later, but within that 24 hour timeframe, the second day's batch of DRAFTs are created, and now the scheduled send 24 hours later sends ALL the DRAFTs rather than just the remaining DRAFTs from the first day. This scenario is frustrating for users because the second day's batch of DRAFTs may not have been reviewed yet, but they were still being sent as a result of the first day's DRAFTs not being fully sent on the first day.
Detection of multiple SPF records: If your domain has multiple SPF records, which is considered failing SPF, you will now be alerted to that specific condition. Both the Email Analyzer will report multiple SPF records and the real-time SPF checker which fires upon any campaign sending will check for multiple SPF records.
Better handling of new Gmail API errors: While sending a campaign, the Gmail API sometimes returns a "Precondition check failed" error and starting in mid May, we noticed a new error, "InternalServerError". If individual recipients of a campaign result in either of these errors, the individual recipients will now be automatically re-tried for sending a few minutes later.
Bug fix when sending DRAFTs: When using the option to create DRAFTs first and then send with a link, if the 5-10 minute delay option was chosen when setting up the campaign, this delay was not respected when the DRAFTs were sending. This is now fixed.
Minor API fix: The two endpoints https://api.gmass.co/api/campaigns and https://api.gmass.co/api/campaigns/{campaignId} were not retrieving a campaign's "friendly name" properly. They would show a null value when a friendly name was actually set. This is now fixed.
Spam Solver Improvement: We've now separated the list of seed accounts used by the Spam Solver from the list of seed accounts used by our public deliverability testing tool (gmass.co/inbox). This will allow the Spam Solver to function much more reliably, because the public seeds have been getting hammered with so much volume lately that the Spam Solver would have trouble locating the emails in the accounts. The Spam Solver will now send to 20 private seeds, that are not exposed to the public, and will still show the placement results across Inbox, Spam, and Promotions.
API Enhancement: The two campaigns endpoints, https://api.gmass.co/api/campaigns and https://api.gmass.co/api/campaigns/{campaignId}, now expose additional campaign data, including the campaign's "friendly name", and any sent auto follow-up emails for those campaigns. The https://api.gmass.co/api/campaigns/{campaignId} endpoint exposes additional specific data about individual batches that make up each individual auto follow-up stage, while the https://api.gmass.co/api/campaigns endpoint does not expose this specific batch data.
Custom tracking domain bug fix: Custom tracking domains were exposing the GMass API Swagger site, when a URL such as http://tracking-domain/apihelp/index was accessed. Now such URLs will redirect to the api.gmass.co domain.
Templates bug fix: Sharing templates wasn't working due to a bug that was introduced when we deployed our campaign data backup storage solution two weeks ago. Templates were able to be shared through the dashboard, but when loading shared templates in the Templates dropdown in the extension, users encountered a "Object reference..." error. This is now fixed.
Open Tracking: The img tag now contains a blank alt tag (alt="") in order to satisfy a particular SpamAssassin test.
MultiSend (Inbox Rotation) Improvement: If an account loses its OAuth connection or GMass is otherwise unable to connect to it to send an auto follow-up batch of emails, the notification sent to the user will now clearly highlight accounts that could not connect at all, and this notification will contain a link to our OAuth connector to re-establish a connection to each failed account.
Bug fix on sending DRAFTS: When a campaign is set to "Just create DRAFTS" and is later queued to send, sometimes temporary errors while sending those DRAFTS, like the "Precondition check failed" error would fail to re-try. The process that sends DRAFTS after the user clicks the link to send created DRAFTS attempts to send each DRAFT 5x, and then after 5x, a notification is sent to the user requesting the user to re-click the link to send the DRAFTS should any DRAFTS still remain because of temporary Gmail API errors. With this bug, if the sending process itself, rather than the DRAFT retrieval process, resulted in a temporary Gmail API error, and all 5 attempts were exhausted, the user was not told to re-click the link to send. That is fixed now, and so now, the user will be told to re-click that link.
Reports bug fix: The single page report wasn't allowing you to click a stat and have the side panel open up with the detail, unless you were also logged into your account's dashboard. This is now fixed, so that the side panels will open even if you're not logged in.
Sending for individual recipients of a campaign will re-try on "Precondition" error: Starting last year, we noticed a new error returned by the Gmail API, the "Precondition check failed" error. Recently, we've seen a ramp-up in this error being thrown by the Gmail API. While the error is unpredictable, it also seems temporary. GMass campaigns that error out at large due to this error have always been re-queued for 10 minutes later, and in most cases, the error does not recur. Campaigns, however, can still complete "successfully" but have individual recipients that still error out due to this error, so we have now deployed a change so that if individual recipients in a campaign receive this error, the campaign will re-queue in 10 minutes to send again to the failed recipients.
Auto follow-up timing change: We previously made it so that if the current time is within 3 hours of a user chosen day/time for auto follow-ups to send, then they would start sending. However, if the time then crossed over into a day that was disallowed, according to the campaign's "Choose specific days" setting, the campaign would stop and resume in the morning of the next allowed day. Sometimes the campaign would stop after sending as few as 50 emails. We've now modified this so that for auto follow-up sends specifically, the campaign will continue sending for a minimum of 4 hours before checking if the time has crossed over into a disallowed day, and if so, it will pause and resume on the next allowed day.
API bug fix: Fixed a bug where the API "campaigns" endpoints sometimes returned an incorrect number of recipients for a campaign. This would happen if individual recipients for a campaign had errored out at some point due to a Gmail API temporary error and then were retried and sent successfully later on.
Chrome extension update: Version 6.0.3 has been published to the Chrome Web Store. Note that we intentionally skipped version 6.0.2. 6.0.3 contains a fix for older browsers, notably Chrome version 109, that didn't allow the new Manifest V3 version of GMass to work. The GMass buttons weren't showing up in Gmail. 6.0.3 is designed to work with older browsers, like Chrome version 109, and newer browsers.
Chrome extension update: Version 6.0.1 has been published to the Chrome Web Store. This version fixes a bug on older computers, and therefore older Chrome browsers (prior to version 111) where repetitive calls were made to a CORS test URL over and over until an INSUFFICENT_RESOURCES error was thrown by Chrome.
Auto follow-up bug fix: We discovered that some campaigns failed to send all of their auto follow-ups if the "Count selected days only" setting was enabled in an account's dashboard settings. This is a global setting that applies to all campaigns. The issue only surfaced if this setting was ON and if in the "Choose specific days" setting for a campaign, 5 or fewer days were chosen, and if the Stage Days settings were such that the highest number of Stage Days added to the last send time for the campaign was less than when the auto follow-ups should actually send based on the "Count selected days only" setting.
On demand auto follow-up bug fix: When using the "Send Stage X Now" buttons to launch an auto follow-up stage on demand, if you had also configured your campaign to use a specific set of days or to skip holidays, and it was a holiday or a disallowed day, the on-demand send would send some emails while the rest would be pushed to the next allowed day. This behavior is not what the user would expect in this scenario, since the point of the "on demand" send for auto follow-ups is to send those emails now, regardless of any timing settings. This has been corrected. On demand auto follow-ups will truly send now and will disregard any Choose-specific-days or Skip-holiday settings.
Auto follow-up bug fix: For a very small percentage of campaigns (less than 1%), auto follow-ups would never send because the original campaign failed to be recorded into the user's "GMass Reports --> Sent Copies" label. The failure would usually happen due to a Gmail API error like a "pre-condition error". As a result of the campaign not being recorded in that label, auto follow-ups would fail to send, because the auto follow-up system is dependent on that message being there. Now we've implemented a backup storage solution such that even if the campaign fails to record itself in that label, auto follow-ups will still send because the campaign data will instead be recorded in our database.
Over-limit bounces handling improvement: If your campaign receives an over-limit bounce from Google that says "You have a reached a limit for sending mail", the normal behavior for GMass is to determine which sent email caused the bounce, and then re-send that individual email at a later time. In some instances, due to how the Gmail API returns InternalDate data, GMass would detect the wrong email in an email sequence that caused the over-limit bounce, and would re-send an email that had actually already been sent. This was because of how the messages were ordered in the thread, as returned by the Gmail API. We've now applied a different algorithm to determine which individual message in an email sequence generated the over-limit bounce, so that GMass knows exactly which email to re-send at a later time.
DKIM Bug Fix: Before, when trying to activate a DKIM record after entering in DNS records, if the DKIM record was 2048 bits or higher, requiring multiple strings as part of the TXT record, sometimes GMass would fail to recognize the DNS record. The DNS query system has been improved to be more reliable and allow more reliable activations of DKIM records. Similarly our process that checks all DKIM records hourly will use this new DNS querying system to avoid erroneous deactivation of DKIM records.
Auto follow-up timing improvement: Previously, if a stage's "time" was set too close to midnight, like 23:00 or 23:30, there was a chance the auto follow-ups didn't send at all or sent days after they were supposed to. Now, this is corrected. GMass now checks to see if the current day/time is within 3 hours of the expected-send day/time. So now if the expected send time is Wednesday at 11PM, then GMass will send if the current time is Wednesday at 11:30PM, or if it's Thursday at 12:30AM or Thursday at 1AM, because these are all within the 3 hour allowance of the expected-send-time.
Bug fix for polls: Previously when creating a poll, after the poll was inserted into the Compose box, if you clicked one of the answers to test the link, an error page would appear. If you sent the campaign, the links would work and the answers were recorded, but if you clicked the link in the Compose box while drafting the campaign, then only the error would appear. Now, after the fix, you'll see a message indicating that the answer link hasn't been personalized yet, and the message will acknowledge that you must be just testing clicking the answer link.
The GMass Chrome extension on the Chrome Web Store has been updated to version 6.0.0. The big difference is that this version of the extension is on Manifest V3 as opposed to the no-longer-supported Manifest V2. JavaScript code can no longer be remotely loaded in Manifest V3 and is instead packaged as part of the extension. While this allows for a more secure extension experience for users worldwide, making changes to the extension will now require a longer process.
Bug fix: Users were unable to subscribe to the Professional plan using PayPal. Trying would result in an error on PayPal's site. Now it works.
Sending bug: Fixed a longstanding bug where a campaign would finish sending and the campaign's DRAFT would be deleted by GMass, and then a few seconds later, the campaign would start processing again, this time resulting in a "Campaign DRAFT deleted" error. This would leave the campaign in an "error" state even though it had successfully finished sending the minute prior.
New onboarding tour launched in extension: We have replaced the onboarding flow for new users from the old "Show me the magic" option to a fully guided tour that walks new users through connecting to a Google Sheet, using personalization, configuring the settings, and sending.
New webhook for OAuth: You can now configure a webhook to be called whenever a user that you direct to GMass has successfully completed the OAuth flow. More information: https://www.gmass.co/blog/oauth-webhook-api/
Extension bug fix: Several users were reporting that clicking the button in the settings box to EDIT an auto follow-up template was not working properly. The Compose window would open with the subject/message but the To field was left blank instead of populating with the GMass-generated unique address. This was likely due to a timing change natively in Gmail. We implemented a fix.
Reporting bug fix: Downloading the main campaign report for a campaign that was not connected to a Sheet wasn't working for the last few weeks. This is fixed now.
MultiSend daily account caps update: When setting daily caps for MultiSend accounts in a campaign, the algorithm for detecting how many emails each MultiSend account has already sent for the day has been improved. Before, the count was a straightforward count over the last 16 hours. Now the count is more accurate because it's based on various factors, including when the campaign last successfully ran and any subsequent runs since then.
New auto follow-up setting: Under the dashboard's "Auto Follow-up" settings, you can now enable a new setting called "Allow adding auto follow-ups after campaign is sent". Enabling this setting will prevent your campaign's DRAFT from being automatically deleted by GMass, even after the original campaign is sent. By keeping the DRAFT around, you can add auto follow-ups to your campaign even after it has fully sent.
New behavior for the "global unsubscribes" setting: Previously enabling this setting would use related accounts for filtering campaigns for unsubscribed addresses. In addition to this, enabling this setting will now also use related accounts for filtering unsubscribed DOMAINS from campaigns.
New auto follow-up setting for counting days: Under the dashboard's "Auto Follow-up" settings, you can now enable a new setting called "Strict count of days between stages". This will force the timing of auto follow-ups such that the number of days BETWEEN stages must pass in order for a subsequent stage to be sent.
New auto follow-up suppression setting for blocks: Under the dashboard's "Auto Follow-up" settings, you can now enable a new setting called "Suppress blocks from later stages". Enabling this will make it so that a campaign that has auto follow-up stages will stop sending to an email address after a "block" rejection has been received.
New bounces/blocks setting: Under the dashboard's settings, you can now enable a setting called "Treat blocks as bounces". Rejection messages that indicate a "block" rather than an invalid recipient address can now be treated as bounces, which will add the address to an account's bounce list for automatic filtering from future campaigns.
SPF Real-time Checking: Now, whenever you send a campaign, the SPF record of your account's domain will be checked, and if it looks incorrect or is missing, we will email you a notice with helpful instructions. To prevent bombarding you with SPF notices, only one per week max will be sent.
Reporting bug fix: Downloading the main campaign report for a campaign that did NOT use a Google Sheet was failing for the last few weeks. Fixed now.
Unsubscribes Importer: You can now import a list of unsubscribed addresses by dragging and dropping any text or Excel file onto the Unsubscribes management page in the dashboard. Just click "Add unsubscribes", and then drag a file onto the popup.
Auto follow-up settings bug fix: Fixed a longstanding bug where the text "null" would show up in the time fields for auto follow-up stages when composing a new campaign.
New Auto Follow-up Feature: You can now send auto follow-ups "on demand" instead of waiting on the timing you've set. Just open up your campaign's DRAFT and you will see new buttons to send each stage "now". This is useful if you've changed your mind on the timing and want to have follow-ups sent sooner than later.
API supports MultiSend Weights: Now when launching a campaign with the API using the /api/campaigns POST endpoint, the MultiSend setting can contain weights after each sending account separated by the pipe symbol. Example: john@smith.com|100,bob@smith.com|200 in order to have the campaign send 100 emails through john@smith.com and 200 emails through bob@smith.com. Weights are optional.
MultiSend Weights: MultiSend, the feature that allows you to load-balance a campaign over multiple sending accounts, can now be used with "weights". You can specify a "weight" to go along with each account to choose exactly how many emails are sent from each account, for that particular campaign.
Countdown timer: The animated GIF images were being generated off our main gmass.co web server, and today, a large campaign using the countdown timer feature resulted in the server being flooded with requests and our website not working anymore. A caching mechanism has been implemented such that the animated GIF for a particular countdown timer will stay in memory for a minute before being re-generated on the next request.
Google Sheet updating: There was a huge backlog of unprocessed Sheet updates for bounces and replies. We've now sped up the process for updating Sheets based on these events, and the backlog will be cleared in about 24 hours.
The settings page where you can customize the unsubscribe text has been improved to be more helpful, to have a one-click link to insert the default unsubscribe link into the HTML editor, and to have default text pre-populate the HTML editor when you haven't yet set custom unsubscribe text.
Fix for users of Gmail layouts: If you were using a Gmail "layout" in your email campaign, this prevented the main GMass button from working. Clicking it to try to send your campaign would have resulted in an endless "Please wait for GMass..." message. This happened because the Compose "div" that GMass looks for changes from contenteditable=true to contenteditable=false after a "layout" is inserted. We have now modified our logic to accommodate this, so you can now use the GMass button when using Gmail layouts.
New Google Sheets feature: GMass can now detect new rows in a Google Sheet instantly, and then start sending emails to the new rows instantly. Under the Scheduling-->Repeat section of the settings box, the "Instantly" option has been added to the dropdown.
New spintax capability: Users can now enable a setting that will increase randomization when using spintax. The setting is under "Other" in the dashboard settings. This is an account-wide setting: https://dl.dropbox.com/scl/fi/976qcrdsk6xscm4unrhr5/chrome_4S7Bdda4X3.png?rlkey=l11c9t1ey85jij4ois5oc585p&dl=0 With this setting ON, each spintax block is treated independently rather than as a set along with the other spintax blocks. With this setting OFF, which is the default behavior and how spintax has always worked, spintax blocks are matched sequentially with each other, meaning the first variation in the first block is matched with the first variation in the second block. With this setting ON, each variation in each block is picked at random to form a complete email message.
Reporting bug fix: Downloads in Excel format were failing before due to a missing DLL on our reporting server. This is now fixed.
Unsubscribe bug fix: If your account was on a shared tracking domain and you were using the GMass-provided unsubscribe link, the unsubscribe page wasn't loading the CSS properly, resulting in a plain text look rather than the formatted look. Additionally, because the CSS was failing to load, an error was being logged for that IP address, so if you were testing your own unsubscribe link, there was a chance that you logged too many errors from your IP address, which would've prevented you from using the GMass button for some time period until the error-block expired.
Sending bug fix: If sending to a Google Sheet and you enabled "Keep Duplicates" when connecting to the Sheet, and the Sheet had duplicate email addresses in different cases, like "email@domain.com" and on another row, "EMAIL@domain.com", only one email was being sent instead of all of them. This is now fixed.
In rare cases, if a customer filed a credit card dispute, the GMass subscription with Stripe wasn't auto-cancelled. This would happen if either the user hadn't yet created a GMass account or if the information retrieved from the Stripe API had a missing "source". Both of these scenarios are now handled properly and the subscription will still be auto cancelled.
Sending bug fix: If a user toggled OFF all of the "standard holidays" but then enabled the "Skip Holidays" setting for a campaign, the campaign errored out. This is now fixed.
Auto follow-up new option to change how days are counted: BEFORE - When setting the number of days after the original a particular stage should be sent, all 7 days were counted, even if you had chosen just Mon/Tues/Wed/Thurs/Fri as your selected days for your campaign. This resulted in auto follow-up batches "bunching up" on Mondays if you had multiple campaigns running. NOW - You have the option in your account settings in your dashboard to check a box labeled "Count only selected days of week". With this option enabled, only the days you've selected for your campaign are counted, which would result in auto follow-ups being further spread out in the above example.
Auto follow-up behavior change when time-of-day is specified: BEFORE - GMass would send an auto follow-up batch if the day was an allowed day according to the user's "choose days" setting and if it was within 3 hours of the user's chosen time, in the user's local time zone. GMass allowed midnight (00:00) to be crossed over when determining if it was within 3 hours of the user's chosen time. This created a sometimes odd scenario where if a user had scheduled auto follow-ups to send at 11:00PM Eastern Time, and chose Sun/Mon/Tues/Wed as allowed days, then the auto follow-ups would send on Sunday at 12:30AM. Why? Because Sunday is an allowed day and 12:30AM is within 3 hours of 11:00PM. NOW - Now, the same rules apply but the current time of day has to be after the user-specified time of day. In the above example, 12:30AM is not after 11:00PM, so now, the auto follow-ups would not send on Sunday at 12:30AM. Now, the auto follow-ups would wait until at least Sunday at 11:00PM to send.
Bounces/Blocks: The bounce message "Message queue continuously deferred for too long", which was previously treated as a "bounce", will now be treated as a "block".
New Feature - ChatGPT campaign creation: Users can now have ChatGPT create an entire email campaign, including an entire email sequence, by typing in a prompt. More information: https://www.gmass.co/blog/chatgpt-email-campaigns/
New Feature - Countdown Timer: Users can now add a countdown timer, in the form of an animated GIF, to their email campaigns with a simple click of a button. More information: https://www.gmass.co/blog/email-countdown-timer/
MultiSend bug fix: Campaigns that used MultiSend, where none of the selected MultiSend accounts were valid, were erroring out with this error: "General Exception Attempted to divide by zero." This error resulted from a division by zero, because the number of valid accounts was found to be zero. Accounts can become not valid when there OAuth connection to GMass breaks. Going forward, when this situation surfaces, the error message will be more meaningful. Example of new error: https://dl.dropbox.com/scl/fi/yszfy7p5al3kzmis3jzkb/chrome_GLswRIm5zD.png?rlkey=tune647wa6uwn6za6iul508sy&dl=0
You can now customize the unsubscribe text that appears when you click the "Unsubscribe Link" button in the extension. Customize the text by going to the dashboard, clicking the "settings" gear, and going to the Unsubscribes section on the left side panel.
Email polls improvement: You can now set better landing page options for your recipients that answer your poll. See https://x.com/PartTimeSnob/status/1770109212363837746?s=20
Template management improvement: You can now bulk delete templates. See https://x.com/PartTimeSnob/status/1770329587290964034?s=20
API bug fix: In certain situations, retrieving a list of account-wide unsubscribes via the https://api.gmass.co/apihelp/index#!/Reports/Reports_Unsubscribes method was resulting in 0 records returned.
Bounce filter adjustment: We discovered a new type of Gmail bounce that looks like this, "550 5.4.5 Daily user sending limit exceeded. For more information on Gmail sending limits go to https://support.google.com/a/answer/166852". This bounce resulted from sending from an "alias from" address instead of the primary Google account, and when the SMTP server connected to the alias was a Gmail server, and when the account was over-limit. These bounces look new and have been appearing since mid November 2023. These bounces were erroneously resulting in the recipient address being placed on an account's bounce list. The filters have been adjusted so that these types of bounces are counted as "blocks" not bounces. Additionally, we've purged the affected addresses from everyone's bounce list.
Extension bug fix: Previously long domains like support.construction could not be entered into the domain suppression box. This is now possible.
Cancelling campaigns: When you cancel a campaign and its auto follow-ups, a more aggressive approach is now taken, where any pending batches of auto follow-ups that haven't completed sending yet, are now also cancelled. Before, any pending batches would be allowed to continue sending but any new batches would be prevented from being created.
API: When retrieving a campaign's status via the https://api.gmass.co/docs#tag/Campaigns/operation/Campaigns_GetCampaign and https://api.gmass.co/docs#tag/Campaigns/operation/Campaigns_Index methods, "status" can now include the additional values of "cancelled", "paused", and "abpaused".
Auto follow-up timing bug fix: If you had set specific times for your auto follow-up stages, and you had also set specific days, like Mon-Fri, when your campaign should send, and then an auto follow-up send fell on a Sat/Sun based on the "Stage Days", the campaign would send close to midnight Monday local time and not wait until it was the right time on Monday. This bug is now fixed.
Spam Solver Improvements: The main functionality has a longer timeout period now such that if it takes longer than 30 seconds to send the email to all the seed accounts, it won't timeout anymore. Before the operation would sometimes timeout resulting in an endless spinning wheel without displaying the bar graph with the results.
Sending: If you launch a campaign and the schedule gets pushed back because the current day is a holiday and you have "Skip Holidays" checked, then the confirmation message will indicate clearly that TODAY is a holiday. This is to clear up confusion about why campaign times are getting pushed back.
Extension: Now when you check the "Skip Holidays" checkbox, a butterbar help dialog will appear in the lower-left.
Auto follow-up bug fixes: Some auto follow-ups did not send entirely or did send but at the wrong time if they had one of the new skip-holidays or choose-holidays scheduling features set. Any affected auto follow-ups will go out in the coming days as close to the "correct" time as possible.
Sending bug fix: If you had skip-holidays or choose-days set, and a campaign was in the middle of sending and the time crossed over into a disallowed day, the campaign paused but never resumed on the next allowed day. This is now fixed.
API: The API methods to retrieve campaign data now include additional information. status: scheduled / sent / error / unknown. There's also a new parameter "lists" which includes information about the Google Sheets that were the source of data for the campaign.
Auto-followups: The timing of auto follow-ups has been improved for campaigns that are paused and later resumed. Instead of auto follow-ups that are "past due" going out right away, they will wait until they are near the 24-hour interval of the prior auto follow-up stage.
API: The method to send campaigns is now in line with the two new scheduling features, "Skip Holidays" and "Choose Specific Days". See "allowedDays" and "skipHolidays" here: https://api.gmass.co/docs#tag/Campaigns/operation/Campaigns_Index
Extension: Two new scheduling feature, "Skip Holidays" and "Choose Specific Days" have been added. Campaigns can now skip sending on holidays and only send on the weekdays that you designate.
API: New method to retrieve campaign blocks has been added. https://api.gmass.co/docs#tag/Reports/operation/Reports_Blocks
A checkbox has been added to the dashboard settings, so that users of personal Gmail accounts who are sending through an SMTP server can use GMass's "from" domain replacement system to become DMARC compliant, even before Gmail changes its DMARC records.
MultiSend update: The MultiSend dropdown has been updated to include the primary sending account as an account that can be selected or UNselected. This allows you to send a MultiSend campaign while excluding the primary account that you're logged into.
If GMass DKIM signs your emails (only possible when sending over an SMTP service), and your email includes the List-Unsubscribe header, the DKIM signature will now be based on the two additional headers of List-Unsubscribe and List-Unsubscribe-Post.
GMass will now include the List-Unsubscribe-Post header if you have the List-Unsubscribe header enabled in your settings. This header will always be set to "List-Unsubscribe=One-Click" if included, and it enables one-click unsubscribe functionality.
When GMass writes a DKIM signature to an email that is being sent over SMTP (not native Gmail), then the email placed in the Sent folder of the account will also now contain the header showing the DKIM signature.
Launched a DNS management system for users with personal Gmail accounts (gmail.com and googlemail.com) who are also connected to an SMTP server. This is preparation for a change in gmail.com's DMARC record that will no longer allow sending campaigns "from" gmail.com accounts through external SMTP services.
GMass Transactional SMTP Relay (smtp.gmass.co): We've added a limit of 5 simultaneous connections per IP address and blocked several abusive IP addresses.
The Reply Project: ChatGPT-generated replies have been updated to the "gpt-3.5-turbo-instruct" model.
Bug fix: Affiliate sign-up form at gmass.co/affiliate wasn't working if user tried to sign up as an affiliate but ALREADY had a GMass account.
Bug fix: When creating DRAFTs instead of sending, if an account had an SMTP service connected to it, and the account had DKIM configured inside GMass, if the DRAFTs were then sent via the account's SMTP server, the DKIM settings were ignored and the messages were not DKIM-signed. This is now fixed.
Bug fix: The suppression "days" parameter wasn't working properly if an account was using MultiSend. The suppression list was being built based on only the MultiSend accounts' sending history and not the original sending account's history.
Extension behavior change: Now, when you load a template from the dropdown in the settings box, if you choose to load only the Settings, the Friendly Name will not be set. You must choose to load the content (Subject/Message) for the Friendly Name and Preview Text inputs to be set. It was decided that the Friendly Name and Preview Text are more closely related to the Subject and Message than the campaign's other settings.
Extension bug fix: If you had a friendly name or preview text set for your campaign, and then you cleared out the list in the To field, the friendly name and preview text would disappear. This won't happen anymore.
Bug fix: Retrieving an account's entire unsubscribe list, either from the dashboard or API, was failing in some cases.
List-Unsubscribe header: We are now forcing the header onto emails sent using our shared AWS SES SMTP account or our internal s1.smtpgm.net server. The header will be added in these cases even if you have the header turned off in your settings.
SendGrid: If a user is assigned to our shared SendGrid account, campaigns can no longer be launched using SMTP as the sending option, due to SendGrid's suspension of our service with them. Users will see an on-screen error when attempting to send.
Dashboard bug fix: Sometimes the recipient count for a campaign wasn't accurate, especially in cases where some recipients errored out and had to be re-tried later on.
Affiliates: Launched a new affiliate sign-up form, gmass.co/affiliate, to replace the old process of signing up to be an affiliate.
API: New endpoint added to retrieve unsubscribed domains. See https://api.gmass.co/docs#tag/Unsubscribes/operation/Unsubscribes_Index.
New "holidays" settings page launched. Choose standard holidays and define your own custom holidays. This section doesn't technically do anything right now, but eventually there will be a "Skip Holidays" option in the scheduling settings of a campaign.
Bug fix: On the individual campaign report page, the real-time Unsubscribes feed wasn't working for the last few hours.
API: The "campaigns" endpoints return additional campaign data, including the "from" line, the campaign creation date, and the stage of auto follow-up if it is indeed an auto follow-up.
Launched MultiSend reporting: Now in the dashboard and in the API campaigns using MultiSend can see a breakdown of stats by individual sending account.
API: When sending a campaign via the "campaigns" endpoint, the campaign object returned will include details beyond just the campaign's ID.
MultiSend settings page: Now shows whether each account is OAuth connected and checks to make sure SPF and DMARC are in place for each domain.
Bug fix: Gmail Pub/Sub wasn't working for certain user accounts where they signed up, disconnected for a while, and then re-connected to GMass.
New setting for bounces: Make bounces disappear instantly
Bug fix: Sometimes when transferring a subscription, a user would get the wrong error, telling them that the transfer-to account doesn't exist when it actually did.
Affiliates: An affiliate's earnings are now accessible via the dashboard.
A "select all" checkbox has been added to certain data tables in the dashboard.
Launched this Product Updates page!
Campaign reports that are inserted into the "GMass Reports" Label will now have the timestamp of when they were generated, so it can be assessed if there's a delay between when the report was generated and when it arrived into the Label.
Bug fix: When logged in as a team master, the user can now take action on its members' campaigns, like pausing/resuming/cancelling/archiving them.
Gmail API began throwing "429" errors. Now campaigns will be auto-retried when they encounter this error.
When an auto follow-up batch errors out, the notification will contain more detail about the error now.
Stage 1 auto follow-ups have been delayed recently. Took steps to optimize speed.
During peak times, the delay between launching a campaign and it starting to send was approaching 3 minutes. Adjusting our server launcher algorithm to bring this closer to 1 minute.
Fixed bug where some "overlimit" bounces from Gmail were erroneously being classified as replies.
Some users are being moved off of shared AWS tracking domains and onto a new set of shared tracking domains.
MultiSend: Better logic to allow other accounts to continue sending when one account in a group hits its sending limit
Bug fix: In rare cases, campaigns with both auto follow-ups and triggers were sending duplicate auto follow-ups to recipients where the trigger had fired
Bug fix: SMTP relay was throwing errors on emails where the "verify" setting was on
Bug fix: The MultiSend helpful butterbar message was appearing at the wrong time when configuring MultiSend settings
MultiSend: Now works when launching campaign with "Create Drafts" option
Bug fix: MultiSend "split factor" calculation was wrong
MultiSend: Removing the aggressive unsubscribe/bounce filtering on campaigns unless Global Unsubscribes/Bounces is turned on
MultiSend: Added butterbar help that appears when you check the box
Better validation for the sending speed field when using MultiSend
MultiSend: Adding aggressive unsubscribe/bounce handling
MultiSend: If campaign is rerouted to user's SMTP server, MultiSend features are now disabled
MultiSend: Validation improvements for emails/day setting. Can now set more than 2,000/day.
Bug fix: Launching a mass forward to a list from a Sheet wasn't working after MultiSend was introduced
Poll improvements: Filtering out bot clicks, and now recording User-Agent and IP for each poll response
You can now cancel a campaign even if your Google account has a broken OAuth connection to GMass
The Reply Project: Delete button wasn't working when viewing campaign-specific replies
The Reply Project: Archive/delete buttons now work with MultiSend campaigns

Join the 200,000+ others using GMass to send their best emails ever

Install in 30 seconds — no credit card or sign up form required

Try GMass for free
Then use the quickstart guide to send your first campaign.