We are running on Enterprise version. But for those who are on the Pro version, your suggestion will be good for ST to upgrade them to Enterprise version.
If we do the archiving of all messages, the storage will grow very large. Is there a way to auto-clean after some time?
The above example is only one case. It affects all users across all domains. We did a check on the logs with many users's inbox folders. It is unlikely all messages are deleted by users. There are no emails on any of the users within the time period. We also check on the Delivery logs, The delivery stops at 08:05am as shown here:
07:57:14  Delivery started for firstname.lastname@example.org at 7:57:14 AM
07:57:23  Added to SpamCheckQueue (1 queued; 0/30 processing)
07:57:23  This message has been quarantined because a virus was found.
07:57:23  Removed from SpamCheckQueue (0 queued or processing)
07:57:26  .eml file not found. Removing .hdr file.
07:57:26  Delivery finished for email@example.com at 7:57:26 AM [id:1664392092138]
08:05:14  Added to RemoteDeliveryQueue (1 queued; 0/50 processing)
08:05:14  Sending remote mail for firstname.lastname@example.org
08:05:14  Spam check results: [_REVERSEDNSLOOKUP: Failed], [BACKSCATTER: passed]
08:05:14  Bounce email written to 1664392092180.eml
08:05:14  Delivery for email@example.com to firstname.lastname@example.org has completed (Bounced)
08:05:14  Removed from RemoteDeliveryQueue (0 queued or processing)
08:05:17  Delivery started for at 8:05:17 AM
08:05:17  Spool message was missing Return-Path; Also missing FROM header
08:05:17  Removing Spool message: Killed: False, Failed: False, Finished: True
08:05:17  Delivery finished for email@example.com at 8:05:17 AM [id:1664392092109]
08:05:20  Added to SpamCheckQueue (1 queued; 0/30 processing)
08:05:20  Launching 'D:\Program Files (x86)\Plesk\admin\bin\smmailfilter.exe' command line exe.
08:05:20  Command line exe finished.
08:05:20  Starting Spam Checks.
08:05:20  Skipping spam checks: Internally Generated Message
08:05:20  Spam Checks completed.
08:05:20  Removed from SpamCheckQueue (0 queued or processing)
08:05:23  Added to LocalDeliveryQueue (1 queued; 0/50 processing)
08:05:23  Starting local delivery to firstname.lastname@example.org
08:05:23  Delivery for to email@example.com has completed (Forwarded Delivered) Filter: None
08:05:23  End delivery to firstname.lastname@example.org (MessageID: <email@example.com>)
08:05:23  Removed from LocalDeliveryQueue (0 queued or processing)
08:05:26  Added to LocalDeliveryQueue (1 queued; 0/50 processing)
08:05:26  Starting local delivery to firstname.lastname@example.org
08:05:26  Delivery for to email@example.com has completed (Delivered) Filter: None
08:05:26  End delivery to firstname.lastname@example.org (MessageID: <email@example.com>)
08:05:26  Removed from LocalDeliveryQueue (0 queued or processing)
08:05:29  Removing Spool message: Killed: False, Failed: False, Finished: True
08:05:29  Delivery finished for at 8:05:29 AM [id:1664392092180]
09:36:27 Relay server stopped at 7/9/2018 9:36:27 AM
09:39:31 Delivery server started at 7/9/2018 9:39:31 AM
09:39:31 Updating ClamAV database...
09:40:10 Updating the ClamAV database has completed successfully
09:43:40  Delivery started for firstname.lastname@example.org at 9:43:40 AM
09:43:40  Delivery started for email@example.com at 9:43:40 AM
09:43:43  Added to SpamCheckQueue (1 queued; 0/30 processing)
09:43:44  Launching 'D:\Program Files (x86)\Plesk\admin\bin\smmailfilter.exe' command line exe.
09:43:45  Command line exe finished.
Our point is this: Emails should never be lost by our email server. We have used MailEnable for 12 years and we have never had any missing emails under any circumstances. There should be never in any case of rarity that emails are ever lost as any of those emails may contain important and legal information to the users. One email lost is just too many.
We have just switched over to Smartermail for barely 1 month. We have faced many critical errors. One is the formatting error and the other are the TCP errors. And now we are facing the missing mails problem, we find that these are not acceptable bugs. All of us will lose customers due to the SM instability program. The customer can TOLERATE us for a while, but not all the times. If we lose customers, so will ST. In additional, This may involve legal action as well for all parties.
ST's reputation is now going down the drain, as we have been religiously following the community and reading the feedback of the users. If ST doesn't buck up, potential buyers will shun away from buying SM.
Therefore, I suggest that ST needs to look into its stability issues before looking at any of added features first. I guess their Quality Control must enhanced further. No customer will accept the reason that different users has different situation if it is a stability issues.