there are non-ascii characters in the local part of the recipient address when empty email in address book

NEW
Unassigned

Status

3 years ago
2 years ago

People

(Reporter: walt_northrup, Unassigned)

Tracking

({regression})

38 Branch
regression

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150812163655

Steps to reproduce:

I have an address book in which some entries have no email address at all.  Up through Tbird 31.5.0, I could send to this address book with no issues.  Tbird just skipped the ones with no email.  Starting with Tbird 38.1 (also in 38.2), these entries with no email cause the "there are non-ascii characters in the local part of the recipient address" error.


Actual results:

I cannot send to these address books due to the error noted above.  I uninstalled 38.2 and backed down to 31.5 (also backed down lightning) and it works as it did before.  


Expected results:

I would hope that 38.1 and 38.2 would work as 31.5 does.  As of now, I'm stuck on 31.5 due to this problem.

Comment 1

3 years ago
Can confirm Behaviour in Daily

Steps to reproduce.

Insert a contact in the address book with only a display name and no email address.
Use that contact to send a mail.

Result,  error as indicated in the original posting, valid addresses ignored.

Expected behaviour: 
Invalid addresses removed and mail sent to valid addresses. 
Warning to sender that XXXX has been removed as invalid.
Status: UNCONFIRMED → NEW
Component: Untriaged → Message Compose Window
Ever confirmed: true

Updated

3 years ago
Keywords: regression

Comment 2

3 years ago
I've upgraded an RHEL server to the 38.2.0 and several users are reporting the issue. It happens with valid email addresses and also from xdg-email calls that use adresses that are not in the abook. It seems more frequent when there is more than one recipient and that removing the <> chars, that now appear at the end of the TO field, "fixes" the problem.

Updated

3 years ago
See Also: → bug 1223667

Comment 3

3 years ago
Can confirm this behaviour, I get the alert:

There are non-ASCII characters in the local part of the recipient address . This is not yet supported. Please change this address and try again.

Just upgraded to Icedove (Thunderbird) 38.3.0 today. Earlier today I could send the message no problem.
Running: Linux 4.2.0-1-amd64 #1 SMP Debian 4.2.3-2 (2015-10-14) x86_64 GNU/Linux

Comment 4

3 years ago
(In reply to hallfaer from comment #3)
> Can confirm this behaviour, I get the alert:
> 
> There are non-ASCII characters in the local part of the recipient address .
> This is not yet supported. Please change this address and try again.
> 
> Just upgraded to Icedove (Thunderbird) 38.3.0 today. Earlier today I could
> send the message no problem.
> Running: Linux 4.2.0-1-amd64 #1 SMP Debian 4.2.3-2 (2015-10-14) x86_64
> GNU/Linux

BTW, I don't know which version I was running earlier today, sorry about that.

Comment 5

3 years ago
(In reply to hallfaer from comment #3)
> Can confirm this behaviour, I get the alert:
> 
> There are non-ASCII characters in the local part of the recipient address .
> This is not yet supported. Please change this address and try again.
> 
> Just upgraded to Icedove (Thunderbird) 38.3.0 today. Earlier today I could
> send the message no problem.
> Running: Linux 4.2.0-1-amd64 #1 SMP Debian 4.2.3-2 (2015-10-14) x86_64
> GNU/Linux

Ah, I just noticed that I tried to sent to a group, one of those people has no e-mail address. (I have included him, so once I get his e-mail so he'll then get the mail too.) When I instead grabbed an older mail on the same topic, and sent my mail as a follow up to that, it worked, because it did not include the person without an address.

Comment 6

3 years ago
I experienced the same for a simple Gmail address. There is not any non ascii character after the @, before the @, and neither in the name of the recipient. I have to click 7 times to the OK button, and after that Thunderbird sends the email without any further problem.

Comment 7

3 years ago
Since upgrading to Icedove 38.4 (from 31.7) on Debian stable, I also have this issue.

I can reproduce the issue when trying to send an email to an email structured as the following "foo bär, baz <baer@baz.com>" or "ö, <baer@baz.com>" - the name part must contain both an umlaut and a comma, otherwise I cannot reproduce.

OTOH, the previous commenter mentioned that s/he can reproduce it without any non-ascii character in name or email.

I don't have any users with an empty email field in my address book, so this is most likely a red herring (or a different issue). We might want to change the title of this issue.

Comment 8

3 years ago
I can't see the problem with neither an empty email in a Ab contact (card) or non-ascii characters in the contacts name.

Maybe somebody can export a sample problematic contact and attach it here?

Comment 9

3 years ago
> Maybe somebody can export a sample problematic contact and attach it here?

For me (now on Icedove 38.5.0, Debian stable), it's sufficient to try to send an email to:

    ö, <any@example.org>

No need to use the address book at all. If you want use a contact, give it a name such as "Fö Bar, Company".

Comment 10

3 years ago
I pasted that exact recipient "ö, <any@example.org>" into the compose window and pus some subject and body. The I clicked Send later. The window closed and the message is in Outbox.
This worked for me in TB38 and also in TB46 (development version).
That is on Linux too.

Comment 11

3 years ago
"Send later" doesn't cause the issue for me either - the problematic email is moved to the outbox as expected. "Send now" (or alternatively "Send unsent messages" after "send later") triggers the alert and does not work.
(Reporter)

Comment 12

3 years ago
Never used send later.  I don't even know where it is or what it does.

Comment 13

3 years ago
This issue has been bugging me ever since I started using Thunderbird many years ago. It is still there in Version 38.7.2. The addresses flagged by TB as having non-ASCII characters in their local part have no non-ASCII characters in them anywhere. I wish someone would take this issue and address it seriously as an urgent bug fix request. Thanks.

Comment 14

3 years ago
P.S. This "error" occurs even when there is no empty e-mail address in the address book.

Comment 15

3 years ago
I cannot send to such address email:

first.second-last@example.com
I think hyphen here is a problem.
(Reporter)

Comment 16

2 years ago
Just as a follow up to my original report, I installed Tbird 45.2 (latest as of this comment).  Bug is still there.

Comment 17

2 years ago
vs 45.4.0 also has this error message as soon as an email address has a comma (,). 
For instance: janssen, jan <jan.janssen@email.com> will generate this error. While in the past this did not happen.

How to fix this? Because replying to a message with such an email address will generate this problem.

Comment 18

2 years ago
To supplement Frank's comment, I can confirm that this issue is present in Thunderbird 45.5.0. Error message began occurring to me after updating, never experienced the problem before.

Comment 19

2 years ago
Thunderbird Search did not spit out the complete results. As suggested I deleted global-messages-db.sqlite to rebuild the index.

Since then I get the message "There are non-ASCII characters in the local part of the recipient address . This is not yet supported. Please change this address and try again."


I checked mailnews.force_charset_override

Apply encoding in Inbox Properties is disabled.


Please HELP.

Comment 20

2 years ago
Latest version (45.6 and 45.7) does not seem to have this problem. So fixed?
You need to log in before you can comment on or make changes to this bug.