Troubleshooting Email Deliverability Issues

If an email sent via Jobman has not been successful you will see this in the outbox under your contact as well as receive a notification to the user who sent the email. See below error messages and how to troubleshoot emails that could not be delivered.


Error Message:

  • The server was unable to deliver your message (ex: unknown user, mailbox not found).
  • The message was delivered, but was either blocked by the user, or classified as spam, bulk mail, or had rejected content.
  • The subscriber explicitly marked this message as spam.

What to do:

  1. Double check that the email address is correct.
  2. If it is correct, reach out to the recipient directly to let them know their email is not working.
  3. Once their email has been reactivated, submit a support ticket to help@jobman.com to reactivate sending to their email.

Error Message:

  • The server could not temporarily deliver your message (ex: Message is delayed due to network troubles).
  • A temporary DNS error.
  • Unable to temporarily deliver message (i.e. mailbox full, account disabled, exceeds quota, out of disk space).

What to do:

  1. Attempt to send the email again, if it has bounced again contact the recipient directly and get them to check with their email provider.

Error Message:

  • The bounce is actually a virus notification warning about a virus/code infected message.
  • The bounce is a challenge asking for verification you actually sent the email. Typcial challenges are made by Spam Arrest, or MailFrontier Matador.
  • Blocked from this ISP due to content or blacklisting.

What to do:

  1. Double check the contents of the email for any suspicious content or attachments.
  2. Try sending the email again.

Error Message:

  • The recipient has requested an address change.

What to do:

  1. Reach out to the recipient directly and update their email address in Jobman.

Error Message:

  • An error occurred while accepting an email through the SMTP API.
  • Email rejected due DMARC Policy.
  • An error occurred while attempting to render your template.

What to do:

  1. Attempt to send the email again.
  2. If the email continues to bounce send a support ticket to help@jobman.com

Error Message:

  • Address not found.

    Your message wasn't delivered to messaging-service@jobmanmail.com<mailto:messaging-service@jobmanmail.com> because the domain jobmanmail.com couldn't be found. Check for typos or unnecessary spaces and try again.

Why is this happening?

When Jobman sends someone an email, it will be sent from the email address "messaging-service@jobmanmail.com", however, it has a very specific reply-to address to make sure the replies come back into Jobman and are assigned to the appropriate job/lead/contact.

The default behaviour of all email clients when you hit "reply" or "reply all" is to use the reply-to address as the recipient, instead of the from address.

However, if you were to change this address to messaging-service@jobmanmail.com before sending your reply, then it would not have been received by Jobman and you would receive the delivery failure message.

Similarly, if your client is composing their reply and replaces the reply-to address with messaging-service@jobmanmail.com, or has accidentally saved messaging-service@jobmanmail.com as your personal email address, they will receive the delivery failure message.

What to do:

  • Check that you/your client have not been sending replies to messaging-service@jobmanmail.com and/or have not aved this email address as a contact.
  • Go back to the original email that was sent from Jobman, and hit reply or reply all.
  • Check that the email you are composing contains a unique "to" address, e.g. jane-doe+745fcefd4c61ca5d41e4-contact-reply@inbound-qa.jobmanmail.com

Support Tickets

It helps our team investigate faster when support tickets are accompanied with as much information as possible including screenshots, affected users and email addresses.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.