SimpliServDocs

Check email sending and fix errors

Systematically check SMTP, sender, recipient, email statistics, failed attempts and resending

→ Open SMTP settings · Open email statistics

When an email doesn't arrive, first distinguish between not sent, technically failed, accepted but not yet delivered and delivered but filtered by the recipient. The email statistics show the stored sending status (Sent, Failed, Pending) and the error text. How sending and layout are set up is covered in Send emails and check delivery.

Quick check

Check message and recipient

Open the record or the email statistics. In a record's conversation an email shows Sending while sending isn't confirmed, and Send failed when the mail server reported an error. Check address, subject and attachments.

Read the error text

Click the row in the statistics. The detail view shows from, to, CC/BCC, time, number of attempts and, under Send error, the mail server's original message.

Check sender and SMTP

In the email settings, check host, port, encryption, username, password and From email address. Don't change credentials if you don't know whether they are an app password or a normal password.

Send a test email

Save corrections and send a single test message to an internal address via Send test email. The message "Test email sent" only means it is queued – you see the result in the statistics shortly afterwards.

Only then resend

Trigger the actual email only once the test email arrives. Avoid repeating the same invoice or dunning letter several times.

Common errors

SMTP login failed

Check username, password or app password. Many providers now require an app password or an enabled SMTP login. Also check that the SMTP host belongs to the mailbox.

Connection or port failed

Check hostname, port and encryption as a combination. Ports 465 and 25 are blocked on our servers – use 587 with TLS (button Switch to 587). TLS/STARTTLS and SSL are not interchangeable; if in doubt, ask your mail provider for the current SMTP details.

Emails come from the wrong sender

If the SMTP card is incomplete (for example without encryption or without a sender address), SimpliServ silently uses its default sending instead of your server. Fill in all required fields and save.

Sender not allowed

The SMTP account may only be allowed to use its own address or a verified alias. Use an approved sender address or adjust the provider's permissions.

Recipient rejected

Check typos, invalid addresses and temporary provider errors. If only one domain is affected, the recipient domain may reject or quarantine the message.

Message sent but not visible

Check spam, quarantine and server-side rules at the recipient. Also compare the sender address and delivery time. An accepted send is no guarantee that the message lands in the inbox.

Resend without duplicates

You retry a failed email from a record in its conversation with Retry sending. Before that:

  • check the status in the statistics,
  • check whether the recipient may already have received the message,
  • don't change the document number or content unnecessarily,
  • for invoices or dunning letters, document why you sent again.

If you prefer to send a document outside SimpliServ, choose Commit Only when finalising or download the PDF – SimpliServ then doesn't create an additional email.

Don't send several times just because the inbox hasn't refreshed yet. Check status, error text and the recipient's spam filter first.

Attachments and templates

If only the attachment is missing, check document status, PDF generation and file size. The detail view in the statistics lists the attachments that were actually sent. For invoices, estimates or delivery notes, attachments are assembled from the document context. An email template doesn't change the document layout.

What an administrator should document

  • SMTP provider and sender used,
  • time of the test,
  • full error text without passwords,
  • affected recipient domain,
  • whether a test email was delivered internally,
  • whether the provider or DNS configuration was changed.

Passwords, app passwords and tokens don't belong in tickets, notes or screenshots.

How is this guide?

On this page