[rt-users] Please Support Me!
Mile by mile and dollar by dollar, Bike MS is changing lives.. That's why I registered for Bike MS and why I'm asking you to support my fundraising efforts with a tax-deductible donation. The National Multiple Sclerosis Society is dedicated to creating a world free of MS, but they can't do it without our help. It's faster and easier than ever to support this cause. Simply click the link below to visit my page and make a donation. Your donation supports cutting-edge research and programs and services for everyone impacted by MS. Ending MS means no one will receive an MS diagnosis again. Every dollar helps. Every person makes a difference.. Please visit National MS Society today! http://main.nationalmssociety.org/site/TR?px=12627943&pg=personal&fr_id=26036&et=Nm7h0syLRAp1QqarZcZCPw&s_tafId=409880";>Click here to visit my personal page. If the text above does not appear as a clickable link, you can visit the web address: http://main.nationalmssociety.org/site/TR?px=12627943&pg=personal&fr_id=26036&et=Nm7h0syLRAp1QqarZcZCPw&s_tafId=409880 http://main.nationalmssociety.org/site/PixelServer?tr=9fYh_NSlbL62RPyrbYGJEw"; height="1" width="1" alt=""/> If you no longer wish to receive email messages sent from your friends on behalf of this organization, please follow the link below: http://main.nationalmssociety.org/site/TellFriendOpt?action=optout&toe=389fe5c9951b652215f87b69d5b0331b20264f1193e03f84117f0eec58e029dac157793613dbaef5 National MS Society | http://www.nationalmssociety.org/index.aspx Forward to a Friend | http://main.nationalmssociety.org/site/TellAFriend Privacy Policy | http://www.nationalmssociety.org/legal-notice-privacy-policy/index.aspx Unsubscribe http://main.nationalmssociety.org/site/CO 733 Third Avenue, New York, New York 10017 | 1-800-FIGHT-MS (344-4867) FOLLOW US Facebook Twitter YouTube LinkiedIn Blogger Flickr MS Connection https://www.facebook.com/nationalmssociety https://twitter.com/mssociety http://www.youtube.com/nationalmssociety http://www.linkedin.com/company/national-ms-society http://www.msconnection.org/Blog http://www.flickr.com/photos/nationalmssociety http://www.msconnection.org
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 )
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
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
