Why Some SteepleMate Emails Don’t Send from Your Church Gmail

Why Some SteepleMate Emails Don’t Send from Your Church Gmail

When you connect your church email account to SteepleMate, most messages go out from your church address. Once in a while a member sees SteepleMate or Pentesoft as the sender instead. This article explains why that happens, what SteepleMate does about it on its own, when your church administrator gets an alert, and what you can do to keep your messages coming from your own address.

Why do some SteepleMate emails show SteepleMate/Pentesoft as the sender instead of our church email?

SteepleMate first tries to send every message through your church email account, using the secure app password you gave it. Sometimes Gmail (for example) or the receiving mail server does not accept the message. When that happens, SteepleMate does not give up on the first error:

  1. 1. It tries again. About two seconds later, SteepleMate sends the same message through your church account a second time. Most first failures are a dropped connection or a slow handshake, so the second try usually works and nobody notices anything.
  2. 2. It uses the backup sender. If the second try fails too, SteepleMate sends the message from its own address (support@pentesoft.com) so the email still goes out instead of being lost. Your church's reply-to address is kept, so replies still come to you.

So when members see SteepleMate or Pentesoft as the sender, it usually means: SteepleMate tried to send this as your church's Gmail twice, and Gmail or the receiving server would not accept it either time. SteepleMate then sent it from its own sender so the message could still be delivered.

SteepleMate is Powered by Pentesoft LLC. Learn more about Pentesoft here.

Will our administrator be told when this happens?

Only when it looks like a real problem. A single failure is handled quietly: SteepleMate retries, uses the backup sender if it has to, and does not send anyone an alert.

If your church email settings fail a second time within 24 hours, SteepleMate sends an email with the subject Invalid Email Settings to the person named as the Administrator in your Organization Settings. That email says your messages were sent from the backup address, and it asks you to check your email settings. SteepleMate sends this alert at most once a week, so you will not be flooded. The SteepleMate support team also gets a note with the error so we can help if you contact us.

If you receive that email, follow the steps in the next section.

How do we check and fix our church email settings?

The Email Messaging Feature section of Organization Settings

1. Enable Email: Must be checked for SteepleMate to send from your own account.
2. Email Provider: Choose Gmail, Office365, or your provider. The sign-in steps shown under it change with the provider.
3. Email Account Username: For Gmail, your full Gmail address.
4. Email Account Password: For Gmail, the 16-character app password you generated, typed without spaces. It is not your normal Gmail password.
5. From Email Address: The address your members will see as the sender.
6. Test Email: Sends a test message to your own primary email address, using only the settings on this screen.

To open the screen, choose Administration, then Organization Settings, then open Email Messaging Feature. You will also find the Reply-To address here.

  1. 1. If the Gmail password has been changed or revoked, follow the "Generate App Password" steps on that screen to create a new app password: turn on 2-Step Verification for the Google account, go to App passwords, and generate one for Mail.
  2. 2. Type the new password into Email Account Password.
  3. 3. Click Test Email. Unlike regular messages, the test never uses the backup sender. If it arrives in your inbox, your settings work. If you see "Test Email Failed", the settings still need attention; check them with your email provider.
  4. 4. Click Save.

You need a personal email address on your own member record to use Test Email. If you do not have one, SteepleMate will tell you to add it in the Person Manager.

When does SteepleMate use the backup SteepleMate/Pentesoft sender?

The backup sender is used after the second try fails. That can happen any time Gmail (or the receiving server) returns an error or refuses the message. Common categories:

Gmail account or connection issues

  • * The Gmail app password is invalid, revoked, or changed.
  • * Security settings changed on the Gmail account (for example, 2-step verification or recovery changes) and Gmail starts blocking the connection.
  • * Connection problems between SteepleMate and Gmail (timeouts, network errors) that last longer than a moment.

Gmail sending limits reached

  • * Standard @gmail.com accounts can send about 500 emails per day.
  • * Google Workspace accounts can send about 2,000 emails per day per user.
  • * If a church sends a lot of messages in a short period or to many recipients (especially via SMTP), Gmail may temporarily block further sending from that account.

Gmail flags the message as risky or spammy

  • * The message looks like bulk marketing (lots of recipients, certain keywords, link patterns, etc.).
  • * Very high bounce rate or spam complaint history from that sender.
  • * Attachments are too large or of a type Gmail does not like.

Recipient mailbox or server issues

  • * The recipient mailbox is full or the account was deleted.
  • * The recipient email server is down, overloaded, or temporarily refusing connections.
  • * Greylisting or temporary deferral by the recipient's mail system.

Address or domain issues

  • * A mistyped or invalid email address.
  • * The receiving domain is misconfigured or has strict policies that cause more aggressive rejection of messages.

Whenever Gmail returns one of these types of errors, SteepleMate decides: we still need this message to go out, so let's send it again using our own sending service. That resend is what members see as "from SteepleMate/Pentesoft" instead of the church's Gmail.

Can SteepleMate always tell us exactly why a specific email fell back?

Not automatically inside your admin view. SteepleMate keeps system-wide delivery logs, but those logs include data for all churches, not only your church. For privacy and security reasons, that information is not shown directly in your login.

However, our team can search the logs if you provide:

  • * The recipient email address, and
  • * The rough date and time (and which email it was, if possible).

We can then check the delivery response and let you know what we are able to see (for example, mailbox full, address invalid, sending limit reached). In many cases, the bounce messages from mailer-daemon@googlemail.com already contain a short explanation, but the wording can be very technical or generic.

Can we stop SteepleMate from ever using the backup sender and force it to only send from our church email?

For SteepleMate as it is today: if the church's email refuses or cannot send the message, SteepleMate has only two options:

  1. 1. Use the backup SteepleMate/Pentesoft sender, or
  2. 2. Not send the message at all (let it fail).

SteepleMate chooses option 1 to avoid lost messages. That means there is no way to guarantee that every email will always show the church's email address, because external systems (Gmail and the recipient's server) can always reject or delay messages.

What can we do to reduce how often SteepleMate uses the backup sender?

You cannot remove the possibility entirely, but you can reduce how often your emails are rejected. Here are practical steps:

Stay within Gmail's sending limits

  • * Avoid large "email blasts" from a free @gmail.com account.
  • * For heavier sending, consider a Google Workspace account, which has higher limits and is designed for organization mail.

Keep mailing lists clean

  • * Regularly remove old addresses that always bounce.
  • * Fix obvious typos (like name@gmial.com).
  • * High bounce rates hurt sender reputation and increase the odds that Gmail or recipients will refuse your messages.

Encourage members to "trust" the church email

  • * Ask members to add the church email to their contacts.
  • * Ask them to mark any messages in spam as "Not spam." This helps future messages land in the inbox.

Keep content "church-friendly" and low-risk

  • * Avoid "spammy" patterns: lots of ALL CAPS, too many links, strange attachments, etc.
  • * Use clear subject lines (for example, "This Sunday's Service Details" rather than clickbait-style lines).

Watch for Gmail security changes

  • * If someone changes passwords, security settings, or 2-step verification on the church Gmail, you may need to generate a new app password and update it in Organization Settings (see "How do we check and fix our church email settings?" above).
  • * If you receive an Invalid Email Settings email from SteepleMate, check your settings the same day. Until the problem is fixed, SteepleMate will keep using the backup sender.

Use a custom domain with proper authentication (when applicable)

  • * For churches on Google Workspace using a custom domain (like office@churchname.org), make sure SPF, DKIM, and (ideally) DMARC are properly set up and passing. This helps Gmail and other providers trust the email.

Why do some backup-sender emails go to members' spam or junk folders?

When SteepleMate uses the backup sender, the email comes from a different "From" address and domain than the one members are used to. Spam filters look at consistency: are messages coming from the same domain that recipients normally interact with? If members are used to seeing churchname@gmail.com and suddenly see a pentesoft.com address, their email provider may treat it more cautiously at first, and that can lead to spam placement.

You can suggest that members:

  • * Add the SteepleMate/Pentesoft sender to their contacts, or
  • * Mark those messages as "Not spam" if they land there.

This helps train their mailbox that these emails are safe and expected.

How should we explain this to our congregation or staff?

You can use language like:

> Our church email is integrated with SteepleMate, which sends most messages directly from our church address. Occasionally, when Google cannot send a message (for example, because of limits or technical issues), SteepleMate tries again, and if that still does not work it uses a backup sender so your message is not lost. If you ever see a message from SteepleMate or Pentesoft, it is still from us. It just used that backup path.