After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 621762 - Evolution changing to address if it contains period
Evolution changing to address if it contains period
Status: RESOLVED DUPLICATE of bug 619347
Product: evolution
Classification: Applications
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-06-16 11:39 UTC by Ruchir Brahmbhatt
Modified: 2013-09-13 01:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ruchir Brahmbhatt 2010-06-16 11:39:54 UTC 
OS: opensuse 11.2 x86_64
Evolution: 2.31.3
Account: Gmail IMAP

Recently I faced a strange issue. Whenever I try to send email to a specific contact, mail used to bounce every time. I confirmed if there's any issue with email address or server but it was not. Then I checked in detail and tried to figure out. I was able to find out the pattern which was causing this. 

For testing I switched to offline mode and sent email to below address.
Inc. Fname Lname <fname.lname@domain.it>

I went to outbox and checked to address, it was as below.
Inc.FnameL <name fname.lname@domain.it>

Then I sent mail to "Inc Fname Lname <fname.lname@domain.it>" and checked outbox, now it was proper.

I did couple more test and figured out that whenever the name contains 3 words and first word contains period, evolution changes email address as explained above. The important point is it does it while sending email not while composing so we think its sending to correct address but its actually not. 

This is potentially big issue as some important mails may be bounced or sent to unexpected addresses.
Comment 1 André Klapper 2010-06-18 18:44:09 UTC 
Also see bug 621812
Comment 2 Akhil Laddha 2010-09-30 05:38:19 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 619347 ***