We have a clone of our production (pre-BETA) mailserver running with BETA for testing issues.
I checked ~50 customers mailing lists on the clone and can't reproduce the issue.
" seems to be the double quotes char.
The message seems to mean an ending double quote is missing somewhere in a file (probably a json file)
My guess here is maybe that some files related to his mailing list is corrupted, maybe due to the constant crashes you had recently with the crashy build, as SmarterMail tends to leave corrupted json files (really annoying) when crashing.
Have you checked the user's json files related to mailing list?
Maybe one of these is corrupt:
list-subscribers.jsons
mailinglist-data.json
mailinglist-history.jsons
While writing this, I notice there are .jsons file (ending with a s). Is this a thing jsonS files or it's a SmarterMail speciality ?
ps: as we had some crashes on our production server too, I've wrote a little dirty powershell script to check json files integrity recursively from the folder where you start it. This helped us discover broken accounts after a crash before being notified by our customers...
It logs json files that need attention to invalid.txt
I don't know if it would work on .jsons files though, not tested yet as i just discovered there where files named like this.
EDIT: I've edited the script to also check .jsons files as it seems to also work for these files.
Get-ChildItem -Path ".\*.json*" -recurse | ForEach-Object {
try {
$powershellRepresentation = Get-Content $_.FullName | ConvertFrom-Json -ErrorAction Stop;
$validJson = $true;
} catch {
$validJson = $false;
}
if ($validJson) {
Write $_.FullName | Out-File valid.txt -Append
} else {
Write-Host $_.FullName FAILED!
Write $_.FullName | Out-File invalid.txt -Append
}
}