Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Something weird with Emails/Notifications

Featured Replies

Posted

I set up a notification.

 

Subject is: Testing

Body is: Leak detected in downstairs bathroom

Format is: Text

 

No more, no less. No variables involved either.

 

The e-mail I receive when I test this:

Mime-Version:1.0
Content-Type: text/plain; charset="utf-8"

Leak detected in downstairs bathroom.

 

What's with the first two lines???

Those two lines are email headers, they should not occur in the body. Did you somehow get an extra CRLF into the Subject line? That would cause this. Can you post the raw message you received, headers and all?

  • Author

I think you were right. There was an extra CRLF in there.

 

But if the subject is: ISY ALARM ${alert.details} I get this in Gmail:

 

Subject: ISY ALARM At: 2013/03/03 4:57:24 PM

Body:
Mime-Version:1.0
Content-Type: text/plain; charset="utf-8"

Testing

And I know I didn't leave out a CRLF anywhere. So why the Mime stuff?

 

If the subject is: ${alert.details} ISY ALARM, I get this in Gmail:

 

Subject: At: 2013/03/03 5:01:15 PM

Body:
Testing

No mention of ISY ALARM...

 

Unless I remove the space and write the subject like this: ${alert.details}ISY ALARM

 

Subject:

Body:
ISY ALARM
Mime-Version:1.0
Content-Type: text/plain; charset="utf-8"

Testing

But part of the subject ends up in the body...

 

I'm puzzled...

  • Author

And if I write it like this: ISY ALARM${alert.details} I get:

 

Subject: ISY ALARM At: 2013/03/03 5:08:34 PM

 

Body:

Mime-Version:1.0

Content-Type: text/plain; charset="utf-8"

 

Testing

Hello Traditore,

 

bsobel is right on. Can you please let me know which SMTP server you are using? And, would it be possible to use either gmail or default just to test differences if any?

 

With kind regards,

Michel

  • Author

I'm using smtp.gmail.com, port 587. User ID : my Gmail address. Password: my Gmail password. From*: ISY. Timeout: 1000. Use TLS: checked.

 

I see the *First-Name Last-Name:Email-Address line, but I don't know what it means for the From* field above.

 

I only had time to test one of the possibilities I mentioned before and the result is the same. Using the Default SMTP server, I get this from alerts@universal-devices.com:

 

Subject: ISY ALARM At: 2013/03/04 8:08:55 AM

Body:
Mime-Version:1.0
Content-Type: text/plain; charset="utf-8"

Testing 

Traditore,

 

Would you please send an email to tech@universal-devices.com? I'll send you a URL to an ISY in the lab and, if you don'd mind, please create the content and we'll test. I really cannot reproduce this problem no matter what I tried.

 

With kind regards,

Michel

Guest
This topic is now closed to further replies.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.