| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0000141 | SKGB-intern | public | 2014-09-29 15:44 | 2015-10-18 23:46 | |||||
| Reporter | aj | ||||||||
| Assigned To | aj | ||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||
| Status | resolved | Resolution | fixed | ||||||
| Projection | tweak | ETA | > 1 month | ||||||
| Platform | The Web | OS | HTTP | OS Version | 1.1 | ||||
| Product Version | 1.3.1 | Product Build | 2014-09-28 | ||||||
| Target Version | 1.3.3 | Fixed in Version | 1.3.3 | ||||||
| Summary | 0000141: Don't send semicolon separators in email addresses | ||||||||
| Description | Certain non-compliant software (e. g. MS Outlook) use ";" for separation of email addresses instead of "," as required by RFC 5322. Email addresses use ";" along with ":" for group definition, which we don't use; separation of multiple single addresses both within and without groups is done with a comma (","). It shouldn't be difficult to have SKGB-intern replace unescaped semicolons that aren't preceded by colons (a construct that would not be in compliance with the Internet Message Address Specification) with commas. ("Do What I Mean") | ||||||||
| Steps To Reproduce | wrong: a@example.org; b@example.org correct: a@example.org, b@example.org | ||||||||
| Additional Information | http://tools.ietf.org/html/rfc5322#section-3.4 The behaviour of Outlook (among some other clients) is forbidden by the IETF specification. The SKGB-intern behaviour suggested in this issue would be permissible. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
aj (manager) 2015-10-18 23:03 |
freenet.de rejects incoming mail with such malformed adresses in the Reply-To field, a behaviour that is probably a violation of the RFC, too |
|
aj (manager) 2015-10-18 23:06 |
As of 1.3.3 the user is presented with an error message if Reply-To or From contain colons or semicolons. That behaviour solves this issue at the (quite neglegible) cost of no longer supporting group syntax. |
| Notes |