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 679305 - EX addresses not decoded in folder summary
EX addresses not decoded in folder summary
Status: RESOLVED FIXED
Product: evolution-ews
Classification: Other
Component: Mail
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Evolution EWS maintainer(s)
Evolution EWS maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-07-03 08:06 UTC by Milan Crha
Modified: 2013-04-24 06:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
ews patch (17.50 KB, patch)
2012-07-03 13:18 UTC, Milan Crha
committed Details | Review
ews patch ][ (7.35 KB, patch)
2012-07-04 11:01 UTC, Milan Crha
committed Details | Review

Description Milan Crha 2012-07-03 08:06:16 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=833744

When there is a recipient stored as <t:RoutingType>EX</t:RoutingType>, then this is not shown in message list. The message itself tries to decode the address, but fails too, as it doesn't convert EX address into SMTP address (also related to bug #672530).

My fetch snippet looks like:
 <t:ToRecipients>
   <t:Mailbox>
     <t:Name>'mcrha'</t:Name>
     <t:EmailAddress>/O=xxx/ou=yyy/cn=Recipients/cn=mcrha</t:EmailAddress>
     <t:RoutingType>EX</t:RoutingType>
   </t:Mailbox>
 </t:ToRecipients>
Comment 1 Milan Crha 2012-07-03 13:18:37 UTC
Created attachment 217931 [details] [review]
ews patch

for evolution-ews;

This patch enables EX mailboxes (before was only SMTP mailboxes used), and a function which tries to convert EX address into SMTP address is also added. It tries to do that according to [1], but if it fails then at least a guess based on the 'cn' of the ex address is done. The worse case here is that the email address will be filled with the EX address, instead of completely ignoring the address.

[1] http://blogs.msdn.com/b/vikas/archive/2007/09/05/howto-ews-get-smtp-address-from-x500-address.aspx
Comment 2 Milan Crha 2012-07-03 13:21:01 UTC
Created commit f7e410d in ews master (3.5.4+)
Created commit 32b2e93 in ews gnome-3-4 (3.4.4+)
Comment 3 Milan Crha 2012-07-04 11:01:31 UTC
Created attachment 218006 [details] [review]
ews patch ][

for evolution-ews;

A follow-up fix, after a notice in the downstream bug. There is one regression, if the mailbox contains only name, not email, then I threw it away as invalid, which could lead to missing From in message list.

It seems that EX addresses are useless, and kinda scary in message list, thus this patch also sets no email in case of unable to resolve the address. One more resolve test was added, based on Mailbox's 'name'. If that matches any resolved user with SMTP address, then that one is used (it's the last try to change EX to SMTP).
Comment 4 Milan Crha 2012-07-04 11:03:15 UTC
Created commit 7be81b6 in ews master (3.5.4+)
Created commit 7d6d159 in ews gnome-3-4 (3.4.4+)
Comment 5 Milan Crha 2013-04-23 07:46:33 UTC
Mikhail, due to bug #689382 and bug #686227, can it be that you got EX addresses only for people whom are no longer working in your company? David told me that it's the case for him, the ResolveNames is called for such people only, same as for Erik, thus if it's true, then this whole change is wrong and might not be in sources (I didn't get it initially, unfortunately).

Could you verify/guess it anyhow, please?
Comment 6 Mikhail 2013-04-23 14:53:06 UTC
Yes, this problem appears only for mailboxes for people whom no longer working in our company.
Comment 7 Milan Crha 2013-04-24 06:21:43 UTC
Thanks for the reply. In that case I'll commit the change from bug #686227, a very different approach.