Back to Community Threads
1
SMTPUTF8
Question asked by Sébastien Riccio - 2/29/2024 at 1:17 PM
Unanswered
Hello,

While trying to troubleshoot recent outgoing mail (SMTP) issues for a customer using Outlook, I noticed in the SMTP log in that his mails are rejected by SmarterMail because of: 

555 Unsupported parameter: SMTPUTF8

It seems that Outlook doesn't care if SMTPUTF8 support is announced or not in capabilities returned by the server and try to use the parameter anyway.

After being authenticated, Outlook sends:

MAIL FROM: <some@mailaddress.tld> SMTPUTF8

And as SMTPUTF8 is not supported by SmarterMail, it is rejected.

Now I don't understand why Outlook would use SMTPUTF8 here, as far as I know, it is only needed if you use international chars in e-mail addresses, and this is very rare imho.

Still, I've searched the SMTP logs on our SmarterMail install for "555 Unsupported parameter: SMTPUTF8" and there are a huge amounts of matches.

Are you also seeing a lot of these in your systems ?

Kind regards
Sébastien Riccio
System & Network Admin

12 Replies

Reply to Thread
1
No results here when searching SMTP logs.
0
Sébastien Riccio Replied
2/29/2024 at 2:37 PM
Ok thank you. Very strange then...
Sébastien Riccio System & Network Admin https://swisscenter.com
1
echoDreamz Replied
2/29/2024 at 3:17 PM
Same, nothing 
SMTPUTF8
Related in our logs either.
1
No results here too when searching "SMTPUTF8" in SMTP logs....
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)
0
Sébastien Riccio Replied
2/29/2024 at 4:34 PM
Ok thanks for the feedbacks. Are your SMTP logs set to detailed ? I think they pop only in detailed mode.
If they are then I'll have to dig deeper at our side to understand what's going on.
Sébastien Riccio System & Network Admin https://swisscenter.com
1
Yes, my SMTP log is set to "detailed"...
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)
1
echoDreamz Replied
2/29/2024 at 4:49 PM
Same, SMTP logs are "Detailed".
1
Kyle Kerst Replied
2/29/2024 at 4:53 PM
Employee Post
I wasn't able to find any references to this error across the various test servers we sync to either.
Kyle Kerst IT Coordinator SmarterTools Inc. www.smartertools.com
0
Sébastien Riccio Replied
2/29/2024 at 5:03 PM
Thank you again for the feedbacks. I'll investigate this more deeply at our side then.

Kind regards
Sébastien Riccio System & Network Admin https://swisscenter.com
0
J. LaDow Replied
2/29/2024 at 9:41 PM
Our logs are set to detailed, we went back 15 days and have not seen that in our report - we are not on the latest version though -- still running build 8657 -- not sure if that helps when tracking this issue.
MailEnable survivor / convert --
0
Sébastien Riccio Replied
2/29/2024 at 10:47 PM
Thank you all.

After checking all our SMTP logs containing a huge amount of these entries, they seems to be linked to only a few users but repeated multiple times per hour.

I hope it's not users that have their Outlook updated to the latest version that triggers this issue...

I keep on digging...
Sébastien Riccio System & Network Admin https://swisscenter.com
1
Sébastien Riccio Replied
3/1/2024 at 12:30 AM
Well I found the issue while working on it with one of our affected customer.

These customers mistakenly tried to send a mail to a mail address CONTAINING an accented character, and this trigger the need of SMTPUTF8 (not supported by SM).

The mail is then stuck in the Outlook outbox and it keeps on retrying sending it over and over again.

But then there is a side effect to this. When the customer tries to delete the mail from the Outbox, Outlook will want to move it to Deleted items, and this brings another problem as Outlook then tries to sync the Deleted item with the server (through IMAP) and this is also rejected by SM.

I was able to reproduce all this with a test mailbox and Outlook with IMAP/SMTP and a mail that has at least on recipient having an accent in the address.

The outlook syncher returns this when tried to sync the deleted item (sorry for french log):

08:28:52 Synchronisateur Version 16.0.17328.20108
08:28:52 Synchronisation de la boîte à lettres 'madjik@cybermind.ch' en cours
08:28:52 Synchronisation des modifications locales dans le dossier « Deleted Items » en cours
08:28:52 Erreur lors de la synchronisation du message 'test stufff'
08:28:52 		 [800CCE46-0-0-322]
08:28:52 Terminé
So well, it seems the situation can be resolved by using shift-delete instead of delete when deleting the stuck mail, but that's still an interresting issue...

To summarize:

1) SMTPUTF8 is pure useless crap (as are IDN domain names)
2) But still, it is supported by quite some clients and mail services so SM might want to consider supporting it too. However because of 1) i understand it's not a top priority...
3) Outlook should not attempt to send the mail when it requires SMTPUTF8 but the feature is not advertised by the SMTP server.

Kind regards
Sébastien Riccio System & Network Admin https://swisscenter.com
Back to Community Threads

Reply to Thread

Related Knowledge Base Articles

Slow 250 response after Mail From command is issued during an SMTP session.SmarterMail > Troubleshooting
Automatic SSL Certificates on a New SmarterMail ServerSmarterMail > Server Configuration and Management
Set up SmarterMail as an IIS Site in IIS 8SmarterMail > Server Configuration and Management
Recommended SPAM SettingsSmarterMail > Antispam and Antivirus
Resolving SMTP Failures on AWS-based ServerSmarterMail > Server Configuration and Management