This is a practical follow-up to our general Sage 50 guide for Panama. If you already have Sage installed and just need to configure email so you can send statements and invoices to clients, this is the guide you need. We cover the most common providers and the fixes for the typical errors we see in the workshop every week.

Why it fails so often

Setting up email in Sage looks simple in theory: enter the SMTP server, port, user and password, and you are done. In practice it fails for these reasons:

  • Microsoft changed the authentication rules. It no longer allows normal passwords in external applications.
  • Gmail also requires app passwords, since 2022.
  • Some hosting providers block SMTP ports by default.
  • Sage is not a modern mail client. It does not support OAuth, so it depends on “app passwords” generated specifically for it.

Most of the errors we see are not Sage problems — they are mail account configuration problems. And solving them means knowing the quirks of each provider.

What you need before you start

Before touching Sage, have this information ready:

  1. An active email account you will send from (typically the business one: sales@company.com, invoices@company.com).
  2. The account password, or the ability to generate an app password (more on this below).
  3. 2FA enabled on the account if you use Microsoft 365 or Gmail (it is a requirement).
  4. Your provider’s SMTP details (we list them below).

Setup with Microsoft 365 / Outlook

The most common option at Panamanian companies. If you use Outlook with a Microsoft 365 account (a work address, whether on your own domain or not), these are the details:

SMTP details

  • SMTP server: smtp.office365.com
  • Port: 587
  • Encryption: STARTTLS (sometimes shown as “TLS” or “SSL/TLS”)
  • User: your full email address (you@company.com)
  • Password: an app password, not your normal password

The password problem with Microsoft 365

Microsoft no longer allows applications like Sage to use your normal password directly. You need a specific app password. The steps:

  1. Enable two-step verification (2FA) on your Microsoft account. Without it you cannot generate app passwords.
  2. Go to https://account.microsoft.com/security → Advanced security options.
  3. Find App passwords → Create a new app password.
  4. Give it a descriptive name (for example: “Sage 50 invoice sending”) so you can identify it later.
  5. Microsoft generates a 16-character password (something like abcd efgh ijkl mnop).
  6. Copy that password. It is only shown once. If you lose it, generate another.
  7. Paste it into Sage as the SMTP account password.

For corporate Microsoft 365 accounts on your own domain

If your account looks like you@yourcompany.com and is managed by Microsoft 365, the steps are the same, but sometimes the IT administrator has to enable authenticated SMTP from the admin center. Without that, the app password will not work even once generated.

If you are the administrator or have access:

  1. Microsoft 365 admin center → Users → Active users
  2. Select the user → Mail → Manage email apps
  3. Enable Authenticated SMTP
  4. Wait a few minutes for it to take effect

If you are not the administrator, ask IT with this exact wording: “I need authenticated SMTP submission enabled for this account.”

Setup with Gmail / Google Workspace

For users with a personal Gmail account or Google Workspace for business:

SMTP details

  • SMTP server: smtp.gmail.com
  • Port: 587
  • Encryption: STARTTLS
  • User: your full Gmail address
  • Password: an app password generated in Google

How to generate the app password in Google

  1. Enable 2-Step Verification on your Google account. Without it you cannot generate app passwords.
  2. Go to https://myaccount.google.com/apppasswords.
  3. Choose “Other (custom name)” and name it: “Sage 50”.
  4. Click Generate.
  5. Google shows you a 16-character password.
  6. Copy it and paste it into Sage as the SMTP account password.

If Google blocks it as a “suspicious sign-in attempt”

The first few times you send from a new IP address, Google sometimes blocks it for security. What to do:

  • Check myaccount.google.com/notifications for a security alert and confirm the activity was yours.
  • Sometimes you have to wait a few hours after generating the app password before everything works.

Note that the old “Less secure app access” option no longer exists: Google removed it, and an app password on an account with 2-Step Verification is now the only supported route for programs like Sage.

Setup with email on your own domain (cPanel, traditional hosting)

If your email is on your own domain but does not use Microsoft 365 or Google Workspace (the typical cPanel setup from a hosting provider), ask your provider for these details:

  • The outgoing SMTP server (something like mail.yourcompany.com or smtp.yourcompany.com)
  • The port (usually 587 with TLS or 465 with SSL)
  • Whether SMTP authentication is required (typically yes)
  • User: your full email address
  • Password: your mailbox password (on this kind of service the normal password does work)

Those servers typically have none of the complicated restrictions Microsoft or Google impose. If you have the right details, it works on the first attempt.

Testing that it works

Once it is configured in Sage:

  1. Go to the client you want to send to (any client with an email address on file).
  2. Generate a statement or report.
  3. Click Email.
  4. Check the recipient’s inbox.

Good practice: test by sending to yourself first. Create a test client with your personal email, send it something, and check it arrives properly. If it does, everything is fine. If not, work through the common errors below.

Common errors and fixes

”Cannot connect to the SMTP server”

Possible causes:

  • The server or port is mistyped. Check it letter by letter.
  • A firewall or antivirus is blocking the outbound port. Add an exclusion for Sage.
  • The premises’ internet connection blocks the SMTP port (uncommon, but it happens with some ISPs).

”Authentication failed” or “535 Authentication failed”

Cause: the password is wrong. With Microsoft 365 and Gmail especially, it must be an app password, not the account’s normal password. Generate a new one following the steps above.

”The email sends but lands in spam”

Causes and fixes:

  • If you use a free address (personal Gmail, personal Outlook) to send invoices, it is very likely to land in spam. For business, use email on your own domain.
  • SPF, DKIM and DMARC are missing from the domain’s DNS records. These are authentication records that tell receiving servers your mail is legitimate. Without them, automated mail looks suspicious.
  • If the message content has typical spam wording (“urgent”, “unpaid invoice”, lots of capitals), it can also be filtered on content. Review the templates in Sage.

”Sage freezes when trying to send”

Causes:

  • An out-of-date Sage version. Some older versions do not support modern TLS.
  • An unstable internet connection. Check with another app.
  • Antivirus blocking the operation. We covered antivirus exclusions in the general Sage 50 guide.

”Error 421” or “Service not available”

Common cause: Microsoft or Google detected suspicious activity and blocked it temporarily. Wait 30 minutes and try again. If it persists, check the account in the provider’s portal for pending security alerts.

The email sends but attachments arrive empty or corrupted

Cause: a problem with the export format. Check:

  • In Sage, the export format: PDF (do not use Excel for external sending)
  • The file size: over 25 MB, Microsoft and Gmail reject it
  • Permissions on the temporary folder where Sage generates the files

When you need a technician

If after working through all the points above it still does not work, it is probably one of these:

  • The mail domain configuration (SPF/DKIM/DMARC) needs DNS knowledge
  • The corporate Microsoft 365 account needs changes from the IT administrator
  • The machine running Sage has very specific network or antivirus problems
  • The Sage version is old and needs updating

Any of these we resolve in one remote support session. The typical total time is 30–60 minutes. And it keeps working from then on.

Summary

  • Microsoft 365 and Gmail require an app password, not the normal password.
  • Enable 2FA first — without it you cannot generate app passwords.
  • Server smtp.office365.com:587 for M365, smtp.gmail.com:587 for Gmail.
  • For domain email on cPanel, ask your provider for the details.
  • If it lands in spam, configure SPF/DKIM/DMARC in the domain’s DNS.

Cannot get email working in Sage? We will get it running over remote support in a short session. Message us on WhatsApp with the mail provider you use and the error you are seeing.