Trust Sender, Block Sender, Untrust Sender Not Working on UTF-8 Encoded Addresses
Problem reported by Scarab - 3/21/2024 at 4:12 PM
All three functions; TRUST SENDER, BLOCK SENDER, and UNTRUST SENDER in the webmail do not work on any emails where the RETURN-PATH: header is either Null <> or UTF-8 Encoded (i.e. =?utf?q?=3Cbounce-1234=5F=40bounce=2Fexct=2Epu?==?utf-8?q?domain=2Ecom=3E?=). No error is thrown, and the only way you can tell that something is wrong is that there is no green box confirmation in the lower-right stating that the action is successful. The Trusted Senders and Blocked Senders remain unchanged.

This is confirmed to occur in the most recent Build 8839 but seems to have been occurring for some time.

I understand why this is not working with Null <> values (once upon a time these did work with Null <> values and untold horrors were unleashed because of it), but it should be able to decode any encoded addresses and take action upon them it seems.

Not entirely sure if intended by design or a bug.

4 Replies

Reply to Thread
Kyle Kerst Replied
Employee Post
Do you get a console error in the web browser Developer Tools area when this happens? If you can open a ticket on this and submit an example EML I can get this escalated for you!
Kyle Kerst System/Network Administrator SmarterTools Inc. (877) 357-6278 www.smartertools.com
Scarab Replied

There is indeed a JS TypeError in the DevTools upon attempting to Block Sender/Trust Sender/Untrust Sender. It is as follows:

TypeError: l.returnPath is undefined
    U /interface/output/site-v-638460392620000000.js:39
    blockSender /interface/output/site-v-638460392620000000.js:39
    Angular 7

As per your request I will open a Support Ticket (already have another one open for other issues).
Scarab Replied
Discovered another instance where these three functions fail with the same JS error:

The Return-Path is a legacy address (RFC 2822 which was superseded in 2008) and does not contain angled brackets as per RFC 5322 (i.e. va049979@hopital-landerneau.fr instead of <va049979@hopital-landerneau.fr>). As these legacy addresses which do not conform to RFC are still able to be delivered and displayed in webmail these should be able to be Trusted or Blocked or Untrusted.
Webio Replied
Already opened ticket - 0C4-2D7AFFB7-0B07 on 6th of march. Based on latest response issue has been forwarded to devs for further review.

Reply to Thread