Skip to main content

HTML Email Format should consider <CR> as <br/>

Completed
Nick Coppins

When documents are previewed before sending, non-technical users want to edit the email to include additional information. 

In plaintext format, there is no way to achieve paragraph formatting. All lines are concatenated into one long string. 

In HTML format, they have to know basic HTML (<BR> at least) to achieve reasonable formatting. 

The body field should optionally interpret <CR> (Newline) as <br/>.

1

Comments

15 comments

Date Votes
  • SSP Automation
    Thank you for your request. It has been scheduled for review by the development team that will get back to you should there be questions.
    (Please note that as we are user-driven we can't guarantee that your request will be met unless it gets many votes and/or fit the product vision)
    Read more about the Feature Request process here
    [Internal Id: 21694]
  • Rasmus Jensen

    Hi Nick

    Thank you for your request;

    I assume you mean this screen right?

    If so it actually sounds more like a bug that new-line in the body-field when HTML is not used is treated is not treated as such (please confirm that is what you mean)

  • Nick Coppins

    Hi Rasmus, 

    Perhaps it is a bug of some sort then. 

    Yes, that is the screen I mean. 

    In the image attached, you can see the report action definition, the email preview, and then the email as delivered and viewed in Gmail (including a source snippet). 

    Perhaps it is a Gmail issue?

    Nick

  • Rasmus Jensen

    Hi Nick 

    We have been trying to recreate the issue but have been unable to do so :-(

    a mail sent to Gmail in our system looks fine

     

     

    Could you please try to share what method you send the mail (Outlook, SMTP, or Microsoft Exchange)?

  • Nick Coppins

    Ok, not sure what is happening then.  

    We're using Gsuite SMTP relay (smtp-relay.gmail.com). 

    Content type is set to text/plain as it should be. 

    I'm attempting to test with alternate SMTP servers (Amazon SES / Mailgun) but having trouble configuring these within Boyum, the authentication seems to fail. (Separate issue...)

  • Rasmus Jensen

    Any news on getting an alternative SMTP up and running so we can figure out if issue is a Gsuite Only issue?

  • Nick Coppins

    I cannot get another SMTP provider to work. 

    Amazon SES / Sendgrid / Mailgun. 

    Unencrypted / TLS / SSL all fail with authentication enabled. 

    Only Gmail Relay allows me to use SMTP without authentication, as our IP is whitelisted. 

    Unencrypted & TLS fails with "System.Net.Mail.SmtpException: Failure sending mail. ---> System.IO.IOException: Unable to read data from the transport connection: net_io_connectionclosed."

    SSL attempts timesout.

    I wonder if it is the long string api key passwords these services require? Otherwise I am at a dead end. 

  • Nick Coppins
    • Edited

    Rasmus, 

    I found another SMTP service that allows IP authentication (again, no other form would work)

    Same result, no CR/newline in the emails received.

  • Rasmus Jensen

    Hmm. Could you try and send the mail to another email linked to another email client than Gsuite... or see the received GSuite Mail looks correct on a Phone app.

    also. What localization is your Windows/Browser using? (perhaps you use a special localization that inteperste our linebreaks differently.

    finally. Does this also happen on direct send of the mail or only when the preview screen is used?

  • Rasmus Jensen

    Any update on above reply?

  • Nick Coppins

    Hi Rasmus, 

    Sorry for the delayed reply. 

    • Same issue on Gmail Mobile. (iOS / Android)
    • Localisation is en-AU
    • Happens on both direct send (SMTP) and Preview screen.

    Additionally I cannot get B!UP to work with alternative SMTP providers, having tried about 3 of them. 

     

  • Rasmus Jensen

    Ok, thanks. We will try and recreate it using your localization.

     

    As for SMTP providers, we have not had any open issues on that and we have 1000+ installations around the world so best guess is the SMTPs are incorrectly configured or you have something in your network that prevents their usage

  • Rasmus Jensen

    Hi Nick

    I've finally been able to reproduce the issue :-) ... The issue is that our emails are sent with special char "\r" as line break... It seems that all other email clients but Google see that fine as a line break while Gmail does not.

    So in the next B1UP (2020.08 released start August), we will switch to sending linebreaks as "\r\n" ... The other email clients do not seem to mind that (aka support both) and in Gmail, it is finally interpreted as a line-break

  • Nick Coppins

    Hi Rasmus, 

    That's excellent news. Thank you for your persistence in following this up, really appreciated. 

    Nick

  • Deyanira Hurtado

    Hi,

    Was this fixed? I have a client that has this issue in 4 databases and they are using the version 2022.08.00.1

Please sign in to leave a comment.

Didn't find what you were looking for?

New post