1
Build 8853 released... any issues so far?
Question asked by Brian Bjerring-Jensen - 3/29/2024 at 4:14 AM
Unanswered

Build 8853 (Mar 28, 2024)

                        
  • Added: Domain Hostnames to the auto-SSL process.                                   
  • Fixed: .com.br isn't accepted as a top-level domain suffix for eM Client.
  • Fixed: An email with attachments loses its attachments on forward if a draft is saved prior to sending.
  • Fixed: An exception at login that could cause random logouts or not allow a user to authenticate.
  • Fixed: eM Client (IMAP) failing to connect over secure/insecure connections due to SASL-IR/NTLM issues.
  • Fixed: If you change the system-level hostname to another hostname and a certificate already exists, it will not try to generate a certificate for the new server-level hostname.
  • Fixed: POP AUTH mechanism doesn't properly support an initial client response for NTLM.
  • Fixed: SMTP logs show failed deliveries due to errors of "Could not write HDR file, trying again in 250ms. Exception: Object reference not set to an instance of an object."

7 Replies

Reply to Thread
1
Roger Replied
Hello

There are a few bugs, but they already existed in the previous versions and were reported by me. The developers were able to reproduce them in about 90% of all open cases and will probably be implemented in the next releases.

However, as far as the version itself is concerned, I have not noticed any negative changes compared to the previous versions.

Here is an excerpt of my pending reports of discovered bugs that are currently being processed:

- Chat names are not displayed correctly
- Rename folder in eM Client fails
- Calendar push synchronization on Mac
- Different colors in webmail notes
- Shared contacts in Office 365
- No push notification in eM Client
2
We have IMAP issues (favorite folders with more than one IMAP and more than one MAPI account).

Calendar permissions not changeable in outlook. Has to be done via webmail.
0
Stefano Replied
May I ask what bugs have been known for some time?
0
Roger Replied
Stefano I have wrote it in my message
0
Stefano Replied
I've read it, but I was trying to understand how much "stable" is that version 😅
1
Roger Replied
Hello Stefano

I think this is one of the best versions so far and I have no problems except for the few bugs that have existed for a long time and have nothing to do with this version.
0
John Quest Replied
  • Fixed: SMTP logs show failed deliveries due to errors of "Could not write HDR file, trying again in 250ms. Exception: Object reference not set to an instance of an object."
This problem still exists and has been reported under an existing ticket.

Reply to Thread