Firetrust Support Forums

Went to URL provided in Chrome.
Created a Registration.
Entered and it created an Error Message "KABOOM" but it did set up an account.

BUG - PROBLEM - MWP will not allow the use of an email address as a UID so I could not do a Sync.

Set up one of my accounts manually and it did a Fetch Mail just fine.

More later.

Automatic Port & SSL Settings for Verizon were incorrect.

Port should be 995

SSL should be enabled.

Thanks, there's definitely something funny going on there as I can setup GMail and Outlook.com and GMX accounts all ok as they all have email addresses as usernames, but a Yandex.com I"m having difficulty with.

The error message was 'KABOOM''? I know next week we're also working on form and global errors.

We'll add back in all the automatic populating of account settings too.

Bug Report in new MWM release.

New mail count indicator on App Icon not being cleared after inbox viewed.

Problem with msg header display in inbox.

When I Use the new mail notification on the lock screen and slide it it does not trigger a new mail sync.

We don't have new mail notifications in it yet, so perhaps you're looking at the old version?

nick.bolton wrote:We don't have new mail notifications in it yet, so perhaps you're looking at the old version?

Not the old version. The badge icon is the new one and the indicator on the new app icon changes as a new number of msgs comes in

ok, head scratcher alright. I'll check the IOS version a bit later in the office - don't have one here at the moment.

nick.bolton wrote:ok, head scratcher alright. I'll check the IOS version a bit later in the office - don't have one here at the moment.

Sending you an email with 2 SC from my IPad. Don't think it's relevant but I also had the new version running as a URL in a browser.

Also thought maybe the the updated one to fix the install problem has some later code changes that are the start of the changes for notification.

Thanks, we'll get to the bottom of it today. Looks like the app wrapper is doing something without us having the notifications actually matched to the server.

The notification certificate is for the old version, but it's not yet implemented. It's an Apple thing because we're using the same name as the old version it still sends notifications.