Re: [rt-users] forwarding correspondence lacks important data in headers
On Tue, Sep 08, 2015 at 08:56:53AM +0200, Arkadiusz Miśkiewicz wrote: > > Hi. > > rt 4.2.12, scenario - there is a ticket, user enters new correspondence via > web interface which is send via email to requestor. > > Then user clicks "forward" near that correspondence and forwards it to third > email address / third person. > > Unfortunately that email sent to third person is lacking important > information. It lacks From, To, Subject headers in attached forwarded message. This should have been fixed in 4.2.10: https://bestpractical.com/release-notes/rt/4.2.10 https://github.com/bestpractical/rt/commit/134a478be1b63ca418380fc355923ea849812bfa Are you still seeing a lack of such headers for tickets created since your upgrade to 4.2.12? Tickets created _prior_ to an upgrade to 4.2.10 will still lack the headers in their Create transactions, of course. > I would expect to see proper From, To, Subject, Date (like in original > correspondence) and possibly other headers, too. Also there is incorrect > Content-Length in it. Hm -- the content-length problem doesn't seem to be replicated on issues.bestpractical.com. Are you seeing it with a vanilla 4.2.12 install? - Alex
Re: [rt-users] forwarding correspondence lacks important data in headers
On Tuesday 08 of September 2015, Alex Vandiver wrote: > On Tue, Sep 08, 2015 at 08:56:53AM +0200, Arkadiusz Miśkiewicz wrote: > > Hi. > > > > rt 4.2.12, scenario - there is a ticket, user enters new correspondence > > via web interface which is send via email to requestor. > > > > Then user clicks "forward" near that correspondence and forwards it to > > third email address / third person. > > > > Unfortunately that email sent to third person is lacking important > > information. It lacks From, To, Subject headers in attached forwarded > > message. > > This should have been fixed in 4.2.10: > https://bestpractical.com/release-notes/rt/4.2.10 > > https://github.com/bestpractical/rt/commit/134a478be1b63ca418380fc355923ea > 849812bfa > > Are you still seeing a lack of such headers for tickets created since > your upgrade to 4.2.12? Tickets created _prior_ to an upgrade to > 4.2.10 will still lack the headers in their Create transactions, of > course. I've checked forwarding of a single correspondence (one correspondence entry, not entire ticket) where ticket and that correspondence was created on 4.2.12. Unfortunately the problem persist - headers are missing information. How to reproducte: - create ticket via web UI - add correspondence with some text and attach pdf file to it; via web UI) - click forward near that correspondence (we want to forward only that one correspondence entry, not entire ticket); again via web UI - enter some email address "email address" receives message with missing headers. > > I would expect to see proper From, To, Subject, Date (like in original > > correspondence) and possibly other headers, too. Also there is incorrect > > Content-Length in it. > > Hm -- the content-length problem doesn't seem to be replicated on > issues.bestpractical.com. Are you seeing it with a vanilla 4.2.12 > install? > - Alex -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
[rt-users] forwarding correspondence lacks important data in headers
Hi. rt 4.2.12, scenario - there is a ticket, user enters new correspondence via web interface which is send via email to requestor. Then user clicks "forward" near that correspondence and forwards it to third email address / third person. Unfortunately that email sent to third person is lacking important information. It lacks From, To, Subject headers in attached forwarded message. Example - this is what third person gets as attached forwarded message, no more headers than these: MIME-Version: 1.0 X-RT-Interface: Web X-Mailer: MIME-tools 5.505 (Entity 5.505) X-RT-Original-Encoding: utf-8 Content-Type: multipart/mixed; boundary="--=_14261232133-20661-12746" Message-ID: In-Reply-To: References: RT-Send-CC: Content-Length: 0 X-UID: 0 [here body of forwarded message follows] Is this how this always worked? If not, there is a bug somewhere. I would expect to see proper From, To, Subject, Date (like in original correspondence) and possibly other headers, too. Also there is ncorrect Content-Length in it. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
Re: [rt-users] forwarding correspondence lacks important data in headers
On Tue, Sep 08, 2015 at 03:35:46AM -0400, Alex Vandiver wrote: > > I would expect to see proper From, To, Subject, Date (like in original > > correspondence) and possibly other headers, too. Also there is incorrect > > Content-Length in it. > > Hm -- the content-length problem doesn't seem to be replicated on > issues.bestpractical.com. Are you seeing it with a vanilla 4.2.12 > install? Wait, the content-length of a multipart/mixed part should indeed be 0 -- it itself has no content. It is the sub-parts that have content. Arguably Content-Length should be entirely omitted on multipart/* parts, but its presence is unlikely to cause interoperability concerns. But that does beg the question -- are you seeing the headers bug only on multipart/mixed messages? How are you creating them via the web UI, by adding attachments? - Alex
