User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322) Build Identifier: version 1.5.0.4 (20060516) when using Chopper for Maxsea a navigation program, we are supposed to define a perimeter to ask weather information. it works with Outlook express but not with Thunderbird; For instance for the same area, we got this message with OE :@mto@reqt@grib@ Z -60.7 18 17.9 12 ; D Monde ; P vent pmer vague ; E 6 12 24 36 42 48 72 96 ; C none ; V 0.0 0.0 ; @mto@reqt@fin@ and with Thunderbird only :@mto@reqt@grib@ Z Reproducible: Always Steps to Reproduce: 1.define the area in Maxsea Chopper 2.dend the email with Thunderbird 3.get only : :@mto@reqt@grib@ Z The software should have registered a geographical area like :-60.7 18 17.9 12 ; D Monde ; P vent pmer vague ; E 6 12 24 36 42 48 72 96 ; C none ; V 0.0 0.0

Maxsea Chopper seems to use the Extended MAPI protocol, see http://comfr.maxsea.fr/MaxSea/Support/FAQ/937.aspx (in French).

Would bug 128284 block this? Or is that far more expansive than what's needed here? (I'm really, really shocked I find only bug 128284 in a search on summaries for only extended mapi)

bug 128284 is sort of the converse of this bug, I would say - this bug wants us to implement MAPI 1, i.e., be a MAPI 1 provider, so other apps can make MAPI 1 calls into us. bug 128284 wants us to be able to make MAPI 1 calls to fetch mail, where we're really a MAPI 1 client. Full MAPI 1 provider support is a huge amount of work. Maybe there's some subset that makes sense to support that makes it merely a large amount of work, but we'd need to know what other apps want.