Quoted names of senders/recipients showing up in gmail instead of addresses

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Upload emails from outlook 2003
2. Look at sender/recipient names on the email

What is the expected output? What do you see instead?
I would expect that the tool would include the email addresses of the
senders/recipients, but it seems to parse only the "Display name" of the
senders and recipients.

What version of the product are you using? On what operating system?
1.0; Windows XP

Original issue reported on code.google.com by nshort...@gmail.com on 22 Feb 2008 at 12:36

[GoogleCodeExporter]

I'm having the same issue.  It looks like there is a quote issue as all my 
names come
in as <name>"  with a quote mark and no email address.

Original comment by matthew-...@dreon.org on 27 Feb 2008 at 7:45

[GoogleCodeExporter]

Clarification, the messages being imported with a <name>" are the local 
messages that
Outlook recognizes as originating from inside our domain.  Thus, only the 
shortcut
name is displayed.  Not sure why there are dangling quotes though.

Uploading .pst files will be very handy but I think I'll wait until this issues 
is
resolved before I move forward.

Original comment by matthew-...@dreon.org on 27 Feb 2008 at 7:51

[GoogleCodeExporter]

For what it is worth, the same thing is happening for me.

Original comment by iam...@gmail.com on 6 Apr 2008 at 7:22

[GoogleCodeExporter]

I was starting to look into the source code for the upload to spot the possible
problem with the code, then it occurred to me that it might not be the uploader 
at
all.  I visited one of these messages in the Google Apps inbox and used the 
"Show
Original" option and can see that the original email file is intact on the 
server. 
So, could this simply be a problem on the server end that can be corrected in 
time
without the need to fix the uploader?

Here is what I am seeing in the original message text for a garbled message:

From: "Vegas Gillette"
Sender: "Vegas Gillette"
To: <amit@betaplayednosuchdomainname.com>,
    "Bob Bigellow"
Cc: "Tom Timpson",
    "Will Smith"

"Vegas Gillette", "Bob Bigellow", "Tom Timpson", and "Will Smith" are all users
within the same domain, so this is just how Outlook rolls.  Mine happens to be 
"Bob
Bigellow".  (By the way, I renamed the names in this sample to protect the 
guilty.) 
It seems that the Google Apps Gmail service (on the server-side) sees "Vegas
Gillette" and assumes that the name is:

"Vegas

...and the email address is:

Gillette"

...which is obviously erroneous.  It is automatically assuming that the space 
must be
delimiting the name from the email address and it is also ignoring the meaning 
of the
quotes.  It is rather unfortunate that even with a fix, there will likely be a 
lot of
emails without valid email addresses associated with them, unless these are in 
fact
found within the Outlook data and is simply not getting picked up by the 
uploader.

In any case, if we use the uploader to send the data to the servers... can the 
bug on
the servers be fixed after-the-fact, without requiring a re-upload by us?

Original comment by iam...@gmail.com on 6 Apr 2008 at 7:39

[GoogleCodeExporter]

>unless these are in fact
>found within the Outlook data and is simply not getting picked up by the 
uploader.

This is exactly where I think the problem lies.  Clearly, the email information 
is
somewhere (either a GAL lookup using the user's name, or some sort of behind the
scenes action), so the question is: How can the Uploader be modified so that it
queries this information?

If this cannot be fixed, the tool is going to be rather useless for people 
migrating
from Exchange, because it seems that the "Firstname Lastname" sans email format 
is
standard within the Outlook/Exchange combination.  And, considering that the 
APIs
only work for Premier Edition users, this MS integration is going to be key.

Original comment by nshort...@gmail.com on 7 Apr 2008 at 6:13

[GoogleCodeExporter]

I'm experiencing this also.  I have Exchange 2003 and Outlook 2007.

Original comment by ssfl...@gmail.com on 9 Apr 2008 at 1:52

[GoogleCodeExporter]

We get the same problem. Names are displaying as Surname" and you can't reply to
imported email without manually correcting the address. We are using Exchange 
2000
and Outlook 2007. 

I tried exporting the inbox to a PST file and then attaching it back in to 
outlook so
the data isn't being pulled from exchange, but this made no difference.

Very frustrating, as this is a nice program that almost works very well, but no 
use
to anyone using a GAL until this is fixed.

Original comment by NeilTurl...@gmail.com on 14 Apr 2008 at 12:22

[GoogleCodeExporter]

I am seeing the same problem. We are using Exchange 2007 and Outlook 2007. This 
is a critical bug, and has 
also been reported in the forums groups.

http://groups.google.com/group/google-email-uploader/browse_thread/thread/371d3b
81383803f5

This issue is keeping IT departments from turning on the switch to move over to 
Google Apps. Are the 
developers paying attention?

Original comment by hkc...@gmail.com on 4 May 2008 at 11:30

[GoogleCodeExporter]

ig,,,,,,,,,,,,,,,,

Original comment by dorgamk...@gmail.com on 9 May 2008 at 1:00

[GoogleCodeExporter]

Getting the same problem with Exchange 2003 and Outlook 2007.

I'm working to convince management that google apps is the way to go, and this 
looks
pretty bad in a demo. We would be upgrading to the Premier service, anyone know 
if
the Premier mail transfer has the same problem?

Original comment by akstormr...@gmail.com on 15 May 2008 at 8:53

[GoogleCodeExporter]

We just upload the email as it is stored in Outlook.  If outlook has no email
addresses for the name in quotes, then there is no way for us to find the email 
address.

Original comment by cvander...@gmail.com on 19 May 2008 at 4:13

[GoogleCodeExporter]

But there must be a way to query  the exchange server as Outlook does when it is
formatting the data for conversion.  If outlook can interpret the quoted names 
as the
correct email addresses, it would make sense that there would be a mechanism in
Outlook that the uploader could use.

Original comment by nshort...@gmail.com on 19 May 2008 at 5:05

[GoogleCodeExporter]

My name is Fahad. I am a citizen of Yemen working in Ta'if-Saudi Arabia as a 
front 
desk operator in a hotel and furnished apartment complex.I consider myself a 
humble 
person. I like to have lot of friends and I am in love with Wikimapia.My 
working 
hours are 12 and i spend most of them watching Wikimapia which i consider my 
window 
on the world.I want to learn a lot and i miss the knowledge of the english 
language , hence i have a language barrier. I appreciate those who help and i 
wish 
always to help  .

Original comment by orif2...@gmail.com on 20 May 2008 at 12:53

[GoogleCodeExporter]

Email address information is available if one uses IMAP to communicate between
Outlook and gmail. Thus there must be some way to figure this out. If IMAP 
doesn't
have its own problem (formatting loss, since gmail doesn't understand 
winmail.dat,
see
http://groups.google.com/group/Gmail-Help-POP-and-IMAP-en/browse_thread/thread/d
df15b91897567b1/),
I would just use IMAP.

Original comment by liling on 22 May 2008 at 8:16

[GoogleCodeExporter]

It's appropriate that this is issue #1 -- it's the first thing I ran into.  It 
needs 
to be fixed.

Original comment by anders.w...@gmail.com on 2 Jun 2008 at 5:50

[GoogleCodeExporter]

Is no one from Google looking at this issue.  This issue is the main reason 
that I'm
not moving my 300 employees from Exchange to Google Apps.

Original comment by ssfl...@gmail.com on 7 Jun 2008 at 3:44

[GoogleCodeExporter]

If you're using Google Apps Premiere (which you should be if its a real 
business [^^
with 300 employees especially] - $50 per year, per employee is nothing compared 
to
Exchange), the server-side migrator works way better in all sorts of ways, and 
does
not corrupt the names the way this uploader does.

Original comment by akstormr...@gmail.com on 8 Jun 2008 at 8:24

[GoogleCodeExporter]

Thank you akstormrider, I didn't know there was another uploader for the Premier
edition.  I was wanting to do a quick proof of concept for a few people at 
first to
show that using Google as a host will be as good if not better than doing it
ourselves with Exchange.

Original comment by allisonf...@gmail.com on 8 Jun 2008 at 2:48

[GoogleCodeExporter]

Has anyone had any luck with third party email importers/exporters between 
Outlook
2003 and Google Apps mail? I am getting the problem outlined above.

Original comment by viekos...@gmail.com on 13 Jun 2008 at 9:45

[GoogleCodeExporter]

I can't believe it's MID-AUGUST and Google STILL hasn't fixed this.
Also, my IMAP migration is broke, so even worse.

Original comment by MichaelL...@gmail.com on 15 Aug 2008 at 1:56

[GoogleCodeExporter]

The RFC requires that email "From" and "To" addresses have email addresses in 
them. 
In situations where the email doesn't conform to the RFC, we upload it anyway.  
I'm
marking this as "won't fix" since we really only plan to conform to the RFC.

Original comment by cvander...@google.com on 20 Aug 2008 at 1:04

• Changed state: WontFix

[GoogleCodeExporter]

Regarding the "won't fix" comment.  While only planning to conform to a 
standard (the
RFC) is admirable, I feel it is misplaced in this context.

I thought the point of the email uploader (though I could be wrong) was to help
Outlook users to upload emails from Outlook to their Google-hosted email 
account to
make migration easier.  If this is the case, it would seem that the primary 
goal of
the tool would be to conform to the rules of Outlook rather than the rules of a 
standard.

Again, this isn't a tool that is attempting to further support a standard... it 
is
meant to help in migration.  If Outlook is not 100% RFC-compliant, it only 
stands to
reason that a migration tool meant to integrate with Outlook would not be 
expected to
be RFC-compliant inasmuch as it is expected to be Outlook-compliant.

By saying that this is something that "won't be fixed" would basically suggest 
that
this tool was never actually supposed to help Outlook users to migrate to Google
Apps, forcing people to abandon their plans of using Google Apps and stick with 
the
walled garden known as Outlook.  If this is the case, it's too bad... because I 
think
that once people feel comfortable enough to completely make the switch (after
escaping the walled garden of Outlook) without negative consequences (like 
corruption
of all prior emails,) they will never look back.

Original comment by iam...@gmail.com on 20 Aug 2008 at 6:24

[GoogleCodeExporter]

I also think the "WontFix" status is a horrible decision.  This is the main 
issue
that stop me from migrated several hundred users to Gmail in the first place.  
Now
that I'm at a new job, where 50 users use Outlook, we will never move to Gmail 
if we
can't migrate without screwing up the From and To fields.  This isssue needs to 
be
resolved, and resolved fast.  Google needs to quit being lazy and just fix 
this, 
it's not that hard of a fix.

Original comment by ssfl...@gmail.com on 20 Aug 2008 at 7:17

[GoogleCodeExporter]

Is there any other options out there?  To import a .PST file into gmail (a 
google
apps) w/ out using IMAP, I have a 4G file(s).

Original comment by dcollins...@gmail.com on 30 Sep 2008 at 7:00

[GoogleCodeExporter]

How on earth can citing Outlook as "not RFC compliant" be used as a reason not 
to 
fix this?  As has already been pointed out, the primary function of the 
uploader is 
to convert from the native format of the mail being uploaded to gmail format.  
Stated plainly, the function of the uploader IS to make this conversion.

Someone has said that the premier ($50 per year) service does not have this 
problem.  This proves that it's possible to resolve.  It's just a matter of 
will.

I guess we must all remember this thing is free.

Original comment by stevegil...@gmail.com on 30 Sep 2008 at 12:32

[GoogleCodeExporter]

Just find/replace - It's a pain, but oh well.

Original comment by joey...@gmail.com on 23 Apr 2010 at 5:23