Common issues for e-faxes and scanners

Scan to email:

• Some scanners connect via smtp using an email account.
• This will cause an issue if the sender email account (account used to connect via smtp) is transitioning over to a Paubox email hosting.
• In order to fix this issue, you will need to reconfigure the SMTP server settings on your application
  • username: <Paubox email address>
  • password: <Paubox email password>
  • server: m.paubox.com
  • port: 587
  • security: STARTTLS (or TLS)

E-Faxes - from email to e-fax software:

• Some e-fax software follows this process flow:
  • Compose an email
    • to: faxnumber@faxcompanyname.com
    • subject: (sometimes requires a code generated by the e-fax software company)
    • body: completely blank
    • attachments: (this is what will be faxed)
  • If the e-fax software company specifically states that the body of the email must be completely blank, then most likely there will be an issue when you attempt to send an email to the e-fax software.
  • This could be for one of two reasons.
    1. The Paubox encryption footer will get added to the message body and may error out the e-fax system.
    2. The e-fax company may not support up-to-date TLS connections and the email will get converted into our secure notification email sent from our Rails application.
  • In order to resolve this, the e-fax company's domain (*@faxcompanyname.com) should be placed on the non-encrypted recipient list so that modern TLS encryption is not enforced to send the message. In order to configure this, please submit a request and include the e-fax email address that you use to send to.