Mailaddresses with exclamation mark like !blasuelz@redacted are wrongly quoted. ("!blasuelz"@redacted)

REOPENED
Unassigned

Status

MailNews Core
MIME
REOPENED
2 years ago
9 months ago

People

(Reporter: klaus-martin.hansche, Unassigned, NeedInfo)

Tracking

({regression})

x86_64
Windows 7
regression

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150806103657

Steps to reproduce:

Start a new mail dialog.
Search for blasuele in addressbook. (LDAP)
Use result '!blasuelz@redacted'
Compose mail.
Send mail.



Actual results:

Mailserver says mail-address '"!blasuelz"@redacted' (single quotes by me) is not deliverable.
This happens since 38.0.


Expected results:

Mail-address shouldn't be quoted this way.
(Reporter)

Updated

2 years ago
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64

Updated

2 years ago
Component: Untriaged → MIME
Product: Thunderbird → MailNews Core

Updated

2 years ago
Keywords: regression
According to RFC 5322, "!" is not a valid character for a bare local part. So the local part must be quoted. The mail server is broken.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID

Updated

2 years ago
Duplicate of this bug: 1203526

Updated

2 years ago
Summary: Mailaddresses like !blasuelz@redacted are wrongly quoted. ("!blasuelz"@redacted) → Mailaddresses with exclamation mark like !blasuelz@redacted are wrongly quoted. ("!blasuelz"@redacted)
Sorry, "!" was a valid character as written in the duplicated bug. (I don't remember why I got the wrong idea.)
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INVALID → ---

Comment 4

2 years ago
! is valid in UUCP bang path addressing so should be quoted no?
RFC 976 does not require quoting for hybrid addresses such as a!b@c.d.

Comment 6

9 months ago
another mime regression?
Regression if it worked in TB 24.
Latest rfc5322 : https://tools.ietf.org/html/rfc5322
> addr-spec       =   local-part "@" domain
> local-part      =   dot-atom / quoted-string / obs-local-part
> dot-atom        =   [CFWS] dot-atom-text [CFWS]
> dot-atom-text   =   1*atext *("." 1*atext)
> atext           =   ALPHA / DIGIT /    ; Printable US-ASCII
>                     "!" / "#" /        ;  characters not including
>                     "$" / "%" /        ;  specials.  Used for atoms.
>                     "&" / "'" / "*" / "+" / "-" / "/" / "=" / "?" /
>                     "^" / "_" / "`" / "{" / "|" / "}" / "~"

Email address in Tb's address book : (all special chars of atext except !)
  #$%&'*+-/=?^_`{|}~@a.b.c
=> Localpart is not quoted correctly by Tb 53 as expected in Compose, Send Later.

It looks that "!" is missing in table for allowed special chars.
Was "!" added while change from rfc822 to rfc2822, or change from rfc2822 to rfc5322?
Looking at some tests, the existing behaviour is clearly desired and cemented-in in various tests:
https://dxr.mozilla.org/comm-central/rev/424cdd3c5239dd57a3110b6468bb79ca9d005eaa/mailnews/mime/jsmime/test/test_header_emitter.js#53-54

https://dxr.mozilla.org/comm-central/rev/424cdd3c5239dd57a3110b6468bb79ca9d005eaa/mailnews/mime/jsmime/test/test_header.js#206-208
https://dxr.mozilla.org/comm-central/rev/424cdd3c5239dd57a3110b6468bb79ca9d005eaa/mailnews/mime/jsmime/test/test_header.js#225-229

So the original author knew exactly what he wanted. This is deliberate. Sadly, the original author is mostly unavailable for comment these days.
Flags: needinfo?(Pidgeot18)
https://tools.ietf.org/rfc/rfc976.txt
https://en.wikipedia.org/wiki/UUCP

Why support of Bang path of UUCP is still needed/mandatory in Thunderbird?
Movemail account is a kind of UUCP? It's used in some Chat feature?
You need to log in before you can comment on or make changes to this bug.