This message is no longer on the server. This message is a replacement for the missing message.
Question asked by Scarab - 6/10/2020 at 4:29 PM
Answered

Oh boy! Just upgraded to Build 7549 Enterprise version from Build 7242

Customers are contacting us non-stop because the majority of messages they are retrieving via POP or IMAP say as follows:

From: System Administrator
To:
Date: Wed, 10 Jun 2020 11:42:52 -0700
Subject: Message removed

This message is no longer on the server.
 
This message is a replacement for the missing message.

There is a X-ESETId: Header on the last line of these messages but we don't use ESET and neither do the customers affected.

These replacement messages are not displayed in the webmail interface, only in email clients using POP or IMAP.

Anyone know what this is, what is causing it, and how to stop it? There is no system message configured in SmarterMail that does this.

14 Replies

Reply to Thread
0
Scarab Replied
Found out that this is something from the Beta.

https://portal.smartertools.com/community/a93159/beta-pop3-message-removed.aspx

Apparently it crept back into the Final Release Build.
0
Sébastien Riccio Replied
Hello Scarab,

Do you have anything in IMAP and/or POP logs that looks like: "message could not be found"  ?
In POP3 logs we have tons of:
RETR failed to FeedMessage for message 4 (UID: 15540) ERR: The group file F:\SmarterMail\Domains\xxx.ch\Users\gilles\Mail\Inbox\2020_5_27.grp is corrupt or a message could not be found in the header..

In IMAP:
[2020.06.11] 00:58:29.347 [188.x.255.x][37227440] Failed to fetch data item 17047 from GRP file for sabxxxxnr@saxxxna.ch in Inbox.


We're having customers reporting the same "This message is no longer on the server. " and our imap/pop3 logs are full of this.

Kind regards,
Sébastien

Sébastien Riccio
System & Network Admin

0
Josh Pickering Replied
Employee Post
Quick update here, I have opened up a ticket with Scarab, and it looks like Sebastien is already working with us on his issue. I will update here when I have more information.
Josh Pickering
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Sébastien Riccio Replied
Well, I was told that this come from an issue in earlier beta versions that affected the users mailbox but it can't be, because we updated our prod server straight from 7242 to the mapi release, no beta was insalled on our prod server!

Still no solution provided and we're in deep trouble... :(


Sébastien Riccio
System & Network Admin

1
Sébastien Riccio Replied
Multiple customers already moved to another service provider since we applied the update as we can't satisfy them with a stable service anymore. We must in emergency move some customers to another mail system so we don't lose them, it's really painful.

Sébastien Riccio
System & Network Admin

0
Scarab Replied
Josh, I responded to the Support Ticket with compressed archives of our Logs and multiple accounts. We did not install any Beta Builds in between versions.

Sebastien, you are correct. For POP users who are receiving a replacement message have the following in the detailed POP Logs "RETR failed to FeedMessage for message X (UID: XXXXX) ERR: The group file D:\SmarterMail\Domains\domain.tld\Users\username\Mail\Inbox\2020_6_10.grp is corrupt or a message could not be found in the header."

For IMAP users, especially MS Outlook users, they are getting the following error in their clients: "The UID of a message changed unexpectedly. This typically indicates a server bug. Your program may not function properly after this." In the detailed IMAP logs we have "Failed to fetch data item 21013 from GRP file for username@domain.tld in Inbox."
0
Tim Uzzanti Replied
Employee Post
We believe the issues is resolved in our upcoming release today. Its was a timing issue.
Tim Uzzanti
CEO
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Scarab Replied
Thank Tim, we'll cross our fingers and give the updated version a whirl in the early morning hours of the morrow.
0
Sébastien Riccio Replied
Hello,

After updating to the latest release we're still seeing logs entries for corrupt grp in POP and IMAP logs.
We really need to find a solution, many customers are complaining and asking what is going on.

Can you please elaborate what do you mean with "a timing issue". We also need a confirmation that there is no possibility of  lost e-mails because of this issue.
Multiple customers claimed to have lost content and asked us to restore their mailboxes from backups.

Kind regards.
Sébastien Riccio
System & Network Admin

0
Sébastien Riccio Replied
Hello, any news on this issue? We already got this morning a whole bunch of customers (most on POP3) having again new mails in their mail client with the content:

This message is no longer on the server.

This message is a replacement for the missing message.

It's really a mess and we have no idea what to do.

Scarab may I ask you if on your site the issue still persists too after the update to friday's build?

ST Please help us!

Sébastien Riccio
System & Network Admin

0
Scarab Replied
Sebastien,

Yes, we are still having the issue even after installing Build 7468. 

ST opened a Trouble Ticket for us and we are working with them, providing them logs, accounts, and remote access so that they can better isolate the issue.

It does look like a transient issue. The accounts affected one day are not the same accounts affected the next day, and thankfully it's a small number of accounts affected (the most we've had are 11 POP accounts and 9 IMAP accounts, the low has been just 3 POP and 1 IMAP).
0
Sébastien Riccio Replied
Hi Scarab and thank you for your feedback. Based on our logs we have ~350  accounts affected on 20k total.
Most complaints come from POP users, but my guess is that this is not handled the same for IMAP and POP....
I have good hopes that ST team will find and fix the issue.

Kind regards
Sébastien Riccio
System & Network Admin

0
Sébastien Riccio Replied
Hmm Scarab, what's your server timezone set to, if I may ask ? Maybe I'm wrong but... I might have an idea about this.
Sébastien Riccio
System & Network Admin

3
Tim Uzzanti Replied
Employee Post Marked As Answer
We have a hot fix on a couple customers servers.  It is what I had mentioned previously, a timing issue which could cause an exception.  In these situations the backend thinks the message count is one higher than it really is. The previous public release had part of the fix but it required an additional code change.  Next release this will be fix will be included.
Tim Uzzanti
CEO
SmarterTools Inc.
(877) 357-6278
www.smartertools.com

Reply to Thread