5
Build 9084: Malformed From field in Outlook (MAPI)
Problem reported by Nick Jansen - 11/15/2024 at 1:46 AM
Resolved
I'm running SmarterMail Enterprise on Ubuntu Server 24.04.1 and I upgraded SmarterMail from Build 9056 to 9084. In Build 9084, the From field at the top of new emails ("new" meaning emails that Outlook retrieved for the first time from the SmarterMail server while Build 9084 was installed, regardless of the SmarterMail server build that was running at the time the email was received from the sender by the SmarterMail server) shown in Outlook via MAPI is malformed and appears as follows:
From: Nick Jansen <nick@example.com>; <From: "Nick Jansen" <nick@example.com>;>
Or if the sender didn't have a display name, it looks malformed like this (it shouldn't have From: or the semicolon):
From: nick@example.com;
In Build 9056, it shows correctly as follows:
Nick Jansen <nick@example.com>
Or, for a sender without a display name:
nick@example.com
The From field in Webmail, Thunderbird via IMAP, and the Android Gmail app via EAS, appears correctly. I downgraded back to Build 9056 and the From field appears correctly again in Outlook via MAPI for new emails that Outlook retrieved after the downgrade.

Emails retrieved during 9084 remained wrong after downgrading to Build 9056, but for folders with affected items (just the inbox for me), with SmarterMail Build 9056 running, right clicking the email folder in Outlook, clicking Properties, clicking Clear Offline Items, and letting Outlook redownload all the messages in the folder caused the From fields from the previously-wrong messages to appear correctly again.

I'm using Office 2019 Outlook Version 2410 (Build 18129.20158 Click-to-Run), 64-bit, on Windows 11 Pro 24H2.

17 Replies

Reply to Thread
2
Nageswara Rao Anumolu Replied
Raised a ticket with the same issue.
2
Oliver Replied
Same problem under Windows Server 2022.
4
Gabriele Maoret - SERSIS Replied
Same issue in our testing with a customer on premise on Windows 2019 (upgraded from 8930) --> we downgraded to 8930 again...
Gabriele Maoret - Head of SysAdmins at SERSIS Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
2
Jorel Haggard Replied
Employee Post
Hello everyone,

Thanks for pointing this out. I've got the bug replicated and a task escalated to development.

Best regards,
Jorel Haggard System/Network Administrator SmarterTools Inc. www.smartertools.com
1
Michael Replied
Yup same. Reported this morning. Hopeful for a quick fix. 
2
Randy Alan George Replied
Good morning to you all 
0
Michael Replied
Has anyone heard if a new build will be coming out today or before Monday to solve this?
1
Jorel Haggard Replied
Employee Post
Hello Michael,

As mentioned in the ticket we have open, there likely won't be a build coming out before Monday. 

Thank you,
Jorel Haggard System/Network Administrator SmarterTools Inc. www.smartertools.com
3
Brian Bjerring-Jensen Replied
When we release updates we usually do this on tuesdays. One day to prepare customers and 3 days to fix issues.

When releasing on a thursday and smartertools dont work fridays, then if there is something wrong like malformed from fields then you wont be able to fix this fast.

And how come things like this slips past QC??
1
Sébastien Riccio Replied
Unfortunately, many ugly things seems to pass QC :'-( It's probably not easy to test every function of a product when a new build is release, but there are main mail servers functionalities that should remain rock solid and thoroughly tested.

BTW I think ST work on friday now, since a few months.
Sébastien Riccio System & Network Admin https://swisscenter.com
0
Michael Replied
We're hopeful at least a special build will come out Monday to help resolve this.
0
Richard Laliberte Replied
Just curious, but outside of say MAPI issues like this one, has anyone seen other "do NOT update" issues with the latest version? We currently don't have any clients using MAPI thus aren't having as many hold backs when upgrading.

There used to be a thread created at each release that posted all the updates, and then left open discussion so that people could comment on any / all issues in one spot, did that get discontinued in favor of a report each issue (many times each thread mentions other problems so it's hard to keep track of lol)

We currently have a hosted solution for SM, so we don't have access to read tickets that were submitted, or submit a ticket outside of threads. And with our current hosted solution, we have gotten to the point where we have to tell them "ok, can you please update now" 
1
Brian Bjerring-Jensen Replied
AS an exchange alternative the primary use for us is MAPI/EAS and its critical. We have a 330 MILL USD turnover company running on the server and if we screw up, their lawyers will let us know that we fucked up....
0
John Quest Replied
A very valid and strong point, do not release updates on the last work day of the week.
2
Derek Curtis Replied
Employee Post Marked As Resolution
We will have an update today for the FROM address displaying improperly in Outlook (MAPI). Also, we do have people in the office five days a week and have since the initial Linux release earlier this year.
Derek Curtis COO SmarterTools Inc. www.smartertools.com
0
John Quest Replied
We will have an update today for the FROM address displaying improperly in Outlook (MAPI). Also, we do have people in the office five days a week and have since the initial Linux release earlier this year.

While that may be true, releasing an update on a Friday with no one available for support on the next 2 days is not good business.
1
Nick Jansen Replied
Thanks, this issue is resolved in Build 9088!

Reply to Thread