shows as utf7
Problem reported by Joe Joe - December 19, 2017 at 9:14 AM
Resolved
Hello,
 
i try to set my txt encoding as utf8,
 
but when i try to send mail to un-existing domain or mailbox,
 
the Delivery Failure mail shows with scramble with non-english words with folowing:
 
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
 
 
how can i change the setting ?
 
SmarterMail Enterprise Edition
Version: 16.3.6526
 
thanks
 

18 Replies

Reply to Thread
1
anhnv mr Replied
Bump, same trouble, at version 15, it's utf8 and quote-printable, up to latest version 16, it's can't change to utf8
0
Joe Joe Replied
what version do you use ? because i check the log,the older v16 shows it is fixed,im not sure if it happnen again on 16.3.6526 ?
0
anhnv mr Replied
at latest version 16, 16.3.6558
0
Joe Joe Replied
ohoh,hope they can find the thread and check it.
0
anhnv mr Replied
ha ha, support smartertools very poor, they don't reply on forum too much
1
Von-Austin See Replied
Employee Post
Joe,
 
I've been able to replicate this same behavior and have written up a bug report for our SmarterMail team to review further. I would expect a fix for this to come in a future minor release.
Von See
Technical Support Supervisor
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
anhnv mr Replied
Thanks you
2
anhnv mr Replied
Hello,
 
I see few release version but this bug still "being fix" status ?
0
Joe Joe Replied
i also have the same question.
1
Von-Austin See Replied
Employee Post
Greetings,
 
Just to keep everyone up to date on the issue, we plan on releasing a fix on 1/18. This is a tentative date and may change depending on what we encounter during this next release cycle. 
Von See
Technical Support Supervisor
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
anhnv mr Replied
hello, any update today ? have this bug fixed yet ?
1
anhnv mr Replied
New version has been release but look like they forgot fix this bug :)
0
Von-Austin See Replied
Employee Post
We are still actively working on a fix for the issue. We were unable to squeeze this fix in on our last release cycle. It will be fixed in the next minor release however.
Von See
Technical Support Supervisor
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Von-Austin See Replied
Employee Post
We are still actively working on a fix for the issue. We were unable to squeeze this fix in on our last release cycle. It will be fixed in the next minor release however.
Von See
Technical Support Supervisor
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
anhnv mr Replied
@Von-Austin See: fix or not ?
0
anhnv mr Replied
They fixed in latest version without notice us :)) bad support
0
Derek Curtis Replied
Employee Post
Actually, it was NOT resolved in the last minor. IT was marked as resolved but did not make it through QC. That said, this has been tested again and will be in this week's release.
Derek Curtis
COO
SmarterTools Inc.
(877) 357-6278
1
Derek Curtis Replied
Employee Post
This is verified fixed and will be in the next minor release. 
Derek Curtis
COO
SmarterTools Inc.
(877) 357-6278

Reply to Thread