wasm-demo/demo/ermis-f/imap-protocol/cur/1600095031.22665.mbox:2,S

107 lines
3.6 KiB
Plaintext

MBOX-Line: From blong at google.com Tue Aug 13 16:24:11 2013
To: imap-protocol@u.washington.edu
From: Brandon Long <blong@google.com>
Date: Fri Jun 8 12:34:51 2018
Subject: [Imap-protocol] GMail IMAP: returning BODYSTRUCTURE for embedded
messages
In-Reply-To: <CABDm0O-7QWY2ks6hi5HEZOgV=bNXqgYuKPa3vSFNm9-Vh0EyGA@mail.gmail.com>
References: <CABDm0O_8gHzzawop++-m5vE9tcLS3b_=DqtNHiwCvAHkXbULGg@mail.gmail.com>
<CABa8R6vU_Sh_nQWO_Jm+BpTvr3uyiZ06DtZHYAZEBciYMpJUWQ@mail.gmail.com>
<CABDm0O-7QWY2ks6hi5HEZOgV=bNXqgYuKPa3vSFNm9-Vh0EyGA@mail.gmail.com>
Message-ID: <CABa8R6tw8cUdG0pqSRuJk_paqAg=6ocXcrpSB+Qr1Sy81A6J5g@mail.gmail.com>
Low priority.
Brandon
On Tue, Aug 13, 2013 at 9:22 AM, Ali, Saqib <docbook.xml@gmail.com> wrote:
> Hello Brandon,
>
> Thanks for the response. Where is this issue in the Google priority
> list? I understand that you may not have an ETA, but we would like to
> understand if Google considers this of high priority or low prirority.
>
> Thanks! :)
>
> On Mon, Aug 12, 2013 at 4:09 PM, Brandon Long <blong@google.com> wrote:
> > Like everything, its complicated.
> >
> > We attempted to roll out a fix for this a year ago, and it even fixed
> some
> > other random bugs in completely unrelated code.
> >
> > Unfortunately, it also broke some fairly important backend handling of
> > messages that were previously parsed with the incorrect parser as it
> changed
> > our understanding of the structure of the message. Enabling our system
> to
> > handle these types of changes is very complicated, and the work is still
> > ongoing. I don't have an ETA on when we'll be able to switch to the
> correct
> > parsing.
> >
> > The exact bug was that we didn't parse message/rfc822 attachments if they
> > had a Content-Disposition: header of value attached. This was an
> > unfortunate and wrong fix to a bug in the early days of Gmail where
> people
> > would want to attach entire email messages (.eml files) and forward them
> and
> > otherwise handle them as an "attachment" and not a sub-part of the
> message.
> >
> > Brandon
> >
> >
> > On Thu, Aug 8, 2013 at 2:57 PM, Ali, Saqib <docbook.xml@gmail.com>
> wrote:
> >>
> >> Hello,
> >>
> >> Has there been any progress made on this?
> >>
> >> Thanks!
> >> Saqib
> >>
> >> Brandon Long <blong <at> google.com> writes:
> >> >
> >> > Yes, we have an open bug for this one, I'm not sure why there hasn't
> >> > been any progress on it.
> >> >
> >> > Brandon
> >> >
> >> > On Thu, May 19, 2011 at 7:35 AM, Mark Crispin <mrc+imap <at>
> panda.com>
> >> > wrote:
> >> > > On Thu, 19 May 2011, Jan Kundr?t wrote:
> >> > >>
> >> > >> I'd appreciate if you could investigate your compliance with the
> >> > >> format
> >> > >> of BODYSTRUCTURE you generate when working with certain messages,
> as
> >> > >> described in this messages. The same issue was reported to you
> >> > >> through
> >> > >> an internal issue tracker in January 2011 by Henner Zeller on my
> >> > >> behalf.
> >> > >
> >> > > And was reported by me more than 3 years ago.
> >> > >
> >> > > -- Mark --
> >> > >
> >> > > http://panda.com/mrc
> >> > > Democracy is two wolves and a sheep deciding what to eat for lunch.
> >> > > Liberty is a well-armed sheep contesting the vote.
> >> > > _______________________________________________
> >> > > Imap-protocol mailing list
> >> > > Imap-protocol <at> u.washington.edu
> >> > > http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol
> >> > >
> >> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20130813/7e76206f/attachment.html>